curl --request GET \
--url https://control.ergoly.ai/api/v1/company/placements \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://control.ergoly.ai/api/v1/company/placements', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://control.ergoly.ai/api/v1/company/placements"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"data": [
{
"id": "b1c2d3e4-f5a6-4b7c-8d9e-0f1a2b3c4d5e",
"kind": "person",
"label": "Jordan Lee",
"title": "Head of Support",
"parentId": null,
"workerId": null,
"slackUserId": "U0A1B2C3D4E"
}
],
"page": {
"limit": 50,
"hasMore": true,
"nextCursor": null
}
}{
"error": {
"code": "unauthorized",
"message": "<string>",
"docs": "<string>"
}
}{
"error": {
"code": "unauthorized",
"message": "<string>",
"docs": "<string>"
}
}List chart placements
Every place on your Company chart a Worker may sit under — a person’s seat, a Worker’s, a team, an open role — in the order the chart draws them, each with its title and the place it sits under. Pass one’s id as reportsTo.placementId when you create a Worker. Nothing inside a vendor or a client is listed, because a Worker may not sit there. The whole chart comes back at once; it is not paged.
curl --request GET \
--url https://control.ergoly.ai/api/v1/company/placements \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://control.ergoly.ai/api/v1/company/placements', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://control.ergoly.ai/api/v1/company/placements"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"data": [
{
"id": "b1c2d3e4-f5a6-4b7c-8d9e-0f1a2b3c4d5e",
"kind": "person",
"label": "Jordan Lee",
"title": "Head of Support",
"parentId": null,
"workerId": null,
"slackUserId": "U0A1B2C3D4E"
}
],
"page": {
"limit": 50,
"hasMore": true,
"nextCursor": null
}
}{
"error": {
"code": "unauthorized",
"message": "<string>",
"docs": "<string>"
}
}{
"error": {
"code": "unauthorized",
"message": "<string>",
"docs": "<string>"
}
}Authorizations
An organization-scoped API key, minted in control under Settings → API keys. Every failure to authenticate answers one identical 401: "Provide a valid organization-scoped API key or an active session." Each operation names the one scope it is filed under, <resource>:<read|write>, where the resource is the first path segment after /api/v1/; a key minted today carries all 22 of them. Scopes are RECORDED — on the key and on every audit row — and are not yet enforced: no request is refused for want of one.

