# The API and webhooks

> Create an OpenATS API key, and send signed webhooks to your own tools when things happen.

Admins create API keys in **Settings → Integrations → API keys**: name the key and choose **Create key**, and copy it, since it’s shown once. **Webhooks**, on the same page, send signed events such as `application.received` and `opportunity.hired` to a URL of yours.

*Integrations · Last updated 2026-11-11*

---

## API keys

1. Open **Settings → Integrations → API keys**.
2. Enter a **Key name**, such as “Zapier”, and choose **Create key**.
3. Copy the key now. It’s shown once.

The API covers postings, opportunities, contacts, stages and the workspace’s event stream, and other tools can send transcripts to `POST /api/v1/transcripts`. Each key is rate-limited per minute.

> **Note:** An admin’s key sees what an admin sees, and what it adds has no owner. For the OpenATS Extension, each person signs in as themselves instead. See [Installing the OpenATS Extension](https://openats.ai/docs/openats-extension/install-and-sign-in).

## Webhooks

1. On the same page, under **Webhooks**, enter your endpoint’s URL.
2. Optionally, filter the events, for example `application.received, opportunity.hired`.
   Leave it empty to receive every event.
3. Choose **Add**.

- Every delivery is signed: check the `X-Source-Signature` header (HMAC-SHA256) before trusting it.
- Events arrive at least once, in order for each endpoint, and failed deliveries are retried.
- Pause or resume an endpoint with its **Active** switch.

---

Still need help? Write to the OpenATS team at https://openats.ai/support (or support@b150.ai). We reply by email.

Source: https://openats.ai/docs/integrations/api-and-webhooks
OpenATS help center: https://openats.ai/docs