Skip to main content

​
Partner Integrator, welcome!

If you’re reading this topic, it means you’ve already been through some challenges with us, right? We are extremely pleased that you consider being a partner integrator. Now that you’ve reached 10 instances, we know each other well and our partnership is even stronger.

​
Integrator Model

By participating in the partnership program, you will receive an exclusive integration token, along with the necessary documentation to create, subscribe, or cancel instances via API, eliminating the need for access to our admin interface.

​
Tokens

At Z-API, we provide two tokens to configure in your account: Client-Token (Account Security Token) and Partner-Token (Partner Token). Below is an explanation of how each one works.

​
Client-Token (Account Security Token)

Used for all calls made via the API, providing an additional layer of protection for your instances, ensuring that only authorized requests have access to your resources.

​
Integrator Token (Partner Token)

After creating your first 10 instances, you can request our support team for the new definitive Partner token, which allows you to create, subscribe, list, and cancel instances via API.

​
Important

ATTENTION
  • All responsibility for token usage belongs to the client. Your company is financially responsible for all created instances. Avoid using tokens in test environments.
  • New instances come with a default 2-day trial period. After expiration, instances stop and are automatically deleted unless the subscription method is invoked. It is not necessary to cancel instances during the trial period.
  • The integrator partnership model currently operates on a post-paid basis, with pre-paid options coming soon.

​
Billing

Our billing cycle works as follows:
  • Every instance subscribed between the 1st and the 31st will be grouped and made available in a single payment due on the 5th of the following month.
  • Canceled instances remain active until the last day of the current month, being automatically deactivated at the end of the cycle. Billing continues normally until that period.
  • All instances expire on the 10th of the billing month. Non-payment results in deletion by DevOps on the 15th.

​
Instance migration

During plan adoption, the integrating company may opt to migrate all active instances from the pre-paid model to the new post-paid model, however this request must be made at the time of enrollment.

​
How to charge your client

We recommend our clients adopt the pre-paid model in their solutions as we don’t work with prorated billing.