---
title: vercel curl
product: vercel
url: /docs/cli/curl
canonical_url: "https://vercel.com/docs/cli/curl"
last_updated: 2026-05-28
type: reference
prerequisites:
  - /docs/cli
related:
  - /docs/security/deployment-protection
  - /docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation
  - /docs/cli
  - /docs/cli/traces
  - /docs/cli/global-options
summary: Learn how to make HTTP requests to your Vercel deployments with automatic deployment protection bypass using the vercel curl CLI command.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# vercel curl

> **⚠️ Warning:** The `vercel curl` command is currently in beta. Features and behavior may change.

The `vercel curl` command works like `curl`, but automatically handles deployment protection bypass tokens for you. When your project has [Deployment Protection](/docs/security/deployment-protection) enabled, this command lets you test protected deployments without manually managing bypass secrets.

The command runs the system `curl` command with the same arguments you provide, but adds an [`x-vercel-protection-bypass`](/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation#using-protection-bypass-for-automation) header with a valid token. This makes it simple to test API endpoints, check responses, or debug issues on protected deployments.

> **💡 Note:** This command is available in Vercel CLI v48.8.0 and later. If you're using an older version, see [Updating Vercel CLI](/docs/cli#updating-vercel-cli).

## Usage

```bash filename="terminal"
vercel curl [path]
```

*Using the \`vercel curl\` command to make an HTTP request to a deployment.*

## Examples

### Basic request

Make a GET request to your production deployment:

```bash filename="terminal"
vercel curl /api/hello
```

*Making a GET request to the \`/api/hello\` endpoint on your production deployment.*

### POST request with data

Send a POST request with JSON data. Use the `--` separator to pass flags through to the underlying `curl`:

```bash filename="terminal"
vercel curl /api/users -- --request POST --header "Content-Type: application/json" --data '{"name":"John"}'
```

*Making a POST request with JSON data to create a new user. The \`--\` separator
passes everything after it to \`curl\`.*

### Request specific deployment

Test a specific deployment by its URL:

```bash filename="terminal"
vercel curl /api/status --deployment https://my-app-abc123.vercel.app
```

*Making a request to a specific deployment instead of the production
deployment.*

### Verbose output

See detailed request information by passing curl's `-v` flag after `--`:

```bash filename="terminal"
vercel curl /api/data -- -v
```

*Using curl's \`-v\` flag for verbose output, which shows headers and connection details.*

### Capture a request trace

Capture a session trace for the request and print the trace request ID:

```bash filename="terminal"
vercel curl --trace /api/hello
```

*Using the \`--trace\` option to capture a request trace.*

After the request completes, the command prints a `vercel traces get` command you can run to inspect the trace. See [`vercel traces`](/docs/cli/traces) for details.

## How it works

When you run `vercel curl`:

1. The CLI finds your linked project (or you can specify one with [`--scope`](/docs/cli/global-options#scope))
2. It gets the latest production deployment URL (or uses the deployment you specified)
3. It retrieves or generates a deployment protection bypass token
4. It runs the system `curl` command with the bypass token in the `x-vercel-protection-bypass` header

The command requires `curl` to be installed on your system.

## Unique options

These are options that only apply to the `vercel curl` command. To pass flags through to the underlying `curl` command, place them after the `--` separator.

### Deployment

The `--deployment` option lets you specify a deployment ID or URL to request instead of using the production deployment.

```bash filename="terminal"
vercel curl /api/hello --deployment https://my-app-abc123.vercel.app
```

*Using the \`--deployment\` option to target a specific deployment.*

### Protection bypass

The `--protection-bypass` option lets you provide your own deployment protection bypass secret instead of automatically generating one. This is useful when you already have a bypass secret configured.

```bash filename="terminal"
vercel curl /api/hello --protection-bypass your-secret-here
```

*Using the \`--protection-bypass\` option with a manual secret.*

You can also use the [`VERCEL_AUTOMATION_BYPASS_SECRET`](/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation#using-protection-bypass-for-automation) environment variable:

```bash filename="terminal"
export VERCEL_AUTOMATION_BYPASS_SECRET=your-secret-here
vercel curl /api/hello
```

*Setting the bypass secret as an environment variable.*

### Yes

The `--yes` option, shorthand `-y`, skips the confirmation prompt when linking is required. Use it in non-interactive environments like CI, or run [`vercel link`](/docs/cli/link) ahead of time to link your project and avoid the prompt entirely.

```bash filename="terminal"
vercel curl /api/hello --yes
```

*Skipping the link confirmation prompt with \`--yes\`.*

### Trace

The `--trace` option captures a [request trace](/docs/cli/traces) for the request and prints the trace request ID once the response completes. When targeting a production deployment, the command prompts for confirmation unless `--yes` is set.

```bash filename="terminal"
vercel curl --trace /api/hello
```

*Using the \`--trace\` option to capture a request trace.*

### JSON

The `--json` option only applies with `--trace`. Instead of streaming the response body to stdout, the command captures it and emits a JSON envelope with the response body and request ID:

```bash filename="terminal"
vercel curl --trace --json /api/hello
```

```json filename="stdout"
{
  "response": "...",
  "requestId": "abc-123"
}
```

*Using the \`--json\` option with \`--trace\` to emit a JSON envelope.*

## Troubleshooting

### curl command not found

Make sure `curl` is installed on your system:

```bash filename="terminal"
# macOS (using Homebrew)
brew install curl

# Ubuntu/Debian
sudo apt-get install curl

# Windows (using Chocolatey)
choco install curl
```

*Installing curl on different operating systems.*

### No deployment found for the project

Make sure you're in a directory with a linked Vercel project and that the project has at least one deployment:

```bash filename="terminal"
# Link your project
vercel link

# Deploy your project
vercel deploy
```

*Linking your project and creating a deployment.*

### Failed to get deployment protection bypass token

If automatic token creation fails, you can create a bypass secret manually in the Vercel Dashboard:

1. Go to your project's **Settings** → **Deployment Protection**
2. Find "Protection Bypass for Automation"
3. Click "Create" or "Generate" to create a new secret
4. Copy the generated secret
5. Use it with the `--protection-bypass` flag or [`VERCEL_AUTOMATION_BYPASS_SECRET`](/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation#using-protection-bypass-for-automation) environment variable

### No deployment found for ID

When using `--deployment`, verify that:

- The deployment ID or URL is correct
- The deployment belongs to your linked project
- The deployment hasn't been deleted

## Related

- [Deployment Protection](/docs/security/deployment-protection)
- [vercel deploy](/docs/cli/deploy)
- [vercel inspect](/docs/cli/inspect)


---

[View full sitemap](/docs/sitemap)