Automate Turbinelabs Turbine Labs

What Turbinelabs Turbine Labs is

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

API host: api.turbinelabs.io

What HumDay can do in Turbinelabs Turbine Labs

22 documented operations change something in Turbinelabs Turbine Labs.

• POSTcreate zone/zone
• POSTcreate proxy/proxy
• POSTcreate route/route
• POSTcreate domain/domain
• POSTcreate cluster/cluster
• POSTcreate listener/listener
• POSTcreate sharedrules/shared_rules
• POSTadd instance/cluster/{clusterKey}/instances
• DELETEdelete zone/zone/{zoneKey}
• DELETEdelete proxy/proxy/{proxyKey}
• DELETEdelete route/route/{routeKey}
• PUTmodify route/route/{routeKey}
• DELETEdelete domain/domain/{domainKey}
• DELETEdelete cluster/cluster/{clusterKey}
• PUTmodify cluster/cluster/{clusterKey}
• DELETEdelete listener/listener/{listenerKey}
• PUTmodify listener/listener/{listenerKey}
• DELETEdelete sharedrules object/shared_rules/{sharedRulesKey}
• PUTmodify sharedrules object/shared_rules/{sharedRulesKey}
• POSTCreates a new Access Token and associates it with the authenticated user./admin/user/self/access_tokens
• DELETEremove instance/cluster/{clusterKey}/instances/{instanceIdentifier}
• DELETEDelete the specified access token./admin/user/self/access_token/{access-token-key}

What HumDay can read from Turbinelabs Turbine Labs

These are the operations a schedule or a trigger can watch.

• GETget a list of zones/zone
• GETlist proxies/proxy
• GETlist listeners/listener
• GETget routes/route
• GETget domains/domain
• GETget clusters/cluster
• GETget sharedrules/shared_rules
• GETget zone/zone/{zoneKey}
• GETget proxy/proxy/{proxyKey}
• GETget route/route/{routeKey}
• GETget domain/domain/{domainKey}
• GETget cluster/cluster/{clusterKey}
• GETget listener/listener/{listenerKey}
• GETget sharedrules object/shared_rules/{sharedRulesKey}
• GETReturns the user object for the account authorized and making this request./admin/user/self
• GETLists Access Tokens that are configured for the authenticated user./admin/user/self/access_tokens
• GETAllows an arbitrary filter to be specified and applied to the org\'s change log./changelog/adhoc
• GETget changes in a specified zone/changelog/zone/{zoneKey}
• GETget changes related to the indicated route/changelog/route-graph/{routeKey}
• GETget changes related to the indicated domain/changelog/domain-graph/{domainKey}
• GETget changes related to the indicated cluster/changelog/cluster-graph/{clusterKey}
• GETget changes related to the indicated SharedRules/changelog/shared-rules-graph/{sharedRulesKey}

How automating Turbinelabs Turbine Labs works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Turbinelabs Turbine Labs account.
4. Grant access, then go live. You approve the specific Turbinelabs Turbine Labs operations it may use — and only those.

Automate Turbinelabs Turbine Labs with these

• Cloudflare3122 operations
• Netboxdemo NetBox386 operations
• Linode342 operations
• Clever Cloud324 operations
• DRACOON276 operations
• Box Platform258 operations
• Netlify's documentation120 operations
• Meshery .75 operations
• Ritc66 operations
• Microsoft Custom Vision Training Client48 operations
• Ably Control22 operations
• Ably Platform22 operations

Categories

• Cloud

Questions about Turbinelabs Turbine Labs automation

Can HumDay connect to Turbinelabs Turbine Labs?

Yes. HumDay reads Turbinelabs Turbine Labs's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 44 operations are documented.

Do I need to write code to automate Turbinelabs Turbine Labs?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Turbinelabs Turbine Labs account.

What can HumDay do in Turbinelabs Turbine Labs?

22 of the 44 documented operations change something in Turbinelabs Turbine Labs, and 22 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Turbinelabs Turbine Labs account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Turbinelabs Turbine Labs is held behind that approval.

Where this came from

The operations above are read from a published API description for Turbinelabs Turbine Labs at raw.githubusercontent.com/turbinelabs/api/master/swagger.yml. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.