You can now manage team members through the API: list users, send invites, update roles and tag access, and remove members.
This uses the users:read and users:write scopes. See the API docs for the full endpoints.
API rate limits are now tied to your plan, and they're higher by default on Business and Enterprise.
Those plans include 900 requests per minute. Other plans stay at 300. Need more than that? Reach out and we can raise the limit for your team.
We've added self-service error templates for teams with a dedicated IP.
Upload your own HTML for 404 pages, paused sources, WAF blocks and the other edge responses, so visitors see your branding instead of the defaults. Open Dedicated IP in your account to get started. Read more in the dedicated IP article.
We've expanded the destination URL validation to include schemes like mailto:, tel: and sms:.
You can redirect a hostname or path straight to an email address, phone number or text message. App deep links that use :// (for example instagram://) already worked, and still do.
We've added a new edge node in Tel Aviv, Israel.
Visitors in the Middle East now have a closer hop, which keeps redirects fast in the region. See the full map on the network page.
We've sped up DNS verification for newly added domains.
New hostnames are checked more often in the first hour, so a correct DNS change is picked up sooner and your redirect can go live without waiting on the slower retry schedule.
We've updated the TLS 1.2 cipher suites on the edge network.
HTTPS redirects now follow Mozilla's Intermediate profile, which matches NCSC-NL guidance: AES-GCM and ChaCha20-Poly1305 only. CBC and SHA-1 MAC suites are no longer offered. TLS 1.3 is unchanged.
Your redirects work the same way. Current browsers and clients are unaffected. We still hold an A+ rating from Qualys SSL Labs on every plan. Read more in the automatic HTTPS article.
You can now import redirects through the API, using the same columns as the dashboard importer. Send a JSON array or a CSV string to POST /api/v1/redirects/import, then poll the import status endpoint for progress.
Re-importing an existing source now updates the destination instead of leaving you to edit it by hand. That makes bulk migrations and ongoing syncs much easier to run. Details are in the API docs.