Hanzo

Destination

Package destinations is your events forwarded to the ad and analytics tools you use.

Package destinations is your events forwarded to the ad and analytics tools you use.

Base URLhttps://api.hanzo.ai
Operations5
AuthAuthorization: Bearer $HANZO_API_KEY

Specification

Specification pending — no HIP in hanzoai/hips declares capability: destination yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.

Four surfaces

SurfaceReaches this capability asCoverage
RESTdestination at its own prefix5 operations
CLIhanzo destinations …5 of 5
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool destinations on https://api.hanzo.ai/v1/mcp5 operations, 1 under the document's own id — ask describe for the rest

Quickstart

export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/destination, operation get_destination:

hanzo destinations list

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
POST /v1/destination/{platform}/testSends ONE synthetic pageview through the connected destination end to end and reports what the platform said.
GET /v1/destination/{platform}Reports one destination's card for the caller's org — its config fields, its connection state, and whether a credential resolves right now.
POST /v1/destination/{platform}Connect one conversion destination for your org, or update the one you have
DELETE /v1/destination/{platform}Forgets a destination for the caller's org: every credential held in KMS, then the stored config.
GET /v1/destinationReports every destination this deployment can forward to, each with the caller org's connection state: whether it is connected, whether it is…

All Hanzo APIs · Interactive reference

How is this guide?

On this page