Official APIPre-production

Technical Brief

This page describes the technical structure that exists in the project today: official demo endpoint, pull-based sync, mapping into shared-ID attribution, and the open items for the live step.

Last updated: March 20, 2026

Architecture

The current PU Prime pilot uses a generic HTTP pull adapter. The connector reads a protected JSON response, detects event rows, and hands them into the existing UID and attribution path.

Current Data Flow

text

PU Prime demo endpoint
  -> http-broker-sync
  -> field mapping (sharedId, brokerUid, externalId, occurredAt)
  -> UID checker / tracking attribution
  -> operator review in GramGrow

Endpoint Shape

Important

The current project state intentionally documents the real demo endpoint, not speculative live endpoints from PU Prime.

Pilot Request Shape

http

GET https://api.gramgrow.io/api/v1/demo/brokers/puprime/official-api/report
Authorization: Bearer <private-demo-token>

200 OK
Content-Type: application/json

Current Response Shape

json

{
  "broker": "puprime",
  "mode": "official_api",
  "version": "demo-v1",
  "generatedAt": "2026-03-20T09:39:09.122Z",
  "data": [
    {
      "sharedId": "gg-shared-9f1a2",
      "brokerUid": "PU-48291",
      "externalId": "evt_puprime_0001",
      "eventLabel": "first_deposit",
      "occurredAt": "2026-03-20T09:23:00Z",
      "country": "DE",
      "campaign": "puprime-review"
    }
  ]
}

Field Mapping

This table shows the mapping between the current demo fields and the GramGrow attribution fields.

This mapping documents the real project path today. The final live mapping will only be confirmed once real PU Prime field names are available.

Demo Field	GramGrow	Notes
sharedId	shared_id	Click / shared-ID matching
brokerUid	broker_uid	Broker-side identity
externalId	external_id	Event consistency across imports
occurredAt	occurred_at	Temporal event anchor
eventLabel	event_label	Registration vs. first_deposit
country	country	Review and reporting context
campaign	campaign	Attribution context

Auth & Pull Cadence

Current Project State

The pilot endpoint is token-protected. The token is issued privately. The demo connector is built for scheduled pull operation; the final cadence is configured per workspace.

For the live step, the auth method is not guessed. It will only be mapped once PU Prime confirms its official mechanism.

Required Inputs

The last mile to a live integration is no longer UI work, but real broker material from PU Prime.

Official reporting or partner API documentation
Sample response or anonymized export with real field names
Confirmation of the allowed read-only scope and auth mechanism
Clarification whether the integration is pull-only or if webhook/postback is also possible

Next Steps

Pilot Access Program

Get pilot access

PU Prime Integration

Back to overview