/api/v1/object/data/{objectSlug}/inlineCreate a record from a quick-add row in a table or board.
Create a record from a quick-add row in a table or board.
A lighter create: data is keyed by field slug, and only fields that can
be edited inline are kept; the others are dropped and listed in
dropped_fields. group places the record in a board column: the field
named by group.field_slug gets group.value, the column's option id,
whatever data says. The record is recorded as created inline, so fields
marked API-only are dropped even with an API key. The response is the new
record, in the same shape as POST /object/data/{objectSlug}.
Scope: create.<object slug>, for example create.contacts.
Errors:
400—group.field_slugis not a field of the object (code: GROUP_FIELD_NOT_FOUND) or cannot be set inline (code: GROUP_FIELD_NOT_WRITABLE), or a value fails validation.409— another record already has the same value in a unique field.422— the body is invalid, for exampledatais missing.
Request:
{
"data": { "title-mpoc3dn1": "Follow up with Acme" },
"group": {
"field_slug": "stage-k2j9h4g7",
"value": "6a1f3c9e-2b7d-4e8a-9f0c-1d2e3f4a5b6c"
}
}
Response 201 (abridged):
{
"status": 201,
"message": "Record created successfully",
"data": {
"title-mpoc3dn1": "Follow up with Acme",
"stage-k2j9h4g7": [
{
"id": "6a1f3c9e-2b7d-4e8a-9f0c-1d2e3f4a5b6c",
"value": "lead",
"label": "Lead",
"color": "#3B82F6",
"icon": null
}
],
"name": "Follow up with Acme",
"slug": "4d9a1c6e0b53",
"relations": {},
"createdAt": "2026-09-14T10:00:00.000Z",
"updatedAt": "2026-09-14T10:00:00.000Z"
}
}
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Request body
application/jsonrequiredResponses
Successful response
{
"dropped_fields": "string",
"warnings": "string",
"message": "string",
"data": "string"
}Bad request
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Unauthorized
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Internal server error
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Powered by heyo-docs