- Print
Create a Tulip Table Query in specified Table.
Requires the table-queries: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 id of a Tulip Table.
The Tulip Table query. All fields must be set.
The ID of the Tulip Table that the query is being created on.
The display label for the query.
The filters that the query uses.
The filters can use any of the columns defined in the Tulip Table (including _createdAt
and _updatedAt
) that the query exists on with any of the functions.
The value to compare to.
If datasourceType
is set to "app-info"
, then params
is not required.
If datasourceType
is set to "static"
, then params
is required.
The static value to compare to. Must be of the same type as the data in the column specified by field
.
The aggregator of all filters defined on the query.
The sorts that will order the records returned by the query.
Sorts are used to order the queries based on columns defined in the Tulip Table where the query exists.
The field that records should be sorted by in the response. Can be the name of any of the columns of the Table (including id
) or one of these special values:
_sequenceNumber
_createdAt
_updatedAt
The direction of the records, either acsending or descending
The number of records that the query returns.
The Tulip Table query was created successfully. The details of the created Table query are returned in the response.
A Tulip Table query that exists on a Tulip Table. The record object will include all the fields of the query, addition to the record's created timestamp and last updated timestamp.
The ID of the Tulip Table that the query exists on.
The name of the Tulip Table Query.
The filters that are applied on this Tulip Table Query.
The filters can use any of the columns defined in the Tulip Table (including _createdAt
and _updatedAt
) that the query exists on with any of the functions.
The value to compare to.
If datasourceType
is set to "app-info"
, then params
is not required.
If datasourceType
is set to "static"
, then params
is required.
The static value to compare to. Must be of the same type as the data in the column specified by field
.
The field and sorting direction used to sort the query results
Sorts are used to order the queries based on columns defined in the Tulip Table where the query exists.
The field that records should be sorted by in the response. Can be the name of any of the columns of the Table (including id
) or one of these special values:
_sequenceNumber
_createdAt
_updatedAt
The direction of the records, either acsending or descending
The number of records that will be returned at most from this Tulip Table query.
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.