Admin23

Agent Permissions4

API Keys1

Apps6

Authentication27

Automations20

Bootstrap4

Capability Sources71

Cloud4

Codemode Runs2

Config Objects16

Connectors30

Deprecated12

Desktop Policies8

Diagnostics3

Direct uploads6

Documents12

Gateway Usage Limits16

GitHub11

Inference15

Inference Providers40

Internal19

Invitations5

LLM Providers18

Managed deployments8

Marketplaces17

Members3

OAuth16

Organizations25

Permissions11

Plugins20

Resources2

SCIM16

SSO12

System4

Teams7

Telemetry4

Users7

Webhooks4

Workbot3

Workers3

Workflow Runs1

Workflows11

Managed deployments

Create a managed deployment

Changed on Oct 14, 2026

Records a new installation target (cloud account or project, region, address). Nothing is launched or billed until an owner prepares and approves it in their cloud. Agents confirm the target, address and that the person's cloud account will be billed before calling this.

post/v1/managed-deployments

Request

Base URL: https://api.openworklabs.com
URL: https://api.openworklabs.com/v1/managed-deployments
Auth: one of:
- API key in header x-api-key
- HTTP bearer

Request body

Response

Create a managed deployment

Changes

Oct 14, 20260005cd4e85a8 Revision changes
- breaking
  added subschema #1 subschema #2 to the response body oneOf list for the response status
- breaking
  the response's body type changed from object to no type for status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- info
  added subschema #2 to the request body oneOf list
Oct 9, 2026cc8a41bb846e Revision changes
- info
  endpoint added

Operation history