HTTP API

One POST. Anything that can make a request can be a source.

Take the write key

Everything this install sends is tagged with it, so one key per environment keeps staging out of your production numbers.

Generating…

Install

Nothing to install — the change is configuration.

No package needed

Add it to HTTP API

Paste this where the request path is assembled. The account callback is the only part you have to fill in — it is what turns a request into a customer.

bash

curl https://ingest.clearplane.com/v1/events \
  -H "X-Write-Key: WRITE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account": "acct_9f2",
    "event": "api.request",
    "properties": { "route": "/v1/charges", "status": 200, "ms": 41 }
  }'

Name this install

Name it for the deployment rather than the framework. Two Next.js apps in one workspace is the normal case, and “Next.js” twice helps nobody.

Name

Environment

Events land in events_http_api and are queryable from Chat, models, and SQL.