Read (GET)

Use the GET method to fetch data from your endpoint.

Use one or more uniqueId’s to fetch specific records from the database. If not specified all records will be returned.

Request data#

HTTP method: GET

URL format: https://baseUrl/versionNumber/customEndpointRoute/userEndpoint?key=apiKey[&uniqueId=uniqueId][&dataOnly=true]


Request Cookies#

yawe_access_tokenThe Access token is required for secure endpoints.

It is obtained when doing a login. To automatically include it in the request you need to set the following property:

// using fetch
{ credentials: 'include' }
// using axios
{ withCredentials: true }

For more information check Secure Endpoints.


Request Parameters#

The following table describes the Request parameters.

baseUrlBase url for calling the API.


versionNumberService version.

Value: The current value is 1.

customEndpointRouteThe route which identifies custom endpoints.

Default value: ce

userEndpointThe endpoint name generated by the user.

Value: the name created at

apiKeyThe API Key of the project.Yes
uniqueIdIf used, the endpoint will only serve the record with a matching uniqueId.

It is also possible to provide multiple uniqueId's.

If none is passed, the endpoint will serve all the records.

dataOnlyIf used, the endpoint will only serve the user data. It won’t include fields such as uniqueId, createdAt, updateAt.

Value: true

masterKeyOverrides the need for Access tokens or restrictions applied to Authentication endpoints.

Don't use this key in your client application.

For more information please refer to projects.

Value: the masterKey created at


Use this parameter to query, filter, sort and transform your data (and more!)

It accepts JSONata compatible expressions.

The evaluation of the expression is applied to the output of the endpoint, including when other parameters are used (e.g. dataOnly).

Check the JSONata documentation on their page, or check our quick guide, JSONata, query and transform.


// With multiple uniqueIds:

Response data#

Error codes#

Error codeDescription
400Possible reasons:
  • Endpoint or API Key not valid.
401If the endpoint is secure and the access token is missing or is not valid.

It may also return this error if the user no longer exists.

403Missing API Key, not allowed origin or disallowed request without orign.

Successful response#

uniqueId: "3f38bf9e1bb54d2396d1f1b8fbba1630",
data: { property: "data" },
createdAt: "2020-12-27T10:58:45.000Z",
updatedAt: "2020-12-27T10:58:45.000Z"

Example of a successful response using dataOnly=true:

"propertyFive": "555"

If the response includes multiple records it returns an Array[] of records:

uniqueId: "3f38bf9e1bb54d2396d1f1b8fbba1630",
data: { property: "data" },
createdAt: "2020-12-27T10:58:45.000Z",
updatedAt: "2020-12-27T10:58:45.000Z"
}, {
uniqueId: "3f38bf9e1bb54d2396d1f1b8fbba1630",
data: { property: "data2" },
createdAt: "2020-12-27T10:58:45.000Z",
updatedAt: "2020-12-27T10:58:45.000Z"