API limits

Records and rate limits

Your subscription plan determines the number of records you can create, such as links, domains, tags, scripts, and teammates. Rebrandly also applies API rate limits to protect platform stability and keep API performance consistent.

To see current plans, limits, pricing, and available features, visit our pricing page.

Default API rate limits

By default, Rebrandly API requests are limited to:

• 10 requests per second
• 20,000 API calls per hour

These limits apply across plans unless your account has an Enterprise account with a custom limit.

Workspace-specific link creation limits

Link creation throughput depends on the workspace type.

Classic Workspaces are accessible via the Rebrandly app dashboard and can be created via the app or the Rebrandly API.

Extended Workspaces are designed for high-volume link creation, are customized based on your Enterprise plan, and support multiple links per request.

Check your current resource limits and usage

To check how many links you have available for the current month:

1. Log in to Rebrandly.
2. Go to profile menu > Settings > Subscription & Usage.

You can also check your subscription information, limits, and usage through the API by using the Account info endpoint.

How we count limits

Resource counters update in real time as your API operations execute.

The following rules apply:

• Pending teammates count toward your teammate limit.
• Deleted resources, such as domains, tags, and scripts, do not count against your limits.
• API calls count toward your request limits whether they are made by an application, script, or integration.

Before running a long-running script, check your available limits and configure the script to process requests in controlled batches.

What happens when you exceed a limit

If your application exceeds an API or resource limit, the API returns an error response and the request does not complete.

When handling limit errors, your application should:

• stop sending repeated requests for the same operation.
• wait before retrying.
• reduce request volume where possible.
• show a clear message to the user or operator.
• stop retry loops when the error is caused by an account or plan limit that cannot be resolved by waiting.

For details about our error responses, see Errors.

Design your integration to avoid limits

If your application sends a high volume of requests, design it to stay within your API and workspace limits.

Recommended practices:

• Throttle requests so your application does not send large bursts of traffic.
• Retry with backoff when a request fails because of a temporary limit.
• Batch bulk jobs into smaller groups instead of sending all requests at once.
• Avoid unnecessary polling by caching responses where possible.
• Monitor usage before and during migrations, imports, or other long-running jobs.
• Tune link creation jobs based on whether you are using a Classic Workspace or Extended Workspace.

For example, if your workflow creates campaign links in an Extended Workspace, use the multi-link request format where available instead of sending one request for every link.

Need higher limits?

If you require higher API limits, contact us to learn about custom limits and high-volume link creation with our Enterprise plan.

To help us evaluate your request, include:

• the endpoints your application uses.
• the expected number of requests per second, minute, or hour.
• whether traffic is steady or occurs in bursts.
• the number of links, domains, tags, or other records you expect to create.
• whether the request is for a one-time migration or ongoing usage.
• whether your application uses Classic Workspaces, Extended Workspaces, or both.