The dailys API is organised around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors.

We use HTTP verbs, which are understood by most HTTP clients. We support cross-origin resource sharing, allowing you to interact securely with our API from a client-side web application (though you should never expose your secret API key in any public website's client-side code). JSON is returned by all API responses, including errors.

Our example requests through-out the documentation are designed to work as is. If you want to test the API, feel free to sign up for another account and use that for trialing the API. All accounts have a 90-day free trial, providing you with a comfortable period to get familiar with the API capabilities.

To get started using the API, take a look at the Application Flow section on how to get a access_token or a client_id/client_secret pair.

Getting Started

For testing and development using the dailys API, we recommend using Postman to test each endpoint to ensure you are getting the expected responses before production implementation.


Download Postman

Request Headers

Dailys requires that all requests will be made as RESTful JSON HTTP requests, and as such will require the following headers.

Header Value Description
Content-Type application/json Setting the content type ensures the server knows the cotent type of your request.
Accept application/json Setting the accept request ensures the server knows what the request is expecting in the response.
Authorization Bearer ... Authorisation is required for all Administration and Resources requests, to identify the user making the requests.