The Turbine Labs API provides CRUD operations for core object types, and is mostly RESTy. The easiest way to interact with the API is with [tbnctl](https://docs.turbinelabs.io/advanced/tbnctl.html). If you want to make direct HTTP calls, however, you can obtain an access token using tbnctl, and then
Every row below was read from the vendor's own OpenAPI document. The summary text is theirs. What this registry adds is that each operation is indexed with its method, path, base URL and auth scheme, so a search for a capability can answer with a call rather than a name, and that the endpoint is probed on a schedule.
Specifications as held by the APIs.guru corpus, whose newest record is 2023-04-21. Operations the vendor has added since are not listed here; the origin links above are the vendor's own current documents.
base URLs: https://api.turbinelabs.io/v1.0
auth: a p i k e y
find it by capability: POST /search {"query":{"text":"..."}} returns these
operations with their invocation detail. Connect any agent client.
The Turbine Labs API provides CRUD operations for core object types, and is mostly RESTy. The easiest way to interact with the API is with [tbnctl](https://docs.turbinelabs.io/advanced/tbnctl.html). If you want to make direct HTTP calls, however, you can obtain an access token using tbnctl, and then pass it in the Authorization header, prefixed by `Token `: ```console curl -H "Authorization: Token
| method | path | what the vendor says it does |
|---|---|---|
GET | /admin/user/self | Returns the user object for the account authorized and making this request. Request the user object for an aut |
DELETE | /admin/user/self/access_token/{access-token-key} | Delete the specified access token. User Management |
GET | /admin/user/self/access_tokens | Lists Access Tokens that are configured for the authenticated user. User Management |
POST | /admin/user/self/access_tokens | Creates a new Access Token and associates it with the authenticated user. User Management |
GET | /changelog/adhoc | Allows an arbitrary filter to be specified and applied to the org\'s change log. Perform an adhoc query agains |
GET | /changelog/cluster-graph/{clusterKey} | get changes related to the indicated cluster Gets all changes to a cluster. Audit Log |
GET | /changelog/domain-graph/{domainKey} | get changes related to the indicated domain Gets all changes to a domain, the proxies that front the specified |
GET | /changelog/route-graph/{routeKey} | get changes related to the indicated route Gets all changes to a route, the domains associated with it, the sh |
GET | /changelog/shared-rules-graph/{sharedRulesKey} | get changes related to the indicated SharedRules Gets all changes associated with set of Shared Rules; the dom |
GET | /changelog/zone/{zoneKey} | get changes in a specified zone Retrieve all changes in the specified zone. Audit Log |
GET | /cluster | get clusters Get a list of clusters Cluster |
POST | /cluster | create cluster Create a new cluster Cluster |
GET | /cluster/{clusterKey} | get cluster Get details for an existing cluster Cluster |
PUT | /cluster/{clusterKey} | modify cluster Modify an existing cluster Cluster |
DELETE | /cluster/{clusterKey} | delete cluster Delete an existing cluster Cluster |
POST | /cluster/{clusterKey}/instances | add instance Add a new instance to a cluster Cluster |
DELETE | /cluster/{clusterKey}/instances/{instanceIdentifier} | remove instance Remove an instance from a cluster Cluster |
GET | /domain | get domains Get a list of domains Domain |
POST | /domain | create domain Create a new domain Domain |
GET | /domain/{domainKey} | get domain Get details for a single domain Domain |
DELETE | /domain/{domainKey} | delete domain Delete an existing domain Domain |
GET | /listener | list listeners Get a list of listeners Listener |
POST | /listener | create listener Create a new listener Listener |
GET | /listener/{listenerKey} | get listener Get details for a single listener Listener |
PUT | /listener/{listenerKey} | modify listener Modify an existing listener Listener |
DELETE | /listener/{listenerKey} | delete listener Delete existing listener Listener |
GET | /proxy | list proxies Get a list of proxies Proxy |
POST | /proxy | create proxy Create a new proxy Proxy |
GET | /proxy/{proxyKey} | get proxy Get details for a single proxy Proxy |
DELETE | /proxy/{proxyKey} | delete proxy Delete existing proxy Proxy |
GET | /route | get routes Get a list of routes Route |
POST | /route | create route Create a new route Route |
GET | /route/{routeKey} | get route Get details for an existing route Route |
PUT | /route/{routeKey} | modify route Modify an existing route Route |
DELETE | /route/{routeKey} | delete route Delete an existing route Route |
GET | /shared_rules | get shared_rules Get a list of shared_rules Shared Rules |
POST | /shared_rules | create shared_rules Create a new shared_rules object Shared Rules |
GET | /shared_rules/{sharedRulesKey} | get shared_rules object Get details for an existing shared_rules object Shared Rules |
PUT | /shared_rules/{sharedRulesKey} | modify shared_rules object Modify an existing shared_rules object Shared Rules |
DELETE | /shared_rules/{sharedRulesKey} | delete shared_rules object Delete an existing shared_rules object Route |
and 4 more operation(s) in this specification, all searchable.
specification origin: https://raw.githubusercontent.com/turbinelabs/api/master/swagger.yml
nothing on this page is a rating, an endorsement or a claim about quality. Reachability is what our probes observed from one network; answering is a floor under usefulness, not a measure of it.