Order a programmatic job advertising campaign via the VONQ HAPI
domain: vonq.stoplight.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain your VONQ partner API token (X-Auth-Token); VONQ supplies this to partners directly — store it securely as an environment variable and never expose it in frontend code.
Query GET /products to retrieve available job board channel IDs and pricing for the target audience, location, and job category; select the desired channel IDs for the campaign.
Build the campaign order payload: include the list of selected channel IDs, the job posting details (title, description, location, apply URL), recruiter contact, and campaign duration.
POST the payload to the campaign order endpoint documented at vonq.stoplight.io/docs/hapi with the X-Auth-Token header; parse the returned campaign ID.
Poll GET /campaigns/{campaignId} to monitor campaign status (e.g., active, published) and handle any channel-level errors for individual boards that failed to publish.
Known gotchas
Authentication uses a static X-Auth-Token header supplied by VONQ, not OAuth; the token must remain server-side and must never appear in client-side JavaScript (HAPI Elements uses a JWT generated from the partner token).
Channel availability and pricing change; always fetch /products at order time rather than caching product lists, as channels can be added or removed.
Each channel may have its own required fields (e.g., salary range, work schedule type); missing required channel-specific fields cause per-channel publish failures visible in the campaign status response.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?