API and billing support

A key is shown once, when it is created, and can't be retrieved afterward; that is a security measure. If this browser still has you signed in to the dashboard, use Rotate secret keys there to issue a new one. Otherwise email support@revaddress.com from the account's email address. Usage history and billing belong to your merchant account, not to a key, so nothing is lost.

Sign in to the dashboard with your current key, go to API keys and choose Rotate secret keys. It revokes every secret key on the account and shows one new key, once. Integrations still on an old key stop working the moment you confirm, so be ready to deploy the new key right away. Publishable keys are not affected.

The usual causes:

• No header: every request needs X-API-Key: your_live_key.
• Wrong key type: use a live key in production; a free evaluation key is only for proving the integration.
• Revoked key: the dashboard marks each revoked key.
• Whitespace: strip trailing spaces and newlines from the header value.

The authentication docs cover the rest.

A 403 means your plan doesn't include that endpoint. USPS operations need current paid access and purchased credits, and connecting BYOK credentials doesn't bypass either check. Label purchase is disabled. The endpoint summary lists what each plan requires. To change plans, start from pricing or open billing tools in the dashboard. If self-serve billing isn't enabled for your account yet, email support@revaddress.com and we'll make the change.

The free tier allows 30 requests per 10 seconds from each IP address. Paid plans raise the monthly cap, and Enterprise limits are set to your workload. Read the X-RateLimit-Remaining header on each response. Pricing lists each plan's limits, and the rate limit docs cover implementation.

A 429 means the request went over your current limit and was rejected. Nothing is charged and no data is lost. The response's retry_after field gives the wait in seconds; retry after that. If 429s are routine, move to a plan with more throughput, or write to support and we'll size the limit to your workload.

Open billing tools from the dashboard (Manage billing). If self-serve billing is enabled for your account, you can upgrade, downgrade, update your card or change your billing email there. If it isn't, email support@revaddress.com and we'll make the change.

Cancel from billing tools in the dashboard, or email support@revaddress.com if self-serve billing isn't enabled for your account. Your API key keeps working until the end of the current billing period. There is no cancellation fee and no long-term contract.

We don't refund a partly used billing period. You can cancel at any time, and access continues until the period ends. If you were charged in error, or something unusual happened, use the form below and we'll resolve it.

BYOK connects on any key, Free included; the USPS calls it runs need a paid plan. Connect from the USPS license panel in the dashboard, or by API:

1. Get your client ID and client secret from your app under My Apps in the USPS Customer Onboarding Portal, plus your CRID and MID if you need labels or postage.
2. Store them with POST /api/byok/credentials.
3. Verify them with POST /api/byok/verify.

Credentials are encrypted at rest with AES-GCM. The BYOK docs have the full API reference.

Run GET /api/byok/status to check credential health, then look for:

• A changed client secret: we refresh USPS tokens automatically, but if the client secret changed on the USPS portal, submit the credentials again.
• A CRID or MID mismatch: both must match your USPS Business Account exactly.
• Credentials stored but not verified: run POST /api/byok/verify, or Re-verify in the dashboard. Until the status reads "verified", your calls fall back to hosted processing.

If the status reads "verified" and requests still fail, start with the USPS OAuth troubleshooting guide.

Free tier: 30 requests per 10 seconds per IP address, enough to validate addresses, compare rates and prove the integration before you buy.
Production: paid plans, with higher rate limits, managed tracking routes, protected label workflows and pickup scheduling (access on request).
Create a key with no credit card, and upgrade when you're ready to ship.

Validate an address with curl:

Address validation works without a key on the free tier. For endpoints that need one, add -H "X-API-Key: your_key_here". To try calls in the browser, use the live API playground. SDKs are available for Python and Node.js.

The free tier is rate-limited by IP address at 30 requests per 10 seconds and covers these read-only endpoint families:

• Address validation: GET /api/address/validate and POST /api/address/validate
• Guided address extraction: POST /api/address/extract
• City and state lookup by ZIP Code: GET /api/address/city-state
• Rate shopping: POST /api/rates and POST /api/international-prices
• Planning helpers: GET /api/service-standards, GET /api/shipping-options and GET /api/locations

Without a USPS license, the free path returns Census standardization and geocoding. USPS-backed data and DPV need paid access and purchased credits. Platform DPV requires 10 purchased credits ($0.01) per address; BYOK uses your own license where it is enabled. Tracking, labels, pickup, BYOK, the dashboard and other paid workflows need an API key. The full endpoint table is in the docs.