Lifecycle
Draft, publish, update, close, repost
The public endpoints wrap the same job mutation path the UI uses, so API posts keep slug history, salary rules, and ownership checks.
Posting API
Automated job posting, same rules as the form.
Create drafts, publish salary-transparent remote roles, update listings, close roles, and repost from your own hiring system. The API uses the same credits, rate limits, ownership checks, and lifecycle rules as the browser flow.
OpenAPI generatedIdempotent writesCredit-aware publishing
GET owned jobs
v1
export RS_API_BASE=https://remotestake.com
export RS_API_KEY=rs_...
curl -sS "$RS_API_BASE/api/v1/jobs?limit=10" \
-H "Authorization: Bearer $RS_API_KEY" | jqRetries
Idempotency for mutating calls
Send an Idempotency-Key on writes. Safe retries replay the stored response; same key with a different body returns a conflict.
Access
Bearer keys with visible fingerprints
Keys are shown once, stored as hashes, scoped to jobs:read/write, and revocable from your account settings.
Generated docs
The reference is generated from the live contract.
The endpoint list, schemas, examples, and request client come from the oRPC OpenAPI document. The human page stays focused on positioning; the generated reference owns method-by-method API details.
Boundaries
What keys never bypass
- Listing credits and paid publish accounting.
- Salary-required validation for published jobs.
- Per-account publish, draft, and repost rate limits.
- Ownership checks, lifecycle preconditions, and slug history.
- Stable problem JSON with request ids for support traces.
Need examples?
OpenAPI is the machine contract. For SDKs, ATS-specific syncs, or high-volume rollout help, use the API key flow and contact us with the integration shape.