Remote Start / Stop

Send a command to a charger to start a charging session. These endpoints wrap the OCPP RemoteStartTransaction / RemoteStopTransaction messages (OCPP 1.6) and RequestStartTransaction / RequestStopTransaction messages (OCPP 2.0.1).

POST /api/ocpp/remote-start

Sends a remote start command to the charger for the given port. If the request is accepted, the charger will unlock the connector and begin a transaction as if a user had initiated it locally.

Request body

{
  portId: number;        // Flipturn charging port ID
  idTag?: string;        // Optional identifier (RFID UID, token, etc) to associate with the transaction. Max 20 characters.
  idTokenType?: string;  // Optional. OCPP 2.0.1 only. See below for valid values. Defaults to 'Central'.
}

If idTag is omitted, the default remote-start identifier is used.

idTokenType values (OCPP 2.0.1 only):

Value	Description
Central	Server-side identifier (default)
eMAID	E-Mobility Account Identifier
ISO14443	RFID tag (ISO 14443)
ISO15693	RFID tag (ISO 15693)
KeyCode	Key code / PIN
Local	Locally known identifier
MacAddress	MAC address
NoAuthorization	Charger should start without authorizing an id

This field is ignored for OCPP 1.6 chargers.

Response

{
  data: {
    status: 'Accepted' | 'Rejected';
  }
}

Status	Meaning
Accepted	The charger accepted the remote start request
Rejected	The charger rejected the request (for example the connector is unavailable)

Example

Request:

curl -X POST "https://api.getflipturn.com/api/ocpp/remote-start" \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{
    "portId": 34,
    "idTag": "RFID001"
  }'

Response:

{
  "data": {
    "status": "Accepted"
  }
}

POST /api/ocpp/remote-stop

Sends a remote stop command to the charger for an active transaction.

Request body

{
  portId: number;         // Flipturn charging port ID
  transactionId: string;  // The OCPP transaction ID of the session to stop
}

For OCPP 1.6 chargers, transactionId must be a numeric string (e.g. "8675309") — the underlying OCPP 1.6 RemoteStopTransaction message requires an integer. For OCPP 2.0.1 chargers it may be any string (typically a UUID).

Response

{
  data: {
    status: 'Accepted' | 'Rejected';
  }
}

Status	Meaning
Accepted	The charger accepted the remote stop request
Rejected	The charger rejected the request (for example the transaction is not known)

Example

Request:

curl -X POST "https://api.getflipturn.com/api/ocpp/remote-stop" \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{
    "portId": 34,
    "transactionId": "8675309"
  }'

Response:

{
  "data": {
    "status": "Accepted"
  }
}