APIs are the favorite target of scrapers and attackers, and many were never built with access control in mind. API Protect puts a token check and a rate limit in front of any URL on your site, enforced by NOC at the edge, before a request reaches your server.
Adding authentication to an existing API means code changes, testing and a release, and some APIs, like the WordPress REST API on /wp-json/, aren't yours to change. With API Protect, the check happens on NOC's network instead: requests without a valid token, or over their limit, get a 403 there, and your application only sees the calls you allowed.
List the API paths to protect, like ^/api/ or /wp-json/.
Create a user for each partner or app. NOC generates a token, or you set your own.
Give each user a limit in requests per hour, and an expiry date if you want.
Each request carries its token in the X-API-Access header. Everything else is refused at the edge.
Manage API Protect users from your own systems.
curl "https://my.noc.org/api?apikey=YOUR_API_KEY&action=cdn/customrules/add&website=example.com&rule_type=api_protect&url=/api/v2/"
curl "https://my.noc.org/api?apikey=YOUR_API_KEY&action=cdn/customrules/api_protect/add_user&website=example.com&username=partner-a&max_requests=500&expire=2027-12-31"
curl -H "X-API-Access: THE_USER_TOKEN" "https://example.com/api/orders"
/wp-json/my-plugin/, not all of /wp-json/.Learn the basics: What is rate limiting? · What is authentication?
Get access to our full suite of services, including DNS, WAF/CDN and Monitoring, or use only what you need. Our WAF/CDN operates on a distributed anycast network with over 20 data centers, delivering exceptional global performance.
Free 14-Day Trial