Before You Start
The Signals API uses the same API key as Zapier. An Org Admin of your organization creates it in Acelab under My Account → Integrations (see Connecting Zapier for the steps). Keys start withak_.
- One key covers all of your organization’s brands. For a distributor or rep firm, that’s each brand you carry (see One Key for All Your Brands). Every signal carries its
brandId, so route by brand on your side. - Working with an integrator? Create a key and give it to them. Deleting the key stops their access.
Making a Request
Parameters
All parameters are optional.The Response
Each response is one page of signals, oldest change first:Syncing Your Signals
1
Load your history
Call without a
cursor. You get your oldest signals first.2
Store each page, then save its cursor
Upsert the page’s signals, then save its
nextCursor. Saving the cursor last means an interrupted run picks up where it left off.3
Keep calling while hasMore is true
Call again right away with the saved cursor until
hasMore is false.4
Sync on a schedule
Once you’re caught up, keep the cursor and call again later, for example every 15 minutes. Signals from the last few seconds are held back until they settle, so a new signal can take a moment to appear.
Keeping Records Up to Date
- Upsert on
id. Several signal types update the same record when the activity repeats (see How often it fires). An updated signal comes back on a later page with the sameid. That’s expected: update the row you already have. - Key Registered for Event on
consumerCompanyId+eventKey. There’s one record per firm per event, and itsidchanges with each new registrant. UpdateparticipantCountandparticipantsfrom the newest record. - Match firms on
consumerCompanyId, not the firm’s name. It’s stable. - Key projects on
projectId. When a hidden project becomes visible, a later signal carries its name, description and architect. Don’t overwrite a value you already have withnull.
What Isn’t Re-sent
The API sends a signal again when the signal itself changes. A few changes in Acelab don’t change the signals you already received, so nothing is re-sent for them:- A hidden project becoming visible. Signals you received while it was hidden keep their
nullname, description and architect. Only signals recorded after that carry them. - A firm leaving your accounts. When the brand removes a firm, or the firm stops qualifying for leads, the signals you already received from it aren’t withdrawn.
- A project the brand removes. Its earlier signals stay as you received them.
- A signal moved to another brand. If Acelab re-attributes a signal to a different brand, the copy you received under the old brand isn’t withdrawn.
- Account deletions. If a conversation starter or event registrant deletes their Acelab account, their name stays in the records you already synced.
Errors
The
400 messages are text, except the limit validation error, which is JSON.
API Key Expiry
Keys expire one year after they’re created, and an expired key gets a401. An Org Admin can extend a key only after it expires: on My Account → Integrations, click Extend on the expired key. Until then, your sync stops.
After the extension, the same key works again. Your next call with the saved cursor picks up every signal recorded in the meantime.
If your plan stops including API access, all of your organization’s keys expire.
OpenAPI Spec
The OpenAPI 3.1 spec for the endpoint is athttps://signals.acelabusa.com/openapi.json. Import it into your integration tool or API client to get the parameters and response schema.
Related
Signals API Data Dictionary
Every signal type and field the API returns.
CRM Integration
Send signals to your CRM through Zapier instead.

