Jump to a popular page, or start typing.

    CONNECTIONS / Datahash API

    Datahash API: post events from your backend to every ad platform.

    Send server-side events to Signals over a documented REST API from any backend, in any language. Signals hashes the identifiers, validates each payload, and delivers the conversions to Meta, Google, TikTok, and Snap, with no pixel and no warehouse read.

    datahash-api :: live

    1. ● datahash-api :: signals live
    2. > POST /v1/events type=purchase value=214.00
    3. > 202 accepted id=evt_9f2a
    4. hash sha256(email,phone) server-side
    5. route meta · google · tiktok · snap
    6. ✓ forwarded · match 82%
    WHAT FLOWS THROUGH DATAHASH API

    The signal Datahash API yields, and receives.

    Every kind of signal that moves between Datahash API and the platforms, through one hashed, deduplicated route.

    What flows Every platform Offline conversions Lead conversions Custom audiences Lead generation Signals hash · dedupe· route Google Meta Snap TikTok LinkedIn OpenAI
    Offline conversions
    Every event type, a purchase, a lead, or a custom action, posts to one documented endpoint, and schema validation rejects a malformed event instead of failing the batch.
    Lead conversions
    Emails and phone numbers are SHA-256 hashed the moment an event is received, or you send them pre-hashed, so no plaintext identifier is ever stored.
    Custom audiences
    The client examples show how to batch and retry, so a backend can post events in near real time or in periodic groups without losing any.
    Lead generation inbound
    Every request appears in the live debugger with its full payload and per-destination status, so a failed match is visible at the exact event that caused it.
    USE-CASE LISTING

    Pick your platform. Every use case for it, in one place.

    Every way Datahash API data moves, grouped by platform and ranked by how many use cases Datahash API supports.

    Google 5 Meta 4 Snap 4 TikTok 4 LinkedIn 3 OpenAI 1
    HOW IT CONNECTS

    From authorization to delivered signal.

    1. Create a key

      Create an API key in the Signals console.

    2. Send

      Send a test event from your backend following the API reference.

    3. Map

      Map custom fields to the signal schema if needed.

    4. Go live

      Verify events in the live debugger and go live.

    FAQ

    Datahash API questions, answered.

    Which languages are supported?

    Any language that can make an HTTPS request works, since the API is a documented REST endpoint that takes JSON payloads. Examples cover common backend stacks, and because there is no SDK to install, a service written in Go, Python, Node, or anything else posts events the same way and reaches every mapped ad platform.

    Is customer PII stored by Datahash?

    Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, so only hashed values are matched to a platform. You can also send values pre-hashed, and a self-hosted Core deployment is available when data cannot leave your perimeter, in which case hashing happens inside your own environment.

    How are failures handled?

    Every request returns a clear status code, and the live debugger shows validation errors per event, so a retry can target only the events that failed rather than resending a whole batch. Schema validation catches a malformed payload before it reaches a platform, so one bad event never blocks the rest of the request.

    NEXT STEP

    See your Datahash API data working in every ad platform.

    Ready to enable a use case, or still mapping what Datahash API data could do? Our team helps you find the right place to start.