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

H

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?

 

2 replies

Eric Fitz
Userlevel 1

Hey @helena p​, could I ask you to share with me a sample call that's returning a 402 error, please?

H

Hey Eric -- I'm afraid I can't do that because the API returns that error when you try to fetch data for a workspace that's on the free plan so can't access the API. So the call returning that error depends on the workspace for which you query and I can't share the workspace ids with you here.

 

Please note that I'm reporting that the Search API is not returning the 402 when the List conversations endpoint does.

Reply


Terms & ConditionsCookie settings