Skip to main content
POST
Create record
Use field names or field IDs as keys and field values as data (e.g., "Email": "user@example.com" or "fwtJyga6dso": "user@example.com")
By default, a select value that matches no option is stored without being added to the field’s options (a multiple select drops it when other values do match), and a number that can’t be parsed is stored as empty. Set "strict": true to reject those values instead. If an attachment URL can’t be stored, the record is still written without it, and the response lists the failure in attachmentErrors.

Authorizations

Authorization
string
header
required

Enter your Zite API key. Format: Bearer <api_key>

Path Parameters

databaseId
string
required

The unique identifier of the database

tableId
string
required

The unique identifier of the table.

Body

application/json
record
object
required

Record data with field names or field IDs as keys and their corresponding values

Example:
strict
boolean
default:false

Reject values the write would otherwise coerce: select values that match no option (by default they are stored without being added to the field's options) and unparseable numbers (stored as empty by default).

Response

Record created successfully

id
string<uuid>
required

Unique UUID identifier for the record

data
object
required

Record data with field IDs as keys

Example:
fields
object
required

Record data with field names as keys

Example:
createdAt
string<date-time>
required

ISO timestamp of when the record was created

updatedAt
string<date-time>
required

ISO timestamp of when the record was last updated

attachmentErrors
object[]

Present when one or more attachment URLs could not be stored.

attachmentErrorsTruncated
boolean

Set to true only when more URLs failed than attachmentErrors lists.