# Integration examples

Three small recipes using the existing contract.

## Search a cohort

Use `job_family=data`, `job_subfamily=data_engineering` and `limit=1` for a data engineering cohort. Add `engagement_model=c2c` and `commercial_eligibility=eligible` only when commercial work is your requirement. A cohort may legitimately have no results. Run the bounded preview from the API overview.

## Inspect one opportunity

Take an `id` from your own search response and request `GET /v1/opportunities/{opportunity_id}`. Inspect `sources`, `evidence`, `last_verified_live_at`, `location` and `rate`. Do not hard-code an example job ID that may disappear. Repeating the same canonical ID within the same account period consumes no additional opportunity allowance.

## Add an internal lookup

Keep `RADAR_API_KEY` on the server. Validate application inputs against an allowlist of supported filters, set `limit=1` or a small cap, apply a timeout and return only the fields your user needs. Keep an explicit maximum of two pages for this example. Never expose an arbitrary URL proxy or a browser credential.

## HTTP automation

A generic HTTP request step can call the REST endpoint using the tool's encrypted credential store for `X-API-Key` and a fresh UUID for `X-Request-ID`. Apply a result budget and backoff. This is a generic recipe, not an official native marketplace integration.

## Runnable request

```sh
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)"
```

See the Examples page for bounded Python and Node.js downloads.