Updated durch Leigh Hutchens

Getting started

To get started with Quinyx REST API, there are a few things you will need to know.

The framework used for authorisations to the REST API´s is Oauth2. More detailed information can be found here . 

The basic flow for authentication is that a user is given a:

  • uuid - this is an identifier for the set of credentials. This is to be used in communication with Quinyx support if needed.
  • Client id - keep this in a safe place. Can be shared, usually used as a username in applications such as Postman or similar.
  • Client secret - needs to be kept VERY confidential, this is the password and in combination with the Client id gives the owner access to the defined scopes.
  • Link to be able to generate a bearer token to be used for authorisations towards the REST API

Different client id/ client secrets is required for our different environments


To obtain a bearer token a POST call is done towards with the following configuration

Parameter settings (Params):

  • Key = grant_type
  • Value = client_credentials


  • Type = Basic Auth
  • Username = Client id
  • Password = Client secret

examples from Postman



RC is our customer environment (Release Candidate) where you as a customer can access your data in a sandbox environment. It will contain your customer data from the production environment up until last month. The data in this environment gets updated on the evening of the 1st of each month with data from production and that will overwrite all changes made in the RC environment.

Api-docs :

Classic Web Interface:

Neo Web Interface:


This is the production (live) environment which is reached through

Api-docs :

Classic Web Interface:

Neo Web Interface:

Programs for testing

For testing and troubleshooting we suggest using SoapUI or Postman, our example queries and responses are from Postman. If in contact with Quinyx always attach the request and response in .xml , .txt or similar format.


The following limitations currently apply:

  • You are not allowed to use more than 5 concurrent requests (eg. running more than 5 threads simultaneously per unique customer regardless of endpoint).
  • When using GET/calculated-variables/{extCalculatedVarId} we do not currently support the retrieval of calculated variables that include standard variables in their calculation. This will be supported in a future version.

Wie haben wir das gemacht?