> For the complete documentation index, see [llms.txt](https://docs.themochi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themochi.app/troubleshooting-and-safety/support.md).

# Get API support

First follow [Troubleshoot API requests](https://docs.themochi.app/troubleshooting-and-safety/diagnose-api-failures.md). If the problem remains, contact your existing Mochi implementation or account contact.

If you cannot see **Settings → Developers**, the controlled self-serve path is not available to your organization. Documentation or a direct URL cannot grant access; see [Create and manage an API key](https://docs.themochi.app/start-here/manage-api-keys.md). If you are already connected through MCP, read [Already connected through MCP?](https://docs.themochi.app/common-tasks/already-connected-mcp.md): do not export its token, and use Public API-specific authorization only when that operation needs it.

## Include this information

* the organization name;
* the UTC timestamp;
* HTTP method and path;
* response status;
* response `X-Request-ID`;
* the API key's name or non-secret prefix;
* whether this was the first attempt or a retry using the same `Idempotency-Key`; and
* a short description of the expected and observed behavior.

## Do not include private data

* the API key or `Authorization` header;
* message text or media;
* email addresses, phone numbers, usernames, or other contact values;
* provider credentials or webhook URLs;
* complete request or response bodies; or
* cursor values unless Mochi specifically requests one through an approved secure channel.

If a key may have been exposed, stop using it and request revocation immediately. Do not wait for the API problem to be diagnosed before revoking a possibly compromised key.
