Getting started with the API

An API token allows you to authenticate with the Quenza API and access your workspace data programmatically.

This makes it possible to build custom integrations, retrieve data, or interact with Quenza from your own applications or scripts.

API tokens are intended for developers or technically experienced users who want to connect Quenza with external systems or build custom solutions.

What is an API token?

An API token is a unique key that identifies you when making requests to the Quenza API.

Instead of using your email and password, the token is sent with each request to verify your identity and grant access to your workspace.

Examples of how an API token can be used

Build a custom integration

Use the Quenza API to connect your workspace with an internal system or custom application your organization uses.

Create clients automatically

Automatically create a client in Quenza when something happens in another system - such as a new contact being added to your CRM, a form submission, or a purchase being completed.

Retrieve workspace data

Pull data such as client information or activity results into your own dashboard or reporting tool.

Automate workflows

Trigger actions in Quenza programmatically as part of a larger automated workflow.

Creating an API token

To create an API token in Quenza:

Go to Developer Tools
Click API Token
Click Generate

Your token will be displayed once. Make sure to copy and store it in a safe place - it will not be shown again.

Using the API token

The Quenza API uses Bearer token authentication.

Include your token in the Authorization header of every API request:

Authorization: Bearer YOUR_API_TOKEN

Full API documentation, including available endpoints and request examples, is available at developers.quenza.com.

Managing your API token

You can view and regenerate your API token at any time from the API Token section in Developer Tools.

If your token is no longer needed or may have been compromised, regenerate it immediately. Keep in mind that regenerating your token will invalidate the old one. Make sure to update it in any integrations or applications where it was being used.

Keep your token safe

Your API token provides access to your workspace. Treat it like a password:

Do not share it with others
Do not include it in publicly accessible code or repositories
Regenerate it if you suspect it has been exposed

Do I need a developer?

Not necessarily.

While working directly with the Quenza API requires technical knowledge, tools like Zapier or Make allow you to connect Quenza with other systems using a visual interface - no coding required.

If you are a developer, you can find the full API documentation at developers.quenza.com.

If you are unsure how to get started, we recommend reaching out to the system's developer or service provider or contacting Quenza Support.