Support

Building on the GrivaOne API and stuck? Start with this reference — most answers are here — then reach out through the channels below. Good bug reports get resolved fastest, so a little detail up front goes a long way.

Before you reach out

• Check the status portal for a current incident.
• Re-read the errors reference — the status code and error body usually explain the cause.
• Confirm your token is valid and unexpired via the API console or GET /auth/me.
• Search the exhaustive API catalog to confirm the endpoint and its parameters.

How to get help

What to include in a report

The single most useful thing you can provide is the requestId. Every response — success or error — carries one, in the error body, in meta on success, and in the X-Request-Id response header. It lets the team trace your exact request. Also include:

• The HTTP method and full path you called (redact any secrets).
• The response status code and body (with the requestId).
• The approximate timestamp and your X-Company-Id, if set.
• What you expected versus what happened.