Create a placement custom attribute definition
Changed onCreates a new agency-wide custom attribute definition for placement records.
For options-type attributes, provide the selectable choices via options (in display order) and optionally set multipleValues to allow multi-select. The attribute name must be unique per entity type within the agency (exact match, case-sensitive — same as the Atlas app) — a duplicate name returns 409.
For placements, the name only has to be unique among attributes that can show on the same placement: a contract and a permanent attribute may share a name, but a both attribute's name must not be used by any other placement attribute.
Each placement attribute applies to contract placements, permanent placements or both — see record_type. This endpoint returns them all; a placement only accepts values for the attributes matching its own kind.
Request
- Base URLhttps://api.recruitwithatlas.com
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Example request
{
"name": "Seniority Level",
"type": "options",
"options": [
"Junior",
"Mid",
"Senior"
],
"recordType": "contract"
}Response
Created placement custom attribute definition
Example response
{
"data": {
"name": "Seniority Level",
"description": "Candidate's seniority level",
"type": "options",
"multipleValues": true,
"recordType": "contract",
"options": [
{
"value": "Senior"
}
]
}
}Changes
- info
added the optional property
to the response with the status
- info