Articles on: Billing & Pricing

How to use ConvertAPI's Access Tokens?

This article provides helpful tips on utilizing our Access Tokens in different scenarios such as reselling, managing multiple environments, and setting restrictions for specific Access Tokens.

ConvertAPI Access Tokens

Access tokens can be created and managed either from your account dashboard or via the Access Token Management API.

How to use Access Tokens?

When it comes to authenticating your conversions, you have two options: using a Secret key or Access Tokens. If you choose the Secret key option, keep in mind that a single account can only have one Secret key. On the other hand, with Access Tokens, you can create multiple tokens per account, making it easy to restrict the consumption per token and distribute your purchased conversions between multiple environments or customers.

Access Tokens also enable you to differentiate the consumption and statistics by tokens, which can be useful for detailed analysis. You can find the detailed statistics in the exported statistics CSV file.

To help you better understand the benefits of Access Tokens, we have listed some of the most common use cases below.

Limit the consumption using Access Tokens

You can apply different limits of consumption of our service by creating Access Tokens with specific conditions. Each Access Token has it's maximum conversion count that is reduced each time a conversion is made. It also has an expiry date which allows you to set the limit of conversions during a given period.

Let's say you purchased a 12 000 conversions annual package, and you want to limit each month's consumption to 1000 conversions max, so you make sure you don't run out of conversions until the end of your billing cycle. This way you would create a new Access Token each month with Request Count = 1000 and Lifetime in seconds = 2 629 746. You can automate this process using our Access Token Management API.

Different Access Tokens for different environments

Access Tokens are incredibly useful for managing authentication between different environments. By creating multiple Access Tokens, you can distribute your conversions across different environments individually, allowing for greater control and flexibility. For example, you can use one Access Token in your Staging environment and restrict it with Request Count = X. This way, in case you accidentally end up in an infinite loop while developing, etc., it will never reduce your account balance by more than X conversions. You can then create another Access Token with Request Count = Y for production use, ensuring that only the authorized personnel have access to your production-grade Access Token.

To make things even easier, you can automate the creation of Access Tokens based on your billing cycle using our Token API. This way, you can focus on your work without worrying about managing access tokens manually. With these features, you can ensure that your access tokens are secure, flexible, and tailored to your specific needs.

Become an affiliate or a reseller of a ConvertAPI service

Access Tokens can be an incredibly useful tool for anyone looking to resell ConvertAPI's credits to their own audience or potential customers. For example, if you provide a service that uses ConvertAPI under the hood, you could avoid asking your customers to purchase a ConvertAPI plan directly from us and provide you with their secret key. Instead, you could purchase a larger plan, which results in a cheaper price per conversion, and distribute the conversions to each customer individually.

This can save your customers money and provide them with a more streamlined experience, all while allowing you to offer a valuable service and get your profit share. By making adjustments to the price per conversion yourself, you can optimize your profit margin and ensure that you are getting your fair share of the earnings. This approach can help you to maximize your revenue and make the most out of your business!

Updated on: 08/01/2024

Was this article helpful?

Share your feedback


Thank you!