X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset are returned with every response.
Secure links with powerful analytics
API & Integration FAQ
Everything your engineering team needs to integrate Linkify’s shortening endpoints, manage webhooks, and troubleshoot rate limits.
Rate Limits & Request Quotas
Linkify enforces tier-based throttling to ensure global endpoint stability. Check your plan’s allowances and learn how to monitor usage headers.
What are the default rate limits for the Pro plan?
The Pro tier allows 12,000 requests per hour per API key, with a burst allowance of 150 requests per 10-second window. Headers
How do I increase my quota for high-volume campaigns?
Contact your account manager at
accounts@linkify.io to request a custom tier. We typically provision enterprise keys with up to 500,000 requests/hour after verifying your traffic architecture and caching strategy.Date Formats & Payload Structure
Consistent timestamp handling prevents webhook mismatches and analytics drift. All Linkify endpoints follow strict RFC 3339 standards.
Which date format should I use for created_at and expires_at?
Use ISO 8601 / RFC 3339 format:
YYYY-MM-DDTHH:mm:ssZ. Omitting the timezone offset defaults to UTC, but explicit Z or +00:00 is strongly recommended to avoid parser errors in Node.js or Python clients.Why are my webhook timestamps showing a 1-hour offset?
Linkify’s event bus normalizes all timestamps to UTC before dispatch. If your receiving service applies local timezone conversion automatically, disable it in your webhook handler. You can also append
?tz=UTC to your subscription endpoint to force strict UTC delivery.Troubleshooting 429 & 403 Errors
HTTP 429 (Too Many Requests) and 403 (Forbidden) are the most common integration blockers. Implement exponential backoff and validate your key permissions.