Useful information to read before attempting to integrate with the API
500
, that means that there was an issue on our side. If you receive a message in the 4xx
range, then there was an issue with the request you made.
If you receive a 500
, there won’t be any detail in the response, because it carries the risk of exposing the Ctrl Hub internals. You can, however, capture the headers of the response which will contain an X-Trace-Id
header which you can forward to us to investigate.
We try to be as helpful as possible with the 4xx
errors, so that you can understand what went wrong. The typical scenarios for these errors are conflicting resources or incorrect payloads. Therefore, they are most likely to occur when you are trying to create or update a resource or relationship between resources.
For example, if you try to create a resource without the required attributes, you will receive a 400
error with a message explaining what went wrong:
meta
field to give you more information about what the specific error is (in this case, a validation error).