Creates a new Tulip Table record in the specified Table.
Requires the tables:write API key scope.
Access to the Tulip API requires the use of HTTP Basic Authentication using the credentials of an active Tulip API Token. All requests require the Authorization HTTP header with the Basic scheme to provide API credentials unless otherwise noted.
API tokens can be configured with a set of scopes which determine what parts of the API that specific token has access to. Security best practices dictate that API credentials be given the minimum set of capabilities required to fulfill their intended purpose. For example, an API token created for use in an integration that is only designed to use the Tables API should probably only be given the tables:read and tables:write scopes. In this way you can minimize risk in the event that API credentials are compromised. API endpoints will document what API token scopes are required to access that endpoint in their descriptions. If a request is made to an endpoint with an API token which does not have the required scopes, the response will be an authorization error.
The format that Tulip should use in the response when formatting Tulip numbers. If omitted or set to
float, Tulip will format numbers as JSON numbers. If set to decimal, Tulip will format numbers as strings
representing the decimal representation of the number, like "1.20". Tulip will only output trailing zeros
when using decimal formatting.
This header only affects the response format. The value written is determined solely by the request body (see body description).
Note that this header only affects Tulip numbers. Other types, including Tulip integers, are unaffected.
The id of a Tulip Table.
The spec for creating a Tulip Table record. The object must include the id field, and the other field must match columns in the Table. Any columns not included in the request will be recorded as null.
For Tulip number fields (not integer fields), you may specify values as either JSON numbers or strings. If
specifying numbers as strings, they must be of format "[-]xx[.yyy]". This corresponds to the JSON number
format, except that the exponent component is not allowed (in other words, you cannot use scientific notation).
Numbers specified as strings will be stored with full allowed precision (up to 20 digits to the right of the
decimal place), including trailing zeros. Numbers specified as JSON numbers will not include trailing zeros.
The Tulip Table record was created successfully. The details of the created Table record are returned in the response.
A single record stored in a Tulip Table. The record object will include the names and values of all columns of the Table that are not hidden, in addition to the record's sequence number, created timestamp, and last updated timestamp.
A monotonically increasing unique identifier for this record.
The request was malformed. This could mean that headers, query parameters, or the request body was unable to be parsed or had unexpected values.
The request was made unauthorized. HTTP Basic Authorization using a Tulip API Key is required for use of the API.
The provided authentication info was rejected. The response will provide additional details.
The requested database entry was not found.
The request was syntactically sound, but could not be processed due to a logical problem.
The server encountered an unexpected error.