---
title: 'PATCH /segments/{segment_id}'
description: 'Update segment'
---

# PATCH /segments/{segment_id}

Update segment

| Detail | Value |
|---|---|
| Operation ID | `igaming.updateSegment` |
| Method | `PATCH` |
| Path | `/segments/{segment_id}` |
| Connector | [OneSignal](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `segment_id` | path | string | **Yes** |

## Request Body

| Field | Type |
|---|---|
| `name` | string |
| `filters` | array |


## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your OneSignal connection from the Connection dropdown.
3. In the Operation dropdown, select `igaming.updateSegment`.
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 OneSignal API reference.