Documentation
Protocol reference

Protocol reference

Reference for the FounderHQ Events protocol.

Every FounderHQ SDK speaks one capture protocol. This section documents it, so you can build your own client, debug a payload, or hand the contract to an AI agent.

Most people skip this section

If you install an SDK, the protocol is already handled. Go to Getting started instead.

Pages

PageRead it to
Wire protocolSee the exact request, the exact response, and what each result status means.
Event taxonomyLook up the reserved $ names FounderHQ owns, so your own names never collide.
JSON SchemaDownload the schema and validate a payload before you send it.
Conformance suiteUnderstand why all five SDKs produce the same numbers.

The short version

  • One endpoint: POST /i/v2/e.
  • One credential: your publishable key, as Authorization: Bearer.
  • One body shape: { "sent_at": "...", "batch": [...] }, up to 100 events.
  • One result per event UUID: ok, warning, drop, or retry.
  • One property namespace. There is no context object.

Server-side capture is a different surface. It uses a secret key and the API reference endpoints.

AI agent or LLM? Read this page as markdown

On this page