> For the complete documentation index, see [llms.txt](https://api-docs.getflipturn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.getflipturn.com/remote-transactions.md).

# 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

```ts
{
  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

```ts
{
  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:**

```sh
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:**

```json
{
  "data": {
    "status": "Accepted"
  }
}
```

## POST /api/ocpp/remote-stop

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

### Request body

```ts
{
  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

```ts
{
  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:**

```sh
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:**

```json
{
  "data": {
    "status": "Accepted"
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://api-docs.getflipturn.com/remote-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.