---
title: 'POST /play/start'
description: 'Launch a remote gaming session'
---

# POST /play/start

Launch a remote gaming session

| Detail | Value |
|---|---|
| Operation ID | `startSession` |
| Method | `POST` |
| Path | `/play/start` |
| Connector | [ScatterKings](./) |

## Parameters

_No parameters._

## Request Body

| Field | Type |
|---|---|
| `GameID` | string |
| `Mode` | string |
| `Currency` | string |
| `Language` | string |
| `PlayerID` | string |
| `ClientType` | string |


## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select `startSession`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

**Required fields are marked — fill them or the call will fail at runtime.**

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream ScatterKings API reference.