Skip to main content
Email support@ibubbl.com with questions about the API, a request that isn’t behaving as documented, a webhook that isn’t arriving, or a mistake in these docs.

​
What to include

The more of this you send, the faster we can find your request in our logs:
  • The X-Request-Id response header. Every API response carries one, and it finds your request directly. See Request IDs for how to read it, and how to send your own.
  • When it happened: the date and time, with the timezone (UTC is best). This matters most when you don’t have a request ID, such as for a webhook.
  • The endpoint: method and path, for example POST /v1/messages.
  • The IDs involved: the message id, the contact_id, the webhook subscription id, or the event id (evt_…), whichever apply.
  • The HTTP status and response body you got back, and the request body if there’s no request ID.
  • The email address of your iBubbl account.
For a webhook problem, also include the endpoint URL the subscription points at, and what the dashboard’s webhook log shows for the delivery.
Never send us your API key or webhook signing secret, in full or in a screenshot. Leave the Authorization header out of anything you paste. If you need to say which key you used, give its prefix (the first 14 characters, such as ib_pk_a3f2c8d9), which the dashboard shows next to each key. If a key or secret has been exposed, revoke it in the dashboard first and create a new one.

​
Before you write

  • Errors lists every error code, what it means and whether to retry.
  • Webhook events describes every payload, including why events can arrive out of order or twice.
  • Changelog lists recent changes to the API and these docs.