Skip to main content

First-party event API

SpendDaddy exposes a lightweight API at api.spenddaddy.app for attribution events from your app backend or SDK gateway.

Base and auth​

All requests use Authorization: Bearer <public_api_key>.

POST /identify​

Send install context when an app user is first seen.

{
  "appUserId": "user_123",
  "installedAt": "2026-06-29T12:34:56Z",
  "asaToken": "optional_asa_attribution_token"
}

Response:

{
  "status": "identified",
  "created": true,
  "attribution": "fetched"
}

If no attribution token is provided, SpendDaddy still stores install timing and marks attribution as not yet resolved.

POST /event​

Send conversion/revenue events that are not already being captured by webhooks.

{
  "appUserId": "user_123",
  "eventType": "trial_started",
  "occurredAt": "2026-06-29T12:40:00Z",
  "eventId": "evt_01",
  "productId": "monthly_pro"
}

Supported event types: trial_started, trial_converted, initial_purchase, non_renewing_purchase, renewal, refund, cancellation.

Key rules​

  • Send event type values in the documented shape above.
  • Amount for refund events must be sent as a positive value; SpendDaddy applies the refund sign internally.
  • This endpoint is additive and runs against the app selected for the key.

Rotation​

Rotate first-party public API keys with POST /api/private/apps/{app_id}/first-party-key/rotate in the authenticated private SPA/API flow. The API key is shown once on creation and then stored as a hashed secret.