Radar API / Developer guide
Quickstart
Create a key and make one small authenticated request.
Read as Markdown1. Get your API key
Open your Radar account and create or reveal the initial customer key. API access uses the existing account and does not require a RadarJobs resume, preferences or purchase. Save the key in a local environment or secret store. Do not put it in a URL, browser code, a commit or a chat transcript.
2. Make one request
Set RADAR_API_KEY securely, then run a server-side example below. The canonical base URL is https://api.revenirdata.com. Send X-API-Key and a fresh X-Request-ID. Start with limit=1. The cURL example needs Bash or zsh, curl and uuidgen; Node.js examples require version 22+; Python snippets require Python 3.12+ and requests, while the Python download uses only the standard library. Never echo the key; disable shell tracing and keep environment files ignored by Git.
curl --fail-with-body --connect-timeout 10 --max-time 30 --request GET 'https://api.revenirdata.com/v1/opportunities?job_family=data&job_subfamily=data_engineering&limit=1' \
--header "X-API-Key: $RADAR_API_KEY" \
--header "X-Request-ID: $(uuidgen)"Bash or zsh with curl and uuidgen. In PowerShell, use the Node.js or Python download.
Server-side only. Set RADAR_API_KEY securely before running.
3. Inspect the result
A successful list response contains data (records), pagination (including returned and next_cursor), and meta (request_id and applied_filters). An empty data array is a valid result, not an integration failure. Compare the returned request ID with your request and inspect usage headers before expanding the query.
4. Observe success
A copied prompt or created key is not a successful integration. Confirm a 200 response from your own server-side request, then check account usage. One canonical ID consumes allowance only on its first delivery to the account in the current period.
Start in your editor
Give this to your AI agent
Copy this prompt into your coding agent. Configure your key privately when it asks.