I think there could be a small improvement in the JSON that comes back when trying to add an illegal collaborator (for example: someone has not yet accepted an invitation to a base).
This is the response I’m seeing:
{"error":{"type":"INVALID_VALUE_FOR_COLUMN","message":"Cannot parse value \\"\object Object]\\" for field Rep"}}
I suspect the ‘object’ part should be something else. :winking_face:
More observations, I’m getting different response types for what is basically the same error:
{"error":{"type":"UNKNOWN_COLUMN_NAME","message":"Could not find fields Rep"}}
{"error":{"type":"UNKNOWN_FIELD_NAME","message":"Could not find a field named Payment_Type"}}
The first one is probably a POST and the second a GET request.
More observations, I’m getting different response types for what is basically the same error:
{"error":{"type":"UNKNOWN_COLUMN_NAME","message":"Could not find fields Rep"}}
{"error":{"type":"UNKNOWN_FIELD_NAME","message":"Could not find a field named Payment_Type"}}
The first one is probably a POST and the second a GET request.
Sorry for the confusion! We’ll make the error types more consistent in the next major version of the API, but we can’t change it in this version since it might break existing integrations.
Sorry for the confusion! We’ll make the error types more consistent in the next major version of the API, but we can’t change it in this version since it might break existing integrations.
No prob. As I said, it’s just an observation. 
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.