Planning API (1.1.0)

Download OpenAPI specification:Download

The planning API provides information about plannings and their lifecycle.

You can find out more in our developer portal.

Changelog

  • GET /planning/v1/plannings now also shows the planning name and planning labels.
  • The following endpoints are marked for removal on 30/06/2025. More information on how to migrate can be found here.
    • GET /planning/v0/releases
    • GET /planning/v0/plannings/{id}/releases/latest

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.

Securitykeycloak
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.

Securitykeycloak
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.

Securitykeycloak
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": [
    ]
}