Reference

Required HTTP Headers

The Content-Type header must be set on every POST. The Accept header is not required, but is recommended.

Responses and Errors

We use HTTP response codes to indicate success or failure of a request.

Response codes in the range 2xx indicate a successful request; 4xx range indicates an error with your request (this could be an invalid Content-Type, missing or invalid parameters, etc), and 5xx range indicates an error on our servers.

Pagination

The Workspace Database Select function has pagination support.

We accept pagination as post parameters. The page parameter denotes the page number, starting from 1. The per_page denotes the number of records shown in each page. This number is 25 if omitted. The maximum is 100.

In order to help navigation, we return a pagination object in the JSON body response with information about pages, like: current page, next page, and total number of pages and records. This information is also returned on HTTP headers.

Lists of items are returned unsorted unless a sort order is explicitly stated in documentation below.

curl -X https://portal.datafeed360.com/api/v1/function/{workspace_id}/call/database.selectdata
     -H "Authorization: Token token={your_token}"

{
  "parameters": {
    "dataId": "WDTBdZnJ0NThRD31q85G",
    "query": [ 
      { "select": "id, title, club_image_id" },
      { "where": { "column": "id", "operator": "=", "value": 3 } },
      { "orwhere": { "column": "id", "value": 2 } },
      { "orderbydesc": "id" },
      { "page": 1 }
    ]
  }
}