One key, every API
The same API key authenticates postal, IP, email, phone, and every other route. No per-endpoint keys to manage.
One key. Every route.
curl -H "X-API-Key: parse_yourkey" https://api.parseapi.com/postal/33139?country=US
curl -H "X-API-Key: parse_yourkey" https://api.parseapi.com/ip/8.8.8.8
curl -H "X-API-Key: parse_yourkey" https://api.parseapi.com/email/name@example.com
curl -H "X-API-Key: parse_yourkey" https://api.parseapi.com/phone/+14155552671
Same header, same key, four different APIs. Authorization: Bearer parse_yourkey works too, pick whichever your HTTP client already sends.
What the key carries
A key belongs to an organization, and the organization has a plan. The plan sets quota and rate limit. Every route checks the same key against the same plan, so the postal endpoint and the email endpoint are pulling from the same pool.
That means one dashboard page for usage across all products, one number for remaining quota, one place to rotate a key when a project changes. Ship a new integration against a different endpoint and there's nothing new to provision, the key already works.
Try it
Get a key and call two different endpoints with it back to back. Same header both times. We checked.