Guide
Quick Start
Get a salary benchmark from WageAPI in under 2 minutes.
1. Subscribe on RapidAPI
WageAPI is distributed via RapidAPI. Head to https://rapidapi.com/AETHAR/api/wageapi and subscribe to the Free plan — 100 requests per day, no credit card required.
RapidAPI handles billing, key issuance, and usage analytics. Upgrading or downgrading a plan takes effect immediately.
2. Copy your RapidAPI key
After subscribing, RapidAPI shows your personal X-RapidAPI-Key in the right-hand Code Snippets pane. This is the key you send on every request — keep it secret, never commit it to git, never embed it in client-side code.
If you're calling WageAPI directly (not through the RapidAPI gateway) — for enterprise customers with a private contract — you'll receive an Aethar-issued key with the prefix sk_ and use the header X-API-Key instead. This guide assumes the RapidAPI path; swap headers if you're on the direct path.
3. Make your first request
Get salary percentiles for software engineers in the New York metro area:
curl -X GET "https://wageapi.p.rapidapi.com/v1/salary?job_title=software%20engineer&location=New%20York-Newark-Jersey%20City%2C%20NY-NJ-PA" \
-H "X-RapidAPI-Key: your_rapidapi_key" \
-H "X-RapidAPI-Host: wageapi.p.rapidapi.com"You should see a 200 response with p10, p25, median, p75, p90 percentiles, the BLS source year, and the SOC occupation code that matched your query.
4. Next steps
Browse the full endpoint reference in the left sidebar. The main tags are Salary (percentiles, compare), Jobs (fuzzy SOC lookup), Trends (CAGR), Compliance (EU pay transparency), and Intelligence (agent-first semantic endpoints like *is this salary competitive?* and *best cities for nurses?*).
For production workloads, read the Rate Limits and Errors guides to handle non-200 responses gracefully, and the Data Sources guide to understand what your data actually means.