Incident postmortem for /deals/{id}/activities endpoint

#1

Incident postmortem for /deals/{id}/activities endpoint

From 17 Apr 2019 16:30 (UTC +0300) until 24 Apr 2019 14:44 (UTC +0300) the API response for /deals/{id}/activities endpoint started to include full JSON object instead of plain int value for the user_id parameter:

“user_id”: {
    “id”: 123,
    “name”: “test”,
    “email”: “test@example.com”,
    “has_pic”: false,
    “pic_hash”: null,
    “active_flag”: true,
    “value”: 123
}

We apologize for our mistake and will try our best to ensure sufficient communication prior to any breaking change that might happen in the future.

1 Like
Related_objects in API response can now be turned off
#2

We had the same issue with person_id at the same time.
Then int value was not found and there was an object with six fields, status etc.

Postmortem could include all. The person_id was an object a bit longer time.