Create a connector of your own

POST
/v1/workspace-connectors

Makes a connector named ws/<workspace>/<name> and says where its image is pushed (repository). Asking again for a name you already made returns the same connector. Push the image there, then publish a version with POST /v1/workspace-connectors/{name}/versions.

Requires an API key with the workspace:write scope.

Authorization

apiKey
headerAuthorizationBearer <token>

A secret API key from the dashboard (Developers → API keys): vl_live_…, or vl_test_… for test mode. Each operation says which scope the key needs.

Request Body

application/json
  1. body
name*string

The connector name: lower-case letters, digits and dashes, starting with a letter (up to 40 characters).

Match^[a-z][a-z0-9-]{0,39}$

Response Body

The connector, and the repository its image is pushed to

application/json
  1. response
connectorId*string
Length1 <= length
name*string
Match^[a-z][a-z0-9-]{0,39}$
repository*string
Length1 <= length
published*|null
latestVersion*integer
Range0 <= value
requirements*|null
Example Request
curl -X POST https://api.vlayers.ai/v1/workspace-connectors \  -H "Authorization: Bearer $VOICELAYER_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "name": "telegram"  }'
Example Response
{  "connectorId": "ws/0192f5a1-5e6f-7a7b-8c8d-9e0f1a2b3c45/telegram",  "name": "telegram",  "repository": "registry.vlayers.ai/0192f5a1-5e6f-7a7b-8c8d-9e0f1a2b3c45/0192f5c2-6f7a-7b9c-8d1e-2f3a4b5c6d78",  "published": {    "version": 3,    "versionId": "0192f5d5-9cad-7ebf-9a4b-5c6d7e8f9012",    "publishedAt": "2026-10-20T15:04:05.000Z"  },  "latestVersion": 3,  "requirements": {    "handshakeToken": false,    "primary": true,    "hosts": [      "api.telegram.org"    ]  }}