Before you start

Droplabs API is organized around REST. Our API requests and responses use JSON format and standard HTTP response codes.

Business background

See our company landing page for the business context: https://droplabs.pl/uslugi/integracje/

Authentication

All endpoints require authentication using the request headers X-Auth-Client-Type, which has to be INTEGRATION, and X-Auth-Token. Contact us at [email protected] to get an Auth Token for your account. 

X-Auth-Client-Type: INTEGRATION
X-Auth-Token: foo-bar
Your API Auth Token is extremely sensitive information. Make sure to familiarise yourself with security best practices around storing and using API secrets. Make sure to never hard-code the API key into source control systems like Git, but extract this information from environment variables instead. Do not expose API keys in frontend code accessible to your customers.

Headers

Please note the additional headers that are sent to the Droplabs API. Requests with additional headers not included in the documentation may result in an error.

We require that you send a User-Agent header with a non-empty value.

Droplabs QR codes

Each ticket has its unique uuid code placed in a QR code in two ways:

  1. Uuid only, e.g. 0a7e1805-e319-49de-a7e9-3c86af7f8d0a
  2. Url address with uuid in a query param, e.g. https://e-bilet.online/facility/201/tickets?uuid=0a7e1805-e319-49de-a7e9-3c86af7f8d0a
The url address can change so please extract the ticket code from the uuid query param.