Planning API (1.2.1)

Download OpenAPI specification:Download

The planning API provides information about plannings and their lifecycle.

You can find out more in our developer portal.

Changelog

  • rename security scheme

Health

Validate connection and accessibility of the API.

Returns a single `pong` string

The ping-endpoint can be used for validating a connection with the application. It will authenticate the caller and returns a pong response when everything is set-up correctly.

SecurityclientCredentials
Responses
200

Everything set-up correctly

401

Authentication required

get/ping
Response samples
text/plain
pong

Plannings

Endpoints used for retrieving information about plannings and its releases.

Get a cursor paged list of plannings

Returns a cursor paged list of plannings. Results are sorted by created_at in descending order. You can find out more about how to use cursors in our developer portal.

SecurityclientCredentials
Request
query Parameters
released_since
string <date-time>

When provided, only plannings which have been released since (exclusive) the given date will be returned.

Example: released_since=2021-01-01T10:15:30Z
cursor
string

Cursor of the page to retrieve.

limit
integer <int32> [ 1 .. 1000 ]
Default: 100

The maximum amount of plannings that should be returned in the response

Example: limit=100
Responses
200

OK

400

Bad request

401

Authentication required

get/plannings
Response samples
application/json
{
  • "plannings": [
    ],
  • "cursor": {
    }
}

Retrieve a released planning using a given planning id

Retrieves detailed information on the given released planning.

Note that information about releases are only stored for 2 weeks after the release was made. If you try to retrieve a release which is older than 2 weeks, you will get a 404 Not Found response.

SecurityclientCredentials
Request
path Parameters
id
required
string

The unique identifier of a planning

Responses
200

OK

401

Authentication required

404

Not found

get/plannings/{id}/releases/latest
Response samples
application/json
{
  • "release_metadata": {
    },
  • "routes": [
    ]
}

Location Workload Levelling

Endpoints used for managing location workload levelling sets.

Get location workload levelling set

Retrieves detailed information on the given location workload levelling set.

SecurityclientCredentials
Request
path Parameters
business_id
required
string^[a-zA-Z0-9.~\-_]+$

The unique identifier of an entity

Responses
200

OK

401

Authentication required

404

Not found

get/settings/location-workload-levelling-sets/{business_id}
Response samples
application/json
{
  • "business_id": "86b54c9d-21d7-4b37-af3d-25f03886153b",
  • "name": "Weekday",
  • "settings": [
    ]
}

Upsert location workload levelling set

Create or update a location workload levelling set. A unique ID (business_id) is required to identify the location workload levelling set. Calling this endpoint with an existing business_id will update the location workload levelling set.

SecurityclientCredentials
Request
path Parameters
business_id
required
string^[a-zA-Z0-9.~\-_]+$

The unique identifier of an entity

header Parameters
If-Match
string

Weak Etag used for optimistic locking.

Example: W/"24"
Request Body schema: application/json
name
string

The name of the location workload levelling set

Array of objects (LocationWorkloadLevellingSetting)
Responses
201

location workload levelling set created successful

204

location workload levelling set updated successful

400

Bad request

401

Authentication required

404

Not found

409

Conflict

412

This status is returned when an entity is updated with an outdated version in the If-Match header.

put/settings/location-workload-levelling-sets/{business_id}
Request samples
application/json
{
  • "name": "Weekday",
  • "settings": [
    ]
}
Response samples
application/problem+json
{}

Delete location workload levelling set

Delete a location workload levelling set by it's business_id.

SecurityclientCredentials
Request
path Parameters
business_id
required
string^[a-zA-Z0-9.~\-_]+$

The unique identifier of an entity

header Parameters
If-Match
string

Weak Etag used for optimistic locking.

Example: W/"24"
Responses
204

Delete successful

400

Bad request

401

Authentication required

404

Not found

412

This status is returned when an entity is updated with an outdated version in the If-Match header.

delete/settings/location-workload-levelling-sets/{business_id}
Response samples
application/problem+json
{}