Can I Apply Signals or Marketing Data to Multiple Calls Using the Signal API?

Not in a single request — each Signal API request targets one call. You can, however, apply many Signals and Marketing Data fields to that call at once.

​

How the Signal API applies data

1. Call reference — a search object that identifies a single call, using transaction_id, call_record_id, external_call_unique_id, or call_start_time.
2. Signals or Marketing Data — signals and custom_data, each an array of objects.
3. OAuth token — required for authentication, either as oauth_token in the body or in an Authorization header.

POST https://invoca.net/api/2018-02-01/transactions.json HTTP/1.1
Content-Type: application/json
Authorization: <oauth_token>

{
  "search": {
    "transaction_id": "00000000-00000001"
  },
  "signals": [
    {
      "name": "Sale",
      "partner_unique_id": "1",
      "revenue": "100.00",
      "value": "true"
    }
  ],
  "custom_data": [
    {
      "name": "line_of_business",
      "value": "Insurance"
    }
  ]
}

​

Things to keep in mind

• One call per request — search resolves to a single call, so applying data to multiple calls in one request isn’t supported. Send a separate request for each call.
• Batch per call — include every Signal and Custom Data Field for a given call in one request rather than sending them one at a time. Don’t include more than 10 Signals in a single request; if you need more, split them into as few groups of 10 as possible.
• Backlog risk — each added Signal increases the response time of the request, and sending a large burst of requests in a short window can create a processing backlog and delay when data is applied. Requests that exceed the 120-second API timeout return a 504 Gateway Timeout.