<!-- Generated by scripts/openapi/build-spec.ts from docs/openapi.json. Do not edit by hand. -->

# Request a go-live review for a connector

```http
POST https://api.onehazel.com/onehazel-api/operators/me/connect/marketplace/{key}/request-go-live
```

Notifies the operator team about an activated connector and returns the review URL. The response carries `ready` and `missing`. `missing` lists each required module that is not conformant and each vendor credential the connection does not hold yet, as `credential:<field>`. When anything is missing it still notifies, but `ready` is false and the notification says the connection needs values. It never changes a connection status.

Section: [Onboarding](./)  
Operation id: `postOperatorsMeConnectMarketplaceByKeyRequestGoLive`

## Authentication

Signed-in session token (`Authorization: Bearer <session token>`).

## Parameters

| Name | In | Required | Description |
|---|---|---|---|
| `key` | path | yes | |

## Responses

`200` `{ "success": true, "data": ... }`

Errors return `{ "success": false, "error": { "code": "...", "message": "..." } }` with a 4xx or 5xx status.

## Example

```bash
curl -X POST "https://api.onehazel.com/onehazel-api/operators/me/connect/marketplace/{key}/request-go-live" \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"
```

Machine-readable: [openapi.yaml](/openapi.yaml), [openapi.json](/openapi.json).