Default off: authorize an opaque TCP connector route
Signed account session, current workspace ADMIN or OWNER and verified email; same-site JSON is mandatory. The organization comes only from the session. Requests are closed and limited to 4096 bytes. TCP forwarding is opaque and does not evaluate SQL or API commands. Default off. Explicit accept_terms:true authorizes a saved tcp_ip resource with a numeric IPv4/IPv6 address and explicit port. Current paid active entitlement is required. Queue an identifier-only worker job; the worker probes only the derived tenant gateway capability endpoint. No HTTPS origin is required and the shared fleet never dials the saved target. Idempotent while the current route is ready or provisioning.
Authorization
AccountSessionCookie The signed HttpOnly account session the web app holds after sign-in (also accepted as a Bearer acct_ token).
In: cookie
Path Parameters
Saved resource UUID in the current workspace; also the TCP route UUID.
uuidRequest Body
application/json
Response Body
application/json
curl -X POST "https://example.com/v1/public/account/workspace/deployments/resources/497f6eca-6276-4993-bfeb-53cbbbba6f08/tcp/activate" \ -H "Content-Type: application/json" \ -d '{ "accept_terms": true }'{ "resources": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "type": "url", "resource": "string", "label": "string", "created_at": "2019-08-24T14:15:22Z", "status": "connected", "status_message": "string", "tcp": { "route_id": "dd833dbc-f3c5-44d9-98a2-7ba12ebc8160", "generation": 1, "state": "provisioning", "gateway_url": "http://example.com", "connector_online": true, "last_seen_at": "2019-08-24T14:15:22Z", "credentials_available": true, "message": "string" } } ], "resource_limit": 50, "tcp_enabled": true}Save a resource to one gateway's inventory POST
Signed account session, current workspace ADMIN or OWNER and verified email; same-site JSON is mandatory. Saves to the gateway deployment_id names, else the primary; an id the workspace does not hold is 404 GATEWAY_NOT_FOUND. Saving never activates routing; a repeat returns the saved resource. At most 50 resources per gateway.
Revoke a TCP route and both role credentials POST
Signed account session, current workspace ADMIN or OWNER and verified email; same-site JSON is mandatory. The organization comes only from the session. Requests are closed and limited to 4096 bytes. TCP forwarding is opaque and does not evaluate SQL or API commands. Works while the TCP feature is disabled. Increments generation, clears both role credentials, and removes tickets and live leases. Existing broker legs close by their last valid 30-second lease expiry. Other resources and HTTPS routing are unchanged.