Pricing and limits

Modified on Mon, 26 Oct at 2:47 PM

Sales Layer API 2.0 offers different capacity plans to meet each customer's integration needs.


Each plan establishes a request quota, a rate limit, and a maximum number of active API Keys per account.


PlanQuota (requests/7 days)Rate limitPrice
Trial (Free)3,50010 req/10 sFree
Pack 170,00020 req/10 s€2,000/year
Pack 2210,00050 req/10 s€4,000/year
CustomCustomCustomCustom pricing


Request quota (Req/7 days)


This is the maximum number of requests you can make to the API over a 7-day period.

For example, Pack 1 includes 70,000 requests every 7 days.


Rate limit (Req/10 s)


This is the maximum number of requests you can make within a 10-second interval.


The quota determines the total number of requests available, while the rate limit determines how quickly those requests can be made.


API Keys available per account


Each plan includes an initial maximum number of active API Keys that you can use to manage different integrations.


PlanActive API Keys per accountPurpose
Trial2Allows testing permissions or two integrations without sharing credentials.
Pack 15Separates integrations and common use cases while keeping administration simple.
Pack 210Supports more integrations while maintaining the same shared request quota.
CustomAgreed based on integration requirementsThe number is explicitly defined in the contract and is not assumed to be unlimited.


Each API Key allows you to manage access for an integration independently, without having to share credentials between different systems.


★

Important: All API Keys within the same account share the request quota of the subscribed plan. Creating additional API Keys does not increase the available quota.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article