Cometly API

Name: Cometly API API
Brand: Cometly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct Analyticsbearer10 EndpointsREST

For Agents

Send server-side conversion events, manage contact records, and export attribution data from Cometly with one bearer token.

Quickstart

Get started with Cometly API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a conversion event to cometly"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cometly API API.

Send a single attribution event via POST /events with contact and conversion data

Stream high-volume events via POST /events/batch for server-side tracking pipelines

Create, list, fetch, update, and delete contact records under /contacts

Trigger a data export via POST /exports for warehouse loading

GET STARTED

Start building with Cometly API API

Explore with Jentic

View OpenAPI Document

Use for: I need to send a server-side purchase event to Cometly, Create a Cometly contact record from a new signup, Update the email address on an existing Cometly contact, Batch upload yesterday's conversions to Cometly

Not supported: Does not handle ad creative management, audience targeting, or campaign budgeting — use for server-side conversion tracking and attribution data export only.

Jentic publishes the only available OpenAPI document for Cometly API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cometly API, keeping it validated and agent-ready. Cometly is an ad attribution and tracking platform; its API exposes contact records, event ingestion, and data exports so server-side code can stream conversions, identify users, and pull historical data for offline analysis. Use it to attribute marketing spend to outcomes, send server-side conversion events that survive ad blockers, and export attribution data into a warehouse.

Use Cases

Patterns agents use Cometly API API for, with concrete tasks.

★ Server-Side Conversion Tracking

Send purchase, signup, or lead events from a backend service to POST /events so attribution survives ad blockers and Safari ITP. Each event carries the contact reference plus conversion value, letting Cometly tie revenue back to the original ad click. Reliable for Shopify checkouts, Stripe webhooks, and CRM-triggered events.

POST a purchase event to /events with contactId, value 49.99, currency USD, and event_name 'purchase'

Bulk Backfill of Historical Conversions

When onboarding to Cometly, replay months of historical orders through POST /events/batch so the attribution engine can rebuild lookback windows. Batch ingestion accepts arrays of events in a single request, reducing rate-limit pressure compared with one-by-one POSTs.

POST a batch of 500 historical purchase events to /events/batch and return the count accepted

Warehouse Export Pipeline

Trigger POST /exports to dump attribution data into the warehouse on a schedule, then poll GET /exports/{exportId} until the status is ready and download the resulting file. This gives BI tools and downstream MMM models a clean source of truth that combines Cometly's attribution with internal revenue data.

Create an export with date_range last_30_days, poll until status is complete, and return the download URL

AI Agent Attribution Reporter via Jentic

An AI agent connected to Jentic can answer 'how much revenue did Meta drive last week?' by triggering a Cometly export, polling for completion, and summarising the results — all without raw API key exposure. Jentic stores the bearer token in MAXsystem and returns only execution results to the agent.

Use Jentic to search 'send a conversion event to cometly', load the operation, and execute with a sample purchase event

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for cometly api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/events

Send a single attribution event

POST

/events/batch

Send a batch of events

POST

/contacts

Create a contact

GET

/contacts

List contacts

PUT

/contacts/{contactId}

Update a contact

POST

/exports

Create a data export

GET

/exports/{exportId}

Get export status and download URL

POST

/events

Send a single attribution event

POST

/events/batch

Send a batch of events

POST

/contacts

Create a contact

GET

/contacts

List contacts

PUT

/contacts/{contactId}

Update a contact

POST

/exports

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cometly bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents call operations via Jentic and the raw key never appears in the agent's context window or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a conversion event to cometly') and Jentic returns the matching operation with its full input schema, so the agent calls the right endpoint without browsing Cometly docs.

Time to first call

Direct Cometly integration: half a day for auth, payload shape, and retry handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hyros API

Hyros offers a similar server-side ad attribution API with its own tracking model.

Choose Hyros when an existing customer relationship or specific channel coverage favours it; choose Cometly when working inside the Cometly attribution model.

Alternative

Northbeam API

Northbeam is a multi-touch attribution platform with a comparable conversion ingestion API.

Choose Northbeam for incrementality and MMM-style reporting; choose Cometly for direct event-based attribution and exports.

Complementary

Segment API

Segment routes raw event streams to many destinations; Cometly is one possible attribution destination.

Use Segment to fan out events to multiple analytics tools and use Cometly when attribution is the specific concern.

FAQs

Specific to using Cometly API API through Jentic.

Why is there no official OpenAPI spec for Cometly API?

Cometly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cometly via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cometly API use?

Cometly uses a bearer token in the Authorization header. Through Jentic the key is stored encrypted in the MAXsystem vault and never enters the agent context — the agent only receives the response of the operation it called.

Can I send conversion events from the server side with the Cometly API?

Yes. POST /events accepts a single conversion event and POST /events/batch accepts an array of events for bulk ingestion. Both expect a contact reference and the conversion attributes (event_name, value, currency).

What are the rate limits for the Cometly API?

Cometly does not document a hard public rate limit; in practice, single-event POSTs above a few hundred per minute should move to /events/batch. Expect 429 responses at extreme volume and back off.

How do I send a conversion event through Jentic?

Search Jentic for 'send a conversion event to cometly', load the schema for POST /events, and execute with the contact reference and event details. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).

Can I export Cometly attribution data to a warehouse?

Yes. POST /exports creates a data export job, GET /exports lists exports, and GET /exports/{exportId} returns the status plus a download URL once the export is complete. Schedule this from a warehouse loader to refresh attribution data nightly.