Skip to main content
Spoo.me API implements rate limiting to ensure fair usage and maintain service quality for all users. Rate limits vary based on authentication method and API version. The new v1 API offers significantly higher rate limits with authentication:

With Authentication (JWT or API Key)

Per Minute

60 requests

Per Day

5,000 requests

Endpoints

All v1 endpoints

Without Authentication (Anonymous)

Per Minute

20 requests

Per Day

200 requests

Endpoints

Limited endpoints
Get far higher limits by using API keys or JWT authentication: 60 vs 20 requests per minute, and 5,000 vs 200 requests per day.

API v0 Rate Limits (Legacy)

The legacy v0 API has lower rate limits:

Per Minute

5 short URLs per IP

Per Day

50 short URLs per IP
The v0 API is legacy, does not support authentication, and is strictly rate limited. Migrate to the v1 API for dramatically higher limits and features. Rate-limited responses from the legacy shorten endpoints carry an X-Spoo-Hint header (and a hint field on JSON responses) with the migration path.

Rate Limits by Endpoint

URL Shortening

v1 API Endpoints

v0 API Endpoints (Legacy)

The following endpoints are part of the legacy v0 API. They do not support authentication and have lower rate limits.

URL Management

Analytics

Authentication & Rate Limits

How you authenticate directly affects your rate limits:
Rate Limits: 60/min, 5000/dayBenefits:
  • Same rate limits as API keys
  • Full dashboard access
  • Can create/manage API keys
  • Manage URLs via web UI
How to use: Obtain JWT via OAuth/login and include in header:
Rate Limits: 20/min, 200/day (public per-link stats: 20/min, 500/day)Limitations:
  • Far lower rate limits
  • Cannot manage URLs later
  • Stats limited to the public per-link endpoint (links with private stats appear as 404)
  • Cannot use URL management endpoints
How to use: Simply make requests without authentication header.

Rate Limit Headers

When you make requests to rate-limited endpoints, the response will include headers indicating your current usage:
Most endpoints enforce a per-minute and a per-day window at once; the headers describe the shortest window. 429 responses additionally carry a Retry-After header.

Handling Rate Limits

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
The hint names the tier with higher limits. It appears on anonymous v1 requests and the legacy mint endpoints (POST /, POST /emoji), and is also sent as an X-Spoo-Hint response header so it reaches callers that receive the HTML error page or ignore the body.

Need Higher Limits?

If you need higher rate limits for your application:
1

Contact Support

If you still need higher limits, contact our support team at support@spoo.me with:
  • Details about your use case
  • Expected request volume
  • Description of your application

Next Steps

Create API Keys

Get started with API key authentication

API Reference

Explore all available endpoints

Quick Start

Build your first integration

Python Library

Use our official SDK