Skip to content

Developers

Pulse is API-first. Everything you can do in the app — send data, resolve identities, manage schemas and datasets, build audiences — is available over a hosted REST API, so technical teams can integrate Pulse directly with their own systems.

All requests go to the hosted base URL:

https://api.azothedge.com

Every endpoint lives under the /v1 path, and every request is scoped to your workspace by the API key you send. You never manage servers or infrastructure — you call the hosted API and Pulse does the rest.

A first request

Authenticate with your API key and send an event:

curl -X POST https://api.azothedge.com/v1/collect \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "schema_id": "<your-schema-id>",
    "timestamp": "2026-06-16T10:30:00Z",
    "payload": {
      "personalEmail": { "address": "ada@example.com" },
      "person": { "name": { "firstName": "Ada", "lastName": "Lovelace" } }
    }
  }'

Pulse responds with 202 Accepted and queues the event for processing:

{ "event_id": "01J9Z2K7P0QJ3M8V4N6T2X5R9C", "status": "accepted" }

Explore the developer docs

  • Authentication


    How API keys work, how to send them, and how access is scoped to your workspace.

    Authentication

  • Sending data


    Send events with the ingestion API, validate inline, and link identifiers.

    Sending data

  • API reference


    The full, interactive reference for every endpoint, request, and response.

    API reference

  • SDKs


    Official client libraries are in development — integrate via REST today.

    SDKs

Looking for the concepts?

If you want to understand what Pulse does before you integrate, start with Customer profiles and How identity works.