OpenAPI reference

Start CPO Session Command

POST/commands/START_SESSION

OCPI 2.1.1 CPO Commands interface endpoint for POST /commands/START_SESSION. The eMSP requests the CPO to forward a START_SESSION command to the charge point. The immediate response indicates whether

API: OCPI 2.1.1 (CPO) · Module: Commands (CPO)
Base path: /commands · Base URL: https://ocpi-api.gridos.co/ocpi/cpo/2.1.1

Overview

POST /commands/START_SESSION

Absolute URL: https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION

OCPI 2.1.1 CPO Commands interface endpoint for POST /commands/START_SESSION. The eMSP requests the CPO to forward a START_SESSION command to the charge point. The immediate response indicates whether the CPO accepted the request for delivery. The final command result is returned asynchronously to the supplied response_url.

Requires authentication. Use Authorization: Token <token>. See OCPI credentials.

How to call

Quick Shell sample (set OCPI_TOKEN when auth is required). Full Python and TypeScript under Examples.

1curl -sS -X POST 'https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION' \
2  -H "Authorization: Token $OCPI_TOKEN" \
3  -H 'Content-Type: application/json' \
4  -d '{"response_url":"https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234","token":{"uid":"100012","type":"RFID","auth_id":"FA54320","visual_number":"DF000-2001-8999","issuer":"TheNewMotion","valid":true,"whitelist":"ALWAYS","last_updated":"2015-06-21T22:39:05Z"},"location_id":"LOC1"}'

Request

Request body

application/json · Required

Schema: StartSession

Field	Type	Required	Description
`response_url`	`string`	Yes	—
`token`	`CommandToken`	Yes	OCPI 2.1.1 Token object as embedded in command requests.
`location_id`	`string`	Yes	—
`evse_uid`	`string`	No	—

Request examples

Example 1

1{
2  "response_url": "https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234",
3  "token": {
4    "uid": "100012",
5    "type": "RFID",
6    "auth_id": "FA54320",
7    "visual_number": "DF000-2001-8999",
8    "issuer": "TheNewMotion",
9    "valid": true,
10    "whitelist": "ALWAYS",
11    "last_updated": "2015-06-21T22:39:05Z"
12  },
13  "location_id": "LOC1"
14}

Example 2

1{
2  "response_url": "https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/5678",
3  "token": {
4    "uid": "APP-USER-01",
5    "type": "OTHER",
6    "auth_id": "EMP-7788",
7    "issuer": "Example eMSP",
8    "valid": true,
9    "whitelist": "ALLOWED",
10    "last_updated": "2015-06-22T07:30:00Z"
11  },
12  "location_id": "LOC2",
13  "evse_uid": "EVSE-22"
14}

Responses

Status	Description	Schema
`200`	Successful Response	`CommandResponseEnvelope`
`400`	Invalid or missing parameters (HTTP 200, OCPI envelope)	`—`
`401`	Unauthorized	`—`
`422`	Validation Error	`HTTPValidationError`

`200` — successful response

application/json

Schema: CommandResponseEnvelope

Field	Type	Required	Description
`status_code`	`integer`	No	Default: `1000`
`status_message`	`string`	No	—
`timestamp`	`string (date-time)`	No	—
`data`	`CommandResponse`	No	`CommandResponse`

Response example

1{
2  "status_code": 1000,
3  "status_message": "Success",
4  "timestamp": "2015-06-29T22:39:09Z",
5  "data": {
6    "result": "ACCEPTED"
7  }
8}

`400` — invalid or missing parameters (HTTP 200, OCPI envelope)

application/json

Response example

1{
2  "status_code": 2001,
3  "status_message": "Invalid or missing parameters",
4  "timestamp": "2025-01-01T00:00:00Z",
5  "doc_url": "https://github.com/ocpplab/ocpi-gateway/blob/main/docs/errors.md#2001-invalid-parameters",
6  "errors": [
7    {
8      "field": "country_code",
9      "message": "expected 'NL' to match Token A identity",
10      "type": "value_error.identity_mismatch"
11    }
12  ]
13}

`401` — unauthorized

application/json

Response example

1{
2  "status_code": 2000,
3  "status_message": "Unauthorized",
4  "timestamp": "2025-01-01T00:00:00Z"
5}

`422` — validation error

application/json

Schema: HTTPValidationError

Field	Type	Required	Description
`detail`	`ValidationError[]`	No	`Detail`

Response example

1{
2  "detail": [
3    {
4      "loc": [],
5      "msg": "string",
6      "type": "string",
7      "input": {
8        "_type": "Input"
9      },
10      "ctx": {
11        "_type": "Context"
12      }
13    }
14  ]
15}

Examples

Shell, Python, and TypeScript (set OCPI_TOKEN when auth is required).

1curl -sS -X POST 'https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION' \
2  -H "Authorization: Token $OCPI_TOKEN" \
3  -H 'Content-Type: application/json' \
4  -d '{"response_url":"https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234","token":{"uid":"100012","type":"RFID","auth_id":"FA54320","visual_number":"DF000-2001-8999","issuer":"TheNewMotion","valid":true,"whitelist":"ALWAYS","last_updated":"2015-06-21T22:39:05Z"},"location_id":"LOC1"}'

OpenAPI reference

Start CPO Session Command

POST/commands/START_SESSION

OCPI 2.1.1 CPO Commands interface endpoint for POST /commands/START_SESSION. The eMSP requests the CPO to forward a START_SESSION command to the charge point. The immediate response indicates whether

API: OCPI 2.1.1 (CPO) · Module: Commands (CPO)
Base path: /commands · Base URL: https://ocpi-api.gridos.co/ocpi/cpo/2.1.1

Overview

POST /commands/START_SESSION

Absolute URL: https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION

Requires authentication. Use Authorization: Token <token>. See OCPI credentials.

How to call

Quick Shell sample (set OCPI_TOKEN when auth is required). Full Python and TypeScript under Examples.

1curl -sS -X POST 'https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION' \
2  -H "Authorization: Token $OCPI_TOKEN" \
3  -H 'Content-Type: application/json' \
4  -d '{"response_url":"https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234","token":{"uid":"100012","type":"RFID","auth_id":"FA54320","visual_number":"DF000-2001-8999","issuer":"TheNewMotion","valid":true,"whitelist":"ALWAYS","last_updated":"2015-06-21T22:39:05Z"},"location_id":"LOC1"}'

Request

Request body

application/json · Required

Schema: StartSession

Field	Type	Required	Description
`response_url`	`string`	Yes	—
`token`	`CommandToken`	Yes	OCPI 2.1.1 Token object as embedded in command requests.
`location_id`	`string`	Yes	—
`evse_uid`	`string`	No	—

Request examples

Example 1

1{
2  "response_url": "https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234",
3  "token": {
4    "uid": "100012",
5    "type": "RFID",
6    "auth_id": "FA54320",
7    "visual_number": "DF000-2001-8999",
8    "issuer": "TheNewMotion",
9    "valid": true,
10    "whitelist": "ALWAYS",
11    "last_updated": "2015-06-21T22:39:05Z"
12  },
13  "location_id": "LOC1"
14}

Example 2

1{
2  "response_url": "https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/5678",
3  "token": {
4    "uid": "APP-USER-01",
5    "type": "OTHER",
6    "auth_id": "EMP-7788",
7    "issuer": "Example eMSP",
8    "valid": true,
9    "whitelist": "ALLOWED",
10    "last_updated": "2015-06-22T07:30:00Z"
11  },
12  "location_id": "LOC2",
13  "evse_uid": "EVSE-22"
14}

Responses

Status	Description	Schema
`200`	Successful Response	`CommandResponseEnvelope`
`400`	Invalid or missing parameters (HTTP 200, OCPI envelope)	`—`
`401`	Unauthorized	`—`
`422`	Validation Error	`HTTPValidationError`

`200` — successful response

application/json

Schema: CommandResponseEnvelope

Field	Type	Required	Description
`status_code`	`integer`	No	Default: `1000`
`status_message`	`string`	No	—
`timestamp`	`string (date-time)`	No	—
`data`	`CommandResponse`	No	`CommandResponse`

Response example

1{
2  "status_code": 1000,
3  "status_message": "Success",
4  "timestamp": "2015-06-29T22:39:09Z",
5  "data": {
6    "result": "ACCEPTED"
7  }
8}

`400` — invalid or missing parameters (HTTP 200, OCPI envelope)

application/json

Response example

1{
2  "status_code": 2001,
3  "status_message": "Invalid or missing parameters",
4  "timestamp": "2025-01-01T00:00:00Z",
5  "doc_url": "https://github.com/ocpplab/ocpi-gateway/blob/main/docs/errors.md#2001-invalid-parameters",
6  "errors": [
7    {
8      "field": "country_code",
9      "message": "expected 'NL' to match Token A identity",
10      "type": "value_error.identity_mismatch"
11    }
12  ]
13}

`401` — unauthorized

application/json

Response example

1{
2  "status_code": 2000,
3  "status_message": "Unauthorized",
4  "timestamp": "2025-01-01T00:00:00Z"
5}

`422` — validation error

application/json

Schema: HTTPValidationError

Field	Type	Required	Description
`detail`	`ValidationError[]`	No	`Detail`

Response example

1{
2  "detail": [
3    {
4      "loc": [],
5      "msg": "string",
6      "type": "string",
7      "input": {
8        "_type": "Input"
9      },
10      "ctx": {
11        "_type": "Context"
12      }
13    }
14  ]
15}

Examples

Shell, Python, and TypeScript (set OCPI_TOKEN when auth is required).

1curl -sS -X POST 'https://ocpi-api.gridos.co/ocpi/cpo/2.1.1/commands/START_SESSION' \
2  -H "Authorization: Token $OCPI_TOKEN" \
3  -H 'Content-Type: application/json' \
4  -d '{"response_url":"https://example.com/ocpi/emsp/2.1.1/commands/START_SESSION/1234","token":{"uid":"100012","type":"RFID","auth_id":"FA54320","visual_number":"DF000-2001-8999","issuer":"TheNewMotion","valid":true,"whitelist":"ALWAYS","last_updated":"2015-06-21T22:39:05Z"},"location_id":"LOC1"}'

Start CPO Session Command

Overview

How to call

Request

Request body

Request examples

Responses

`200` — successful response

`400` — invalid or missing parameters (HTTP 200, OCPI envelope)

`401` — unauthorized

`422` — validation error

Examples

Is this helpful?

AI Tools

On this page

Start CPO Session Command

Overview

How to call

Request

Request body

Request examples

Responses

`200` — successful response

`400` — invalid or missing parameters (HTTP 200, OCPI envelope)

`401` — unauthorized

`422` — validation error

Examples

Is this helpful?

AI Tools

On this page