Support

Contact

Developer email: [email protected]
Dashboard: manage keys, usage and webhooks in my.kinmu.app → Developers .

For incidents, always include the error’s code, the endpoint, the webhook-id (if applicable) and the approximate timestamp. Never share your API key in a ticket.

Before opening a ticket

The code table explains each code and its cause.

Review the errors

A 403 invalid_scope is almost always a missing scope.

Check your scopes

A 429 indicates burst or quota; check the X-RateLimit-* headers.

Look at the limits

Quick diagnosis

Symptom	First check
`401 unauthenticated`	`Authorization: Bearer …` header; key not revoked or expired.
`403 invalid_scope`	The key has the scope the endpoint requires.
`403 addon_disabled`	The Public API addon is active for the company.
`403 subscription_inactive`	The subscription is up to date.
`404 not_found`	The resource exists and belongs to your company.
`409 idempotency_conflict`	You reused an `Idempotency-Key` with a different body.
`429`	Wait the seconds in `Retry-After`; space out your requests.
Webhook not arriving	Endpoint active, responds `2xx` in < 10 s and signature verified.

Security

Think a key is compromised? Revoke it immediately from the dashboard and review the last_used_ip in the key’s detail. To report a vulnerability, email [email protected] with the subject [SECURITY].

Service status

Maintenance notices, incidents and deprecations are communicated by email to the developer list and logged in the changelog.