internkim
APIEvery endpointLeave

leave_delete

Take a leave back out of the record entirely, as though it was never filed. A person takes back their own while it is still waiting on a decision; an administrator takes back anybody's. Entitlement an approved leave spent comes back with it. To refuse a leave rather than erase it, decide it rejected. `destructive` · approval · v2

POST
/tools/leave_delete/invoke

Authorization

memberToken
AuthorizationBearer <token>

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/leave_delete/invoke" \  -H "Content-Type: application/json" \  -d '{    "input": {      "leaveHint": "…"    }  }'

{  "toolName": "leave_delete",  "outcome": "succeeded",  "selectedBackend": "device",  "effects": [    {      "objectType": "leave",      "effect": "created",      "id": "7a93de11-…"    }  ],  "result": {    "…": "the tool's own document"  }}