Leave request

Change the status of leave requests

Activity name : <a href="https://developer.loket.nl/Activities/PatchLeaveRequestsByLeaveRequestIds" target="_blank">PatchLeaveRequestsByLeaveRequestIds</a>

This endpoints changes the status of the list of leave requests provided in the request body to the provided status. The leave requests are processed one by one. The leave requests that had no error's will be commited to the database while those with an error will be skipped. If an error occured the service will return a 400 bad request with a message explaining what error occured for what ID (GUID). The leave requests that where processed successfully will not be returned in te response.

This endpoint can be used by provider, employer and employee users. Provider and employer users are able to accept, reject or reopen leave requests depending on the status of the request. Employee users are only able to revoke a submitted leave request.

patch/v2/providers/employers/employees/employments/leaverequests

Request

  • Base URL
    https://api.loket.nl
  • URL
    https://api.loket.nl/v2/providers/employers/employees/employments/leaverequests
  • Auth
    none required

Headers

Authorizationstring required
Example:Bearer <TOKEN>

A valid Bearer token for authorizing the request.

Acceptstring required
Example:application/json;version=2018-01-01

The accept header is used to influence what type of output is returned and in most cases the version of the output

Request body

idstring uuid required

The unique identifier (a GUID/UUID)

action'accept' | 'reject' | 'reopen' | 'revoke' required

The action to perform on the leave request resulting in a change of leaveRequestStatus The following transitions are possible per status

  • leaveRequestStatus = (1)submitted -> accept, reject or revoke(by employee)
  • leaveRequestStatus = (9)accepted -> revoke or reopen(by employee)
  • leaveRequestStatus = (3)rejected -> submitted
  • leaveRequestStatus = (10) accepted with revoke request -> accept of reject

Example request

[
  {
    "id": "b14acd0d-75d7-4fc8-8b22-4a3924585cab"
  }
]

Response

OK

contentobject

Example response

{
  "version": {
    "resourceVersion": "2018-12-31"
  },
  "messages": [
    {
      "type": "Warning",
      "description": "<some warning>",
      "id": "904d6856-6034-4624-bcbc-886188c115c5",
      "code": 12
    }
  ]
}

Changes

No recorded changes to this operation across all 6 revisions of this API.