company_settings_get
The company settings: its name, country, language, time zone, base currency, the work locations attendance can be recorded at, the annual leave a person is granted, whether everybody may see the whole company's attendance, and the address of its picture. Read this to answer 'what time zone are we on', 'which currency do we use', or 'where can we clock in from'. The work location names are what attendance_add's location takes. `read` · v2
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/company_settings_get/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": {} }'{ "toolName": "company_settings_get", "outcome": "succeeded", "selectedBackend": "device", "result": { "…": "the tool's own document" }}company_record_update POST
Update fields on an existing company record named by recordHint from a prior company_record_list result. Only provided fields change. `workspace_write` · v1
company_settings_update POST
Change the company settings. Only the fields the call names change. This is an administrator's, and it is company-wide: the time zone and the language decide what every colleague sees, so put it to the requester before calling. `workspace_write` · approval · v2