Webhook In: POST records straight into a table — The format is published, not guessed

The endpoint's page writes out the exact body to send — a real example built from the table's live schema, with a copy button and a ready-made curl line. It is one JSON object: an optional displayName (left out, the record is named after the first field's value, the same convention as the grid) and a values object keyed by field key. It is the same envelope as POST /api/v1/tables/{id}/records, so a sender that outgrows the endpoint moves to the REST API without reshaping its payload. Bad payloads are refused loudly: a 400 with a problems list naming each unknown key, unwritable field or malformed date — and nothing partial is stored. A retried POST carrying an Idempotency-Key header replays the original answer instead of filing twice.