Search API doesn't pass 402 error but List conversations does - is this intentional?

Helena P · 2021-07-20T15:49:49+00:00

When we make a call to the Conversations Search API, it passes the expected errors as listed here: https://developers.intercom.com/intercom-api-reference/reference#http-responses) BUT the 402 error (which is when the user is on a free plan so can't access the API) doesn't come through. For example, this is what we get for a bad request error: {"type":"error.list","request_id":"003cf6a7obhfbnmt0uv0","errors":[{"code":"invalid_operator","message":"Composite operators must be of type AND or OR "}]}⏎ But we only receive the 402 error if we make a call to List conversations, NOT to Conversations Search. Using the same credentials and app both times. We use version 2.3 of the API. Is this a bug that the Search API is not passing this one 402 error or expected?

Search API doesn't pass 402 error but List conversations does - is this intentional? | Community

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded