---
title: "POST Postback API v2"
method: POST
path: "/postback/v3/event/{database_name}/{table_name}"
---

# POST Postback API v2

`POST /postback/v3/event/{database_name}/{table_name}`

Send data in POST payload to the v2 Postback endpoint.

Authentication is **header-only**. Provide one of:
1. `Authorization: TD1 <APIKEY>`
2. `X-TD-Write-Key: <APIKEY>`

URL-path keys (`?td_write_key=...`) accepted by the legacy endpoint are **not** supported here. If both headers are sent, `Authorization` takes precedence.

Note: Requests with an invalid API key return a 200 HTTP status code. This behavior is intentional and ensures a fast response, preventing ingestion from being canceled due to slow response. After the response is returned, the endpoint performs asynchronous validations. If the API key is invalid, an authentication failure will be raised despite the initial 200 status.

Maximum request body size is 1,048,064 bytes; larger payloads are rejected with `413`.

## Request body

- object

## Response `200`

Success.

- AllResponse — response for all objects
  - `Content-Type` string
  - `Date` string, date-time
  - `Strict-Transport-Security` string
  - `Content-Length` integer
  - `Connection` string

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `413` — Payload Too Large (request body exceeds 1,048,064 bytes)

---

[API](https://skmtc.net/treasure/apis/postback-api-v2.md) · [All operations](https://skmtc.net/treasure/apis/postback-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/treasure/postback-api-v2/versions/e2831146bf4e/schema)
