# Record custom events from your server (shape-only: a name, a time, IDs and tags)

`POST /api/v1/events` · operationId `recordCustomEvents`

For developers: your server sends this request with a server key; it is not a button in the dashboard.

Counted per day, per account and month; never a message, parameters or payload: unknown fields are refused. A resent eventId is a replay. See [Custom events, tags and debug mode](/docs/custom-events).

## Authentication

Send `Authorization: Bearer YOUR_SERVER_KEY` (siteServerKey: Site server key in Authorization: Bearer <key> (the scheme is case-insensitive and required; a bare key is 401). Shown once on creation or rotation. Publishable keys cannot authenticate). Keep the server key in server-only configuration; never send it to a browser.

## Request body

Content-Type: application/json (required)

- `sdk` (object, optional)
- `sdk.name` (string, required)
- `sdk.version` (string, optional)
- `events` (object[], required)
- `events[].eventId` (string, required) · pattern `^[A-Za-z0-9_-]{8,128}$`
- `events[].name` (string, required) · pattern `^[a-z][a-z0-9_.]{0,63}$`
- `events[].at` (integer, required)
- `events[].accountId` (string, optional) · maxLength 512
- `events[].userId` (string, optional) · maxLength 512
- `events[].channel` ("server" | "mcp" | "api", optional)
- `events[].tags` (object, optional): Categories only: keys that suggest personal data or secrets, identifier-like values and free text are dropped and counted in tagsDropped.

```json
{
  "events": [
    {
      "eventId": "event_00000001",
      "name": "report_exported",
      "at": 1762300800000,
      "accountId": "acct_456",
      "userId": "usr_123",
      "tags": {
        "format": "csv"
      }
    }
  ]
}
```

## Responses

- **200**: Success · body `object`
- **400**: bad_request: the request is invalid; message says what to fix and field names the request field · body `Error`
- **401**: unauthorized (missing or invalid server key, missing Bearer scheme) · body `Error`
- **403**: forbidden: the call came from a browser page or another Site; call from your server with this Site’s server key · body `Error`
- **404**: not_found: unknown path, or an ID in the path that is not on this Site · body `Error`
- **409**: conflict: an eventId was already used with a different name or time · body `Error`
- **413**: payload_too_large: the request body exceeds 131072 bytes · body `Error`
- **429**: rate_limited: wait for Retry-After · body `Error` · headers `Retry-After`
- **500**: internal_error: fail the protected action; do not retry automatically · body `Error`
- **503**: service_unavailable: temporarily unavailable; only verify retries · body `Error`

### Success body fields

- `accepted` (integer, required)
- `replayed` (integer, required)
- `tagsDropped` (integer, required)
- `rejected` (object[], required)
- `rejected[].index` (integer, required)
- `rejected[].field` (string | null, required)
- `rejected[].error` (string, required)

Failures are not verdicts. Error bodies follow the `Error` schema: `code` is one of `bad_request`, `unauthorized`, `session_reinit_required`, `forbidden`, `not_found`, `conflict`, `identity_required`, `payload_too_large`, `rate_limited`, `internal_error`, `service_unavailable`, `request_failed`, `approval_invalid`, `approval_used`, `approval_expired`, `approval_mismatch`, `step_up_not_held`, `step_up_mismatch`, `step_up_settled`, `step_up_expired`, `step_up_superseded`, `agent_tokens_disabled`, `tool_not_approved`, `tool_not_read_only`. [Errors and retries](/docs/errors) explains each code and what to do.

## Example

```sh tab=curl
curl -sS -X POST 'https://app.trytelltale.dev/api/v1/events' \
  -H "Authorization: Bearer $TELLTALE_SERVER_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"events":[{"eventId":"event_00000001","name":"report_exported","at":1762300800000,"accountId":"acct_456","userId":"usr_123","tags":{"format":"csv"}}]}'
```

```js tab=fetch
const response = await fetch("https://app.trytelltale.dev/api/v1/events", {
  method: "POST",
  headers: {
    Authorization: 'Bearer ' + process.env.TELLTALE_SERVER_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "events": [
      {
        "eventId": "event_00000001",
        "name": "report_exported",
        "at": 1762300800000,
        "accountId": "acct_456",
        "userId": "usr_123",
        "tags": {
          "format": "csv"
        }
      }
    ]
  }),
  signal: AbortSignal.timeout(5000)
});
const result = await response.json();
```

Machine-readable contract: [openapi.json](https://app.trytelltale.dev/openapi.json). Request builder: the [API explorer](/docs/api-explorer) shows every operation as curl; it sends requests only on a local dashboard.