API keys and webhooks help AfterCheck fit into your existing operating systems such as POS, e-commerce, job management, CRM, helpdesk, email marketing, accounting, and reporting tools.

API keys

API keys are for server-side integrations. Create them from API Keys and choose only the scopes your integration needs.

Store API keys securely. AfterCheck shows the secret only once when the key is created. Revoke keys that are no longer used.

Developer reference is available at API docs.

If an API request fails, keep the API key secret private. Share the request ID, endpoint, HTTP status, scope you expected to use, and workspace name through Support.

Webhooks

Webhooks let external systems receive AfterCheck events. Use Webhooks to create endpoints, choose subscribed events, and review delivery posture.

Consumers should verify webhook signatures before trusting events. Endpoint secrets and provider credentials should never be pasted into public pages, spreadsheets, or customer messages.

If webhook delivery is not behaving as expected, check the endpoint status, subscribed events, delivery console, and recent delivery state first. Share the webhook endpoint ID and provider message ID through Support when you need help.

Data portability

For many teams, integrations are as important as exports. Use CSV exports for manual portability and API/webhooks for operational systems that need live or automated data flow.