Classic token (n8n, Zapier)

Routes under /api/v1/accounts on the same domain as the app (https://www.dal-ia.com). The token is in Settings → API access (the "Classic token" block). Only a super admin can see that row. The account owner or administrator should never paste the token into a chat or a repository.

Where to find the token

1. Settings → API access, Classic token (n8n, Zapier) block.
2. API access token field. It's hidden by default; click the eye icon to show it. Copy it with the copy button.
3. Regenerate invalidates the previous token. The on-screen warning says: don't share it; if you think it leaked, regenerate it; only account administrators can see it.

Authentication

api_access_token header (not Bearer). The token must belong to the same account as the account_id in the URL. Requests are rate-limited per IP and per account.

curl -s \
  "https://www.dal-ia.com/api/v1/accounts/ACCOUNT_ID/contacts/CONTACT_ID" \
  -H "api_access_token: TOKEN" \
  -X PATCH \
  -H "Content-Type: application/json" \
  -d '{"custom_attributes":{"ciudad":"Bogotá"}}'

Routes in use

• PATCH /api/v1/accounts/{id}/contacts/{id} — updates the contact's custom attributes (merged with its existing ones).
• POST /api/v1/accounts/{id}/contacts/{id}/labels — adds labels.
• GET /api/v1/accounts/{id}/conversations/{id}/messages — lists a thread's messages.
• POST on the same messages route — sends a message to an existing conversation.

Some module-specific routes (for example, test drives) only apply if that module is enabled. If an old example points to api.daliacrm.com, ignore it: the host is the app's own domain.

Outbound events

With API keys, webhooks are managed through the API itself (/api/v1/webhooks, with HMAC signatures; see the reference). The classic Settings → Webhooks (n8n) flow is still available; see Advanced for details.