Can HumDay connect to TYK Gateway?

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

Do I need to write code to automate TYK Gateway?

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 TYK Gateway account.

What can HumDay do in TYK Gateway?

11 of the 18 documented operations change something in TYK Gateway, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my TYK Gateway 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 TYK Gateway is held behind that approval.

Automate TYK Gateway

HumDay reads TYK Gateway’s own published API description and derives 18 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What HumDay can do in TYK Gateway

11 documented operations change something in TYK Gateway.

POSTCreate a new API token with the session object defined in the body/tyk/keys/create
POSTAdd a pre-specified API token with the session object defined in the body, this operatin creates a custom token that dsoes not use the gateway naming convention for tokens/tyk/keys/{keyId}
POSTCreate an API Definition object/tyk/apis/
DELETEDeletes an API Definition object, if it exists/tyk/apis/{apiID}
PUTUpdates an API Definition object, if it exists/tyk/apis/{apiID}
DELETERemove this API token from the gateway, this will completely destroy the token and metadata associated with the token and instantly stop access from being granted/tyk/keys/{keyId}
PUTUpdate an API token with the session object defined in the body, this operatin overwrites the existing object/tyk/keys/{keyId}
POSTCreate a new OAuth client/tyk/oauth/clients/create
POSTThe final request from an authorising party for a redirect URI during the Tyk OAuth flow/tyk/oauth/authorize-client/
DELETEInvalidate a refresh token/tyk/oauth/refresh/{keyId}
DELETEDelete the OAuth client/tyk/oauth/clients/{apiId}/{clientId}

What HumDay can read from TYK Gateway

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

GETGets a list of API Definition objects that are currently live on the gateway/tyk/apis/
GETGets a list of key IDs (will only work with non-hashed installations)/tyk/keys/
GETGets the health check values for an API if it is being recorded/tyk/health/
GETWill reload the targetted gateway/tyk/reload/
GETWill reload the cluster via the targeted gateway/tyk/reload/group
GETGets an API Definition object, if it exists/tyk/apis/{apiID}
GETGet a list of OAuth clients bound to this back end/tyk/oauth/clients/{apiId}

How automating TYK Gateway works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
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.
See it proven. The program runs and shows you the result before it is allowed near your live TYK Gateway account.
Grant access, then go live. You approve the specific TYK Gateway operations it may use — and only those.