Different payloads for same types from webhooks and REST | Community
Skip to main content

Different payloads for same types from webhooks and REST

  • November 16, 2020
  • 1 reply
  • 111 views
M
Forum|alt.badge.img+1

For example:

Webhook-model has event conversation.user.created which seems to return Conversation type.

But if I request the same conversation by id from REST api (i.e. GET /conversations/id) the one from webhook and the one from REST will have different properties . E.g in the webhook's one there is no Source field and not all conversation parts are present.

 The same goes to contacts

 

If it's intended maybe types from webhook model should be documented separately?

1 reply

M
Forum|alt.badge.img+1
  • Misha
  • Author
  • Active User
  • November 17, 2020

One more thing. For topic 'company.created' I'm not getting name of the company even if I create it by typing the name. This makes me do extra call for company after receiving this topic.

 

Example of the event payload:

 

```

"body": {

"type": "notification_event",

"app_id": "ep13p0k7",

"data": {

"type": "notification_event_data",

"item": {

"type": "company",

"id": "5fb3fac9078eba3b55f6ba09",

"company_id": "5fb3fac9078eba3b55f6ba0a-qualification-company",

"app_id": "ep13p0k7",

"created_at": "2020-11-17T16:31:05.462+00:00",

"updated_at": "2020-11-17T16:31:05.551+00:00",

"last_request_at": "2020-10-22T09:19:05.128+00:00",

"monthly_spend": 0,

"session_count": 0,

"user_count": 1,

"tag_ids": [],

"custom_attributes": {}

}

},

"links": {},

"id": "notif_644d3c97-7b1b-49e2-987c-2442c084fe29",

"topic": "company.created",

"delivery_status": "pending",

"delivery_attempts": 1,

"delivered_at": 0,

"first_sent_at": 1605630665,

"created_at": 1605630665

```

Terms & ConditionsAccessibility statement