Campaigns in a connected tool
The campaigns in your account of that tool, so you can pick where people go. Archived campaigns are left out. Use the id as target_campaign_id when you send.
| Cost | What it does | Key scopes |
|---|---|---|
| Free | Reads only | argorant:read_counts |
Authorization
BearerAuth AuthorizationBearer <token>
Your API key from app.argorant.com/profile, sent as Authorization: Bearer <key>. A connector sign-in token (ag_mcp_...) works the same way.
In: header
Path Parameters
integration_id*integer
The connected tool's id from GET /api/v1/integrations.
Header Parameters
X-Request-Id?string
Your own id for this request, 8 to 64 letters, digits, dot, dash or underscore. Returned as X-Request-Id; one is made for you when you send none.
Match
^[A-Za-z0-9._-]{8,64}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
Shell
curl -X GET "https://app.argorant.com/api/v1/integrations/18/campaigns"JSON
{ "integration_id": "18", "tool": "sending_tool", "campaigns": [ { "id": "3356753", "name": "Q4 CFO follow-up", "status": "DRAFTED" } ]}