Looks up a Tulip Table record by id.
Requires the tables:read 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.
Note that this header only affects Tulip numbers. Other types, including Tulip integers, are unaffected.
The id of a Tulip Table.
The id of a Tulip Table record.
Specifiying fields allows to reduce the amount of data returned in the result to just the data for each of the fields specified. If ommitted, all fields for a given record will be returned. A field value that is not one of the table's fields will generate a 422 error.
Example: ["ipwkk_weight", "cyveu_completed", "id", "_updatedAt", "bDabBK8jmxZqWY8iT_link_left_column"]
A list of fields of the record that should be fetched. If an empty list is given, or if the query parameter is left out, all fields will be returned.
If specified along with the fields query parameter, a 422 error will be returned.
This parameter is deprecated and will be removed in a future version - please use the fields query parameter instead.
The Tulip Table record was retrieved successfully.
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 malformed. This could mean that headers, query parameters, or the request body was unable to be parsed or had unexpected values.
The server encountered an unexpected error.