Plainrouter API

Use the Plainrouter REST API to send consented conversion events, inspect delivery, run controlled destination tests, and read stored reports. Start with the synthetic sandbox before connecting a production workspace.

Make your first request

Send an identity-free test event without an account or API key.

Authenticate production requests

Use the Signals workspace secret for your server integration.

Connection details

Setting	Value
Base URL	`https://plainrouter.com/api/v1`
Request and response format	JSON; each endpoint documents its schema
Production authentication	`Authorization: Bearer YOUR_SIGNALS_WORKSPACE_SECRET`
Synthetic sandbox	No credential for `/sandbox/events`; a short-lived sandbox key for `/sandbox/keyed-events`
API schema	Published OpenAPI contract
Official clients	TypeScript, Python, Ruby, Go, and CLI

This is Plainrouter’s API, not Meta’s Graph API. Workspace execution tokens used for MCP do not authenticate the Signals REST API.

Make your first request

You need an HTTP client such as cURL. This request validates an invented event without writing a production conversion or contacting Meta. Use only synthetic values; omit personal data and customer identifiers.

curl --include https://plainrouter.com/api/v1/sandbox/events \
  --request POST \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --data '{
    "event_id": "sandbox-order-123",
    "event_name": "Purchase",
    "action_source": "website",
    "value_data": {
      "value": "49.90",
      "currency": "EUR"
    }
  }'

Expect HTTP 200. The response includes these fields; this is an excerpt:

{
  "sandbox": true,
  "accepted": true,
  "status": "simulated",
  "persisted": false,
  "provider_delivery": false
}

accepted: true confirms synthetic validation. It does not test your production credential, store an event, or verify Meta delivery. Continue with the sandbox quickstart to test bearer authentication, check allowed fields, or troubleshoot sandbox keys.

Choose an endpoint group

Group	Operations	Use it to
Sandbox	Discover, issue a sandbox key, validate a synthetic event	Test request shape and client authentication.
Events	Submit, verify ingestion, retrieve, or list events	Send conversions and inspect event and delivery state.
Destination testing	Set test mode and send a controlled test purchase	Check the connected Meta destination. These operations can change state or contact Meta.
Delivery replay	Replay selected eligible failed deliveries	Retry retained payloads after fixing the destination problem.
Reports	Reconciliation and Event Match Quality	Read stored conversion comparisons and matching reports.
Privacy	Delete user data	Request workspace-scoped deletion using the endpoint’s documented identifiers.

Expand a group in the sidebar for its request fields, responses, and examples. Production operations use real workspace data; check each endpoint’s side effects before sending a request.

Move to production

Set up Signals, then configure your server with its Signals workspace secret. Keep credentials out of browser code, prompts, and source control.
Use the identity-free ingestion diagnostic if you only need to check the authenticated write path. It does not verify a real website arrival.
For advertising delivery, connect the intended Meta dataset. Send an actual conversion only with the recorded consent and original event data required by the conversion guide.
Preserve the event ID on retries and inspect the delivery trace. HTTP 202 is ingestion acceptance; destination acceptance is a separate result.

Handle errors and retries

Result	Next step
`401`	Check the credential type, scope, and validity. Sandbox keys and production secrets are not interchangeable.
`422`	Read the field errors and correct the payload before retrying.
New production event: `202`	Read `warnings` and inspect delivery separately.
Duplicate production event: `200`	Keep the original ID. The response does not replay failed delivery.
Uncertain production write after a timeout	Retry the original event ID and payload, subject to continued consent eligibility.

See conversion errors, consent warnings, and sandbox rate limits for the applicable details. Prefer an official SDK when you want typed operations in application code.

Overview

Endpoints

Resources

Make your first request

Authenticate production requests

Connection details

Make your first request

Choose an endpoint group

Move to production

Handle errors and retries

Make your first request

Authenticate production requests

​Connection details

​Make your first request

​Choose an endpoint group

​Move to production

​Handle errors and retries

Connection details

Make your first request

Choose an endpoint group

Move to production

Handle errors and retries