Perform Simple and Compound queries
Powerful query functionality for specifying which documents you want to retrieve from a Collection
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The Name of the Collection or the Group where you want to store all your data.
The Queries that you want to run on the Collection. You can run a simple WHERE query or a compound AND or OR using the join query parameter on a Collection.
The Compounding Operator that you want to run the query with. This is optional. By default we will run the query with the and operator if you pass multiple queries. If you add a compounding parameter, we will run the query with that Compounding Operator.
and, or The Field/Key that you want to sort the response by. This is optional. By default we will sort it by the Field/Key that you pass in as default orderBy value when collection was created. If you add a orderBy Field/Key, we will sort the response by that Field/Key.
The Order Type that you want to sort the response by. This is optional. By default we will sort it in asc order. If you add a orderType Field/Key, we will sort the response by that Order Type on the orderBy Field/Key.
asc, desc The Limit of the number of Documents that you want to fetch. This is optional. By default we will fetch all the Documents that match the query. If you add a limit Field/Key, we will limit the response by that number.
The number of documents to skip. This is optional. By default we will not skip any documents. If you add a startAfter value, we will skip the number of documents that you pass in.
The type of output you want. json will return the data as a JSON object that is parseable. stream will return the data as a stream of data and file will return the data as a parseable CSV file.
json, stream, file Response
Status indicating the success of the text moderation.
The time taken to process the request, in milliseconds.
A universally unique identifier for the request. This can be used to track the request in the logs.
The number of times the request has been processed. This is what is considered in the Billing Process. This is either the number of times the image is processed or the number of words that the server processes.
Was this page helpful?