recruiting.applications.create
Add a candidate to a posting yourself (a referral or someone you sourced): postingId, candidate name, email, optional phone, location and links, source (referral, sourced, other), an optional note, and idempotencyKey. A person already in recruiting with that email is reused. Only administrators and the posting's hiring manager can do this.
/api/v1/accounting/recruiting.applications.createPermissions
Who can call it
Retries
MCP
accounting_recruiting_applications_createFields
postingIdstring (ID)RequiredThe ID of the related record.
candidateobjectRequiredNo other fields
sourceenumWhere the record came from.
referralsourcedotherDefault "sourced"
notestringA short note, kept with the record.
at most 5000 characters
idempotencyKeystringRequiredAny unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.
8–200 characters
Example
curl https://app.getoatmilk.com/api/v1/accounting/recruiting.applications.create \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"postingId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"candidate": {
"name": "Synthetic Ventures Inc.",
"email": "finance@example.com"
}
}'{
"data": { … }
}Try it
Try it
Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.
curl https://app.getoatmilk.com/api/v1/accounting/recruiting.applications.create \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"postingId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"candidate": {
"name": "Synthetic Ventures Inc.",
"email": "finance@example.com"
}
}'More in Contractors.