Skip to main content
POST
https://api.amplemarket.com
/
custom_signals
/
{token}
/
entries
Create Custom Signal Entry
curl --request POST \
  --url https://api.amplemarket.com/custom_signals/{token}/entries
{
  "status": 123
}
Send data from any external tool (Zapier, Clay, RB2B, your own app, etc.) into Duo Copilot via a webhook. Whenever new data arrives, Duo generates a signal and can automatically create personalized sequences for each lead.

​
Authentication

This endpoint uses a token-based URL instead of the standard API key authentication. Each custom signal has a unique token embedded in its webhook URL. You can find your token in the Duo Copilot signal settings.
Treat your webhook URL as a secret — anyone with the URL can send data to it. Avoid sharing it publicly or committing it to repositories.

​
Path Parameters

​
token
string
required
The unique token for your custom signal. Found in the Duo Copilot signal settings.

​
Request Body

The request body is a dynamic JSON object. You can send any fields that are relevant to your use case — there is no fixed schema. After sending a test request, Amplemarket will auto-map your fields to the identifiers it needs to look up each person or company.

​
For people signals, include at least one of:

FieldDescription
linkedin_urlLinkedIn profile URL
emailEmail address
full_name + company_namePerson name combined with company name or domain

​
For company signals, include at least one of:

FieldDescription
company_nameCompany name
company_domainCompany domain
company_linkedin_urlCompany LinkedIn URL
You can include any additional fields (e.g. pages_visited, form_responses, use_case) that you want Duo to use as context for AI personalization.
Nested objects are supported — Amplemarket will flatten them into dot-notation paths (e.g. person.name, company.domain) for field mapping.

​
Response

​
status
number
HTTP status code.
StatusMeaning
202 AcceptedRequest received successfully
400 Bad RequestMalformed JSON, empty body, or non-object payload
404 Not FoundInvalid webhook token
413 Content Too LargePayload exceeds 1 MB
Test data vs. live data: During initial signal setup, requests are treated as test data for configuring field mappings — no leads are generated. Once the signal is saved, all subsequent requests generate real leads.