# POST Postback API Send data in POST payload. Every request must contain authentication information. Authentication can be provided in two ways: 1. In header with the X-TD-Write-Key: format 2. In URL Path with the ?td_write_key= format Note: Requests made 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. In case both header and URL parameter are provided, the header takes precedence. Endpoint: POST /postback/v3/event/{database_name}/{table_name} Version: 1.0.0 ## Path parameters: - `database_name` (string, required) Name of the database the table is in. Name may contain letters, numbers or _ . - `table_name` (string, required) Name of the table to log data to. Name may contain letters, numbers or _ . ## Header parameters: - `X-TD-Write-Key` (string, required) Example: "12345/abcdef" ## Response 200 fields (application/json): - `Content-Type` (string) Example: "application/json" - `Date` (string) Example: "Wed, DD MM YYYY xx:yy:zz GMT" - `Strict-Transport-Security` (string) Example: "max-age=31536000" - `Content-Length` (integer) Example: 2 - `Connection` (string) Example: "keep-alive" ## Response 400 fields (application/json): - `Content-Type` (string) Example: "application/json" - `Date` (string) Example: "Wed, DD MM YYYY xx:yy:zz GMT" - `Strict-Transport-Security` (string) Example: "max-age=31536000" - `Content-Length` (integer) Example: 2 - `Connection` (string) Example: "keep-alive" ## Response 403 fields (application/json): - `Content-Type` (string) Example: "application/json" - `Date` (string) Example: "Wed, DD MM YYYY xx:yy:zz GMT" - `Strict-Transport-Security` (string) Example: "max-age=31536000" - `Content-Length` (integer) Example: 2 - `Connection` (string) Example: "keep-alive"