This page focuses on getting started with Tyk Cloud, If you are looking for information on Tyk Self-Managed, please refer to the Getting Started with Tyk Self-Managed Guide.
My First API
).http://httpbin.org
).Edge Gateways
generally provide low-latency, regionally distributed API processing, ideal for a global user base.Regular Gateways
centralize API management, offering comprehensive API processing without additional edge optimizations.Active
will publish your API and make it public. When in the Disabled
state, your API will stay in a draft state until you are ready to publish it. This is a required field; for this guide, we will set it to Active
.Internal
or External
, determining whether you want to keep your API accessible only through Tyk or to external services, respectively. This is a required field; for this guide, we will set it to External
.path
Tyk API will use to proxy your API requests. So a request made to this URL https://<tyk-clou-url>/<listen-path>
will be proxied to the upstream URL configured above.
My First API
, which we created in the previous step. You can:
curl
to send a request to your API endpoint.curl
:
{YOUR_API_KEY_ID}
with the actual key ID and {YOUR_TYK_GATEWAY_URL}
with your gateway’s URL.200
status code.