ClientErrorResponse exception too general, all code/type info is in message string about intercom-php HOT 3 CLOSED

Hi @mikegioia

The API is designed fairly RESTfully, split into resources:

Why am I getting a "404" error when a company ID doesn't exist in a batch update?

The answer to this is because the resource is Company and the resource cannot be found with your supplied parameters.

A missing endpoint is pretty rare (ie. I don't think it's ever happened). You don't need a different exception class for each endpoint, and you don't need to parse the error message. The 404 will tell you if the resource is missing (and other 4xxs will correspond to other types of client errors). In other words, we try to use HTTP instead of rolling our own error signalling.

I hope that helps explain our methodology.

from intercom-php.

No @bobjflong it doesn't explain it. If I send a batch update of 50 company IDs and 1 company doesn't exist, the whole response returns a 404. I don't understand how that makes sense. If it was a single company I could understand that, but this is a batch update.

You're not even returning WHICH company didn't exist. It's just a full stop 404. Do you see how this causes problems during batch updates? I can't know which one failed, and the 49 others didn't go through. So now I have to do them 1 at a time which will defeat the purpose of the batching and cause me to run over my rate limit!

from intercom-php.

We are designing appropriate APIs for bulk updates: https://developers.intercom.io/reference#bulk-apis

(Which don't have company tagging right now).

Why not get in touch through the Intercom messenger (ask for Bob) and we can substantially increase your rate limit if you explain what you need.

from intercom-php.