API is a very good way of preforming various actions on Quicklizard, you either update data or get data using our different API endpoints.
Each API endpoint has its own uses and therefore requires different queries, but there are repetitive information that should be passed in any request to validate and verify to which account it belongs.
- API key
- API secret
- Client key
- QTS
- Channel key (for omnichannel systems)
The API key and API secret, generated by quicklizard, serve as a key combination for our system to authenticate requests and verify the requester's approval to access the quicklizard API.
The client key uniquely identifies your system within our platform.
If your system is omnichannel, ensure to include the channel key as the identifier for the specific channel. QTS, representing the timestamp of your request, must be within the last 3 minutes. The value to be passed is the current UTC Unix timestamp in seconds.
For each usage of the API, you will need these credentials. You can find them by using the manual Where can I find my client Key and Channel Key?
Now after you have all the data you are ready to get started using our different api endpoints. you can read all about them here
Note: A good thing to know is that API usage has a limit enforced on it of 100 calls per minute, in order to prevent abuse of the system, when exceeding it your calls will fail with http status of 429. To read more about it see our article API rate limitation
Comments
0 comments
Please sign in to leave a comment.