API keys and webhooks

Everything in Dalil is accessible programmatically: records, pipelines, tasks, notes, metadata. API keys authenticate your integrations, and webhooks push events to your systems in real time. They are the two building blocks for connecting Dalil to your own tools and scripts.

Both live in Settings → APIs & Webhooks. Full endpoint documentation is in the API Reference.

API keys

An API key is a bearer token that authenticates requests to Dalil's APIs.

Creating one:

1. Go to Settings → APIs & Webhooks → APIs
2. Click Create API key
3. Give it a name (and choose its expiration)
4. Copy the key immediately: it's shown once and can't be retrieved later

Managing keys:

• Regenerate Key: invalidates the old value and issues a new one for the same key entry; update your integrations with the new value
• Delete API key: revokes access entirely (in the key's Danger zone)

Good practice: one key per integration, named accordingly ("Zapier", "Lead sync script"). When a tool is retired or a key may have leaked, delete or regenerate just that key without breaking everything else. Access to this area is controlled by the API Keys & Webhooks role permission.

The APIs

Two interfaces are available:

• REST: CRUD operations on every entity, including custom entities and pipelines (which are discoverable via the metadata endpoints)
• GraphQL: including full-text search across records

Try both live from the built-in playgrounds (REST and GraphQL) linked from the APIs & Webhooks page. They're the fastest way to explore the schema and prototype a query before writing code.

Webhooks

Webhooks notify your systems the moment something happens in Dalil, with no polling.

Creating one:

1. Go to Settings → APIs & Webhooks → Webhooks
2. Click Create Webhook
3. Set the Endpoint URL: Dalil will send POST requests to it for every matching event
4. Choose the events with Filters: pick an entity (or All Entities) and an action (create, update, delete: or All Actions)
5. Optionally set a Secret: a string included with every webhook so your endpoint can verify the request genuinely came from Dalil

Common patterns:

• Person created → sync to your billing or product database
• Opportunity updated → post deal changes to a Slack channel via your own handler
• Record deleted → keep an external audit trail

Webhooks vs. workflows

Both react to events; choose by where the logic lives:

• Workflows act inside Dalil (update records, enroll in sequences, run AI steps), and their HTTP Request action covers simple outbound calls
• Webhooks are for your infrastructure: they deliver the raw event to your endpoint and your code decides what happens

Key outcome

API keys and webhooks turn Dalil from an application into a platform: your scripts, products, and internal tools can read and write CRM data securely, and react to changes the moment they happen.