REST · JSONOAuth 2.0 client credentialsCursor paginationWebhooksRate-limited per plan
Authenticate
curl https://api.coreforge.example/v1/audiences \ -H "Authorization: Bearer $COREFORGE_API_KEY" \ -H "Content-Type: application/json"
Issue scoped keys per workspace. Rotate from /settings/api. All requests are TLS-only.
Create an audience
POST /v1/audiences
{
"name": "in-market Q3",
"prompt": "Mid-market logistics, US, hiring ops",
"filters": { "region": ["US"], "size": "20-200M" },
"refresh": "4h"
}Endpoints
| GET | /v1/audiences | List audiences in the workspace. |
| POST | /v1/audiences | Create a new audience from a prompt + filters. |
| GET | /v1/audiences/{id}/members | Stream audience members with explainable scores. |
| GET | /v1/signals/{account_id} | Return the per-signal breakdown for an account. |
| GET | /v1/lineage/{record_id} | Return source, license, refresh, and permitted-use metadata per field. |
| POST | /v1/activations | Push an audience to a connected destination. |
| GET | /v1/consent/{contact_id} | Return the consent ledger for a contact. |
Webhooks
Subscribe to audience.refreshed, signal.score.changed, consent.updated, and activation.completed. Payloads include lineage references for replay.
Documentation is in active development. Full OpenAPI spec available to design partners.