Zapier + C2

Publish strategy signals through Collective2 API4.

Code flowing between connected systems

Use Webhooks by Zapier

There is no dedicated Collective2 app to install in Zapier. Instead, use Webhooks by Zapier to call API4 directly. This guide is for a Collective2 strategy manager who wants a Zap to publish trading signals into a strategy. It is separate from white-label billing automation.

The important detail is authentication: the key from collective2.com/apikey goes in an Authorization: Bearer request header. It does not go in Zapier’s Basic Auth field or in a legacy apikey field.

1. Create a dedicated API4 key

  1. Sign in to Collective2 and open Get your API4 key.
  2. Create a key with permission to manage your strategies. Give it a recognizable name such as Zapier signals.
  3. Copy the key and keep it private. Anyone holding it can use the permissions you assigned to it.

2. Add the webhook action

  1. Build your Zap and choose the trigger that should create a C2 signal.
  2. For the action, choose Webhooks by Zapier.
  3. Choose Custom Request. A C2 signal uses nested JSON and custom request headers.

3. Configure the request

Method POST
URL https://api4-general.collective2.com/Strategies/NewStrategyOrder
Data Paste the JSON body shown below. Replace the strategy ID and map any values supplied by your Zap trigger.
Basic Auth Leave this blank.
Headers Authorization   Bearer YOUR_API4_KEY
Content-Type   application/json 
{
  "Order": {
    "StrategyId": 123456789,
    "OrderType": "1",
    "Side": "1",
    "OrderQuantity": 1,
    "TIF": "0",
    "ExchangeSymbol": {
      "Symbol": "IBM",
      "Currency": "USD",
      "SecurityType": "CS"
    }
  }
}
Testing is live. Zapier’s Test step sends the request to Collective2 and can publish a real signal. Use a strategy created for testing, confirm its strategy ID, and review the order before you run the test.

A successful response includes a C2 signal ID. Open your strategy in Collective2 and confirm the signal before turning on the Zap.

Troubleshooting

Key rejected or unauthorized Confirm that the header name is Authorization and its value begins with Bearer , including the space. Do not add quotation marks, use Basic Auth, or send the key as apikey.
Old submitSignal URL An API4 key is not a replacement for the credential used by an old APIv2 or APIv3 example. Use the API4 URL on this page for a new integration.
Bad request or invalid JSON Use Custom Request, send JSON, and keep the outer Order object. Check that Zapier has not flattened the nested fields.
Strategy not allowed Verify that the strategy ID belongs to the signed-in strategy manager and that the key has permission to manage strategies.

Reference