You can post a role into Picked without opening the app. A system you own, or an AI agent, sends the job to Picked and it lands in your workspace as a draft, ready for a human to review and publish. This is useful when your careers site, your ATS, or an assistant already holds the role and you want it in Picked without re-keying it.
Go to Account, then API tokens, and choose Create a token. Give it a name you will recognise, for example Careers-site poster. The secret is shown once, at creation, and stored only as a hash, so copy it somewhere safe. Treat it like a password: anyone holding it can post drafts into your workspace. You can revoke a token at any time from the same page.
Send a POST to https://picked.ai/api/v1/employer/jobs with your token as a bearer credential in the Authorization header, and the role as a JSON body. The fields are:
A successful call returns 201 with a role_id and a review link. If the payload fails a check you get a 400 with a message naming the problem, so an over-short description or a missing pay band tells you exactly what to fix.
If you are driving Picked from an AI agent that speaks MCP, point it at https://picked.ai/api/employer/mcp with the same token as a bearer credential. The server exposes one tool, post_job, whose arguments match the fields above. The agent calls post_job and the role arrives as a draft, exactly as with the JSON API.
Every posted job lands as a draft in your workspace under Roles. It is never published automatically. A person on your team reviews it and publishes it through the normal flow, which is where the compliance step lives. Nothing goes live, and no candidate sees it, until a human publishes it.
What to do next: create a token, post one test role, and check it appears under Roles as a draft. Once you are happy, wire the call into whatever system holds your roles.