> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automate.ax/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Automate.ax automations are TypeScript programs.
> Use Bun for installation and command examples.
> Use Automate.ax for the product name and automate.ax for the package, CLI, and domain.
> Treat documented public APIs as current; do not invent transitional or deprecated names.

# List feature flag segments

> Lists segments for one Vercel project.

`vercel.listFeatureFlagSegments` lists segments for one Vercel project.

```ts automations/list-feature-flag-segments.automation.ts theme={null}
import { automation } from "automate.ax"
import { vercel } from "automate.ax/vercel"

export default automation("List feature flag segments", () => {
  vercel.listFeatureFlagSegments({
    projectIdOrName: "prj_1",
    teamId: "team_1",
  })
})
```

## Input

* `projectIdOrName`: included in the runnable example and checked by the callable's TypeScript contract.
* `teamId`: included in the runnable example and checked by the callable's TypeScript contract.

Optional filters, pagination controls, request bodies, and provider enums remain visible in editor autocomplete. Unknown keys are rejected by TypeScript instead of being silently discarded.

## Output

Returns Vercel's typed collection response. Pagination metadata is included when the endpoint paginates. Public request and response fields use camelCase.

## Provider behavior

OAuth installations default `teamId` to the installed team; access-token connections must identify the intended scope when Vercel requires it. Automate.ax may retry this read safely. Vercel validates identifiers, permissions, and state transitions and returns its provider error when the request is not allowed.