API

The redirect.pizza API gives you programmatic access to your team: manage redirects, email forwards, domains and users, read analytics and check your quota. It's a JSON REST API, and everything you can do in the dashboard is available through it.

View the API documentation

Authentication

Create an API token under More, API/MCP. A team can have multiple tokens, each with its own scopes and tag access. Pass the token as a bearer token:

curl --header "Authorization: Bearer rpa_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  https://redirect.pizza/api/v1/redirects

Scopes

Limit what a token can do by giving it only the scopes it needs:

  • redirects:read and redirects:write
  • email-forwards:read and email-forwards:write
  • domains:manage
  • analytics:read
  • team:read and team:write
  • users:read and users:write
  • mcp:use: allows the token to be used by MCP clients

Tag access

Restrict a token to redirects with specific tags, or exclude specific tags. This lets you hand out tokens that only see a subset of your redirects, for example one per department or per customer. It works the same way as access control for users.

Tag access settings for an API token

Rate limits

Requests are rate limited per team: 300 requests per minute on the Free, Basic and Pro plans, and 900 requests per minute on the Business and Enterprise plans. Need more? Contact sales.

Endpoints

The API covers redirects, email forwards, domains (including a forced DNS check), analytics, users and team details, plus a redirect tester and a QR code generator. The API documentation describes every endpoint with request and response examples.

Integrations built on the API

  • MCP: manage redirects from Claude, Cursor and other AI clients
  • Terraform provider: manage redirects as infrastructure as code
  • Zapier: create redirects from triggers in other apps, without code

More articles

Setup & Configuration
What are these DNS changes?
What DNS types can I use?
How long does the DNS change take?
Troubleshooting new redirects
Redirecting non-www to www
Redirect settings
Matching
Regex matching
Wildcard subdomains
Destination variables
Dynamic destinations
Redirect flattening
SSL profiles
robots.txt
Monitoring redirect.pizza itself
Features
Automatic HTTPS
Automatic DNS
Nameservers
Analytics
Broken destination monitoring
Email forwarding
Pause and resume
Dedicated IP
API
MCP
Zapier
Terraform provider
Security & Account
Team management
Two-factor authentication
SAML SSO
SSO via Okta
Summary email
HSTS (HTTP Strict Transport Security)
Prevent foreign embedding
Web Application Firewall (WAF)
Security & compliance
Subprocessors
Service level agreement (SLA)
Walkthroughs
GoDaddy: Forwarding with HTTPS support
Namecheap: Forwarding with HTTPS support
Cloudflare: Forwarding with HTTPS support
Network Solutions: Forwarding with HTTPS support
Hover: Forwarding with HTTPS support
Amazon Route 53: Forwarding with HTTPS support
Google Cloud DNS: Forwarding with HTTPS support
Azure DNS: Forwarding with HTTPS support
DigitalOcean: Forwarding with HTTPS support
NS1: Forwarding with HTTPS support
DNS Made Easy: Forwarding with HTTPS support
TransIP: Forwarding with HTTPS support
EuroDNS: Forwarding with HTTPS support
Mijndomein: Forwarding with HTTPS support
Freenom: Forwarding with HTTPS support