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.
Apply for someone else with the API
For developers and platforms: apply on behalf of people who gave you permission, with their own name, email, and resume.
On worklittle.com, Worklittle applies for you. Applying for other people is only available through the API, for developers and platforms under the API terms. You must have each person's permission to apply for them.
How it works
Send POST /v1/apply with "use_profile": false and an applicant with at least their name and email, plus their resume (resume_file, resume_pdf_base64, or resume_text). They do not need a Worklittle account. Billing goes to your account.
The response has an applicant_id. That id is this person from now on, and Worklittle also emails it to them, so they always have it. One person keeps one profile: Worklittle picks the best resume for each job and tailors it, so a second profile is never needed.
Save the applicant_id
Store the applicant_id permanently, next to the person in your own records (your user table, a CRM, a file), somewhere you can look it up later. Then:
- Apply again: send applicant_id instead of applicant. No resume upload needed. - Update their profile: POST /v1/apply/profile with "action": "save", the applicant_id and only what changed (a new phone, city, job title, or email). Do not make a new applicant for a change. - New resume: the same call with resume_file. - Check on them: POST /v1/apply/profile with "action": "get" returns their profile, applications and employer emails.
It works with any API key. The applicant_id belongs to the person: whichever app they give it to can apply for them, update their profile, and read their applications and employer emails. Each application is billed to the key that started it. Only the app that created the applicant can delete it or turn its auto-apply on or off (it pays for auto-apply).
One profile per person. Sending an email that already has a Worklittle applicant does not make a second one. It answers 409 APPLICANT_EXISTS and emails the applicant_id to that address, so only the real person can get it back, never someone who just knows their email. (Your own personal key simply reuses applicants it created.) Lost the id? Ask the person: it is in the email Worklittle sent them.
Their email
Use their real email. If an employer site sends a verification code, Worklittle gives the application its own my.worklittle.com address, reads the code automatically, and forwards every other employer email (interview invites, replies) to the applicant's email. Change it any time with POST /v1/apply/profile ("action": "save", the applicant_id and the new email).
Their emails and auto-apply
- Employer emails: POST /v1/apply/profile with "action": "get" includes what employers sent about their applications (verification codes, interview invites, replies), newest first. Every one is also forwarded to their own inbox. - Auto-apply: POST /v1/apply/profile with "action": "save", the applicant_id and "auto_apply": true, and Worklittle applies to jobs that match their profile on its own. auto_submit and tailor_resume are theirs too. Billing goes to your account; it needs a Worklittle Instant subscription or a card on it.
Manage or delete a person
- POST /v1/apply/profile with "action": "get" reads their profile. GET /v1/applicants lists everyone, on your own key only (a shared key cannot list). - POST /v1/apply/profile with "action": "delete" erases their profile and resumes. Stop any application in progress first.
Errors you might see
| Code | Meaning | Fix | | --- | --- | --- | | `APPLICANT_EXISTS` | This email already has a Worklittle applicant | Ask the person for the `applicant_id` we just emailed them, then send it | | `APPLICANT_REQUIRED` | A shared key must say who it applies for | Send `applicant_id`, or `applicant` plus a resume | | `APPLICANT_ID_REQUIRED` | Shared keys show one person at a time | Add `applicant_id` | | `SHARED_API_KEY` | A shared key cannot use the account's own profile | Apply with an applicant instead | | 404 Applicant not found | No applicant has that id | Use the exact `applicant_id` the first apply returned | | `COMPANY_LIMIT_REACHED` | `max_per_company` applications at one company in 30 days (default 3) | Ask them, then resend with a higher `max_per_company` (up to 10) |
Platforms applying for many people
If your product applies for its own users, email [support@worklittle.com](mailto:support@worklittle.com) for a platform key. It can only search and apply, only sees the people it created, and has daily application limits for the key and for each person.
You are responsible for having each person's permission before you apply for them. See the Terms of Use.
Related
- Apply for jobs through the API - Apply for someone else (developer docs)