| name | persona-rate-limits |
| description | Handle Persona API rate limits with exponential backoff and request queuing.
Use when working with Persona identity verification.
Trigger with phrases like "persona rate-limits", "persona rate-limits".
|
| allowed-tools | Read, Write, Edit |
| version | 1.4.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","persona","identity","kyc","verification"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
persona rate limits | sed 's/\b(.)/\u\1/g'
Overview
Persona rate limits (varies by plan), backoff on 429, batch inquiry creation, queue-based processing.
Prerequisites
- Completed
persona-install-auth setup
- Valid Persona API key (sandbox or production)
Instructions
Step 1: Implementation
import os, requests
HEADERS = {
"Authorization": f"Bearer {os.environ['PERSONA_API_KEY']}",
"Persona-Version": "2023-01-05",
}
BASE = "https://withpersona.com/api/v1"
resp = requests.get(f"{BASE}/inquiries?page[size]=10", headers=HEADERS)
resp.raise_for_status()
inquiries = resp.json()["data"]
for inq in inquiries:
print(f" {inq['id']}: {inq['attributes']['status']}")
Output
- Persona rate limits (varies by plan), backoff on 429, batch inquiry creation, queue-based processing.
Error Handling
| Error | Cause | Solution |
|---|
| 401 Unauthorized | Invalid API key | Check PERSONA_API_KEY |
| 429 Rate Limited | Too many requests | Implement backoff |
| 404 Not Found | Wrong resource ID | Verify ID format |
Resources
Next Steps
See related Persona skills for more workflows.