Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.
Post a job
Publish roles on your Worklittle job board and optionally the global jobs index. Session posting in Worklittle Business or API-key automation for listings.
Overview
Posting creates Worklittle-hosted jobs that appear on GET /business/jobs/company/:company_slug/jobs and may enter the paid global index. A sk-wl-api01-... key for job search does not replace employer session auth for posting unless it includes jobs:post.
When to use
If you are building:
Employer workflow in Worklittle Business Sign in at worklittle.com/business, set organization, submit via Post a job (session routes) Automated listing management API key with jobs:post on /business/jobs or MCP post_a_job / create_job Agent-driven hiring ops MCP tools mirror ATS tables: list_posted_jobs, update_posted_job, delete_posted_job Apply-ready postings Published jobs accept applications - Apply for jobs * Custom careers UIs use the public board + form fields - Public job board
Basic usage
Session (Worklittle Business) - after sign-in:
POST /business/jobs
Cookie: session=…
Content-Type: application/json
{
"title": "Senior Backend Engineer",
"description_raw": "…",
"employment_type": "full_time",
"workplace_type": "remote"
}
API key listing:
curl -s -X POST "https://api.worklittle.com/business/jobs" \
-H "Authorization: Bearer $WORKLITTLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"title":"…","description":"…","employment_type":"full_time","workplace_type":"remote"}'
MCP: post_a_job or create_job with the same fields.
Post a job reference
> Self-contained reference for employer job posting.
Overview
| Surface | Auth | Routes | | --- | --- | --- | | Worklittle Business UI | Session | `/business/jobs/*` | | REST automation | `jobs:post` | `/business/jobs`, `/jobs/manage` | | MCP | API key | `post_a_job`, `create_job`, `update_posted_job`, `delete_posted_job`, etc. |
Session routes
| Method | Path | Purpose | | --- | --- | --- | | GET | `/business/jobs/organization` | Read posting organization | | PUT | `/business/jobs/organization` | Set organization (one per account) | | POST | `/business/jobs` | Submit job for review and publish | | GET | `/business/jobs` | List your submissions | | PATCH | `/business/jobs/:id` | Edit, reopen, or stop accepting applicants | | DELETE | `/business/jobs/:id` | Close job and remove from public search | | GET | `/business/jobs/:id/applications` | List applications for a job | | GET | `/business/jobs/:id/applications/:application_id` | Read one application | | POST | `/business/jobs/:id/transfer` | Transfer job to another org member |
API key job listings
| Endpoint | Methods | Scope | Purpose | | --- | --- | --- | --- | | `/business/jobs` | GET, POST | `jobs:post` | List or create Worklittle ATS job listings | | `/business/jobs/:id` | PATCH, DELETE | `jobs:post` | Update or close a listing | | `/jobs/manage` | GET, POST | `jobs:post` | Alias for job listings | | `/jobs/manage/:id` | PATCH, DELETE | `jobs:post` | Alias for listing item routes |
Required fields on create
| Field | Rule | | --- | --- | | `title` | 3–160 characters | | `description` or `description_raw` | 120–25,000 characters | | `employment_type` | `full_time`, `part_time`, `contract`, `temporary`, `volunteer` | | `workplace_type` | `remote`, `hybrid`, `on_site` | | Location | Required when not fully remote |
Common mistakes
| Wrong | Correct | | --- | --- | | Using `jobs:read` only to post | Add `jobs:post` scope | | Expecting instant global index visibility | Jobs may need review; board routes update first | | Posting then applying with the wrong job id | Use the posted job's `public_job_id` for apply |
Patterns and gotchas
Organization first - GET/PUT /business/jobs/organization before first publish. Public slug - Optional slug / public_slug on create/patch. Auto-generated from title when omitted. Returned as slug with preview_key on employer job APIs (preview key is never on public list responses). Application fields - Configure application_fields on the listing so apply validation matches your form. Applications inbox - GET /business/jobs/:id/applications and MCP list_job_applications for employer review. * Custom boards - Public consumers resolve jobs by slug via GET /business/jobs/company/:company/jobs/:slug - see Public job board.