APIs
Weik.io 2026.2Publish an API, open it to callers with subscriptions and limits, watch every call, receive webhooks, and set up gateways, hostnames and upstreams.
On this page
API management puts a gateway in front of any HTTP API, whether it’s an integration you built, your ERP’s REST interface or a public API such as Google’s. The gateway terminates TLS with certificates the platform obtains and renews, admits each caller by its subscription, rate limits the calls and logs each request with its trace. Devtest and production answer on their own hostnames, and each has its own keys.
These pages publish one API, finance/invoices, in front of the ERP, open it to the partner partner-x, and follow its calls.
A partner calls the API on the gateway at api.example.com with its API key. The gateway checks that the key belongs to the subscription finance/partner-x, applies its rate limit of 60 calls in 60 seconds and answers 429 when the limit is reached. It forwards the call to the upstream, which is an integration at a site or any HTTP service such as an ERP's REST interface. Each call becomes one trace with the gateway's step and the upstream's steps.
Pages#
weikio api deploy serves the version on an environment's gateway, and the first curl needs a subscription's key.Subscriptions and rate limits A subscription gives one caller access to APIs in one environment with an API key, a password, an OpenID Connect token or a client certificate, with its own limit and expiry.Watching the calls The gateway logs each request with its trace, splits failures into the server's side and the caller's, and every response's traceresponse header finds the call.Webhooks A webhook API version stores each call's body in a channel before it answers, and the caller's headers travel with it so an integration can check the sender's signature.Gateways and hostnames A gateway is one door of one environment, with its hostnames, the networks it admits, its client certificate rule, its limits and where its certificates come from.Gateways at sites A gateway served at a site accepts calls only on the addresses its enrolment gives it, and partners reach it through a hub gateway with no port opened at the site.Upstreams and routes An API version's routes and clusters are YARP's own configuration, and Weik.io adds the credential the gateway sends upstream and the connection settings around it.The gateway on a laptop The gateway runs alone on a laptop on plain HTTP, with the same code a hub and a site run, so you can deploy, subscribe, call and try every rule locally.