
Only organization admins can generate, rotate, or revoke API keys and configure webhooks.
API key management
Your API key authenticates every request to the Partner API. See authentication for how to pass it in your requests.Generate a key
If your organization does not have an active key yet:Click Generate API Key
The dashboard creates a new key and displays it in an orange banner at the top of the page.
Rotate a key
Rotation revokes the current key and generates a replacement in a single step. Use this when you need a fresh key without downtime between revoke and generate.Click Rotate Key
A confirmation dialog warns that existing integrations will stop working immediately.
Confirm the rotation
The old key is revoked and a new key appears in the banner. Copy it before leaving the page.
Revoke a key
Revoking permanently deactivates the key. Any request using the revoked key will receive a403 Invalid API Key error.
Webhook configuration
Webhooks deliver real-time notifications when an analysis changes status, so you don’t need to poll the results endpoint. For full details on events, payload format, and ordering, see the analysis webhooks guide. You can configure your webhook either from this dashboard or via the API withPUT /webhook.
Set up a webhook
Enter your endpoint URL
Provide an HTTPS URL where Ochy will send POST requests. For example:
https://your-app.com/webhooks/ochy.Enable or disable
Once a webhook is configured, use the toggle switch on the Webhooks tab to enable or disable delivery without removing the URL.Edit the URL
Click Edit URL to change the endpoint. After editing, click Update Webhook to save.Test the webhook
Click Send Test Event to send a sample payload to your endpoint. The dashboard displays the HTTP status code and response latency so you can verify connectivity.Events reference
When enabled, your endpoint receives POST requests for these analysis lifecycle events:| Event | Description |
|---|---|
analysis.started | Analysis begins processing |
analysis.progress | Processing percentage updates (at each 10% milestone) |
analysis.completed | Analysis finished successfully |
analysis.failed | Analysis encountered an error |
analysis_id, event_type, status, percentage, a monotonic sequence counter, and a timestamp. See payload format for the full schema.
Usage and credits
The remaining two tabs on the API page provide monitoring:- Usage — view your API request history and consumption patterns.
- Credits — check your remaining analysis credits. Each analysis consumes one credit when started (see authentication).