Provider API Key Management

If you publish an API on Zyla API Hub and your API already has its own key, you add that key once. Zyla then gives each customer their own key. You do not create, send, or manage a key for every customer.

The key you give Zyla:
When you add your API, the Access Control step is where you enter the authentication your API already uses. Add the name, the value, whether it goes in a Header or a Parameter, and a short description.

Zyla keeps that secret and attaches it to every request it sends to your API. Your customers never see it, and you only set it up once, even if many people subscribe.

The full publishing steps, including this one, are here: https://helpcenter.zylalabs.com/adding-your-api-on-zyla-api-hub

The key each customer receives:
Every customer has one Zyla account and one Zyla API key. That same key works for every API they subscribe to on the Hub, including yours. The plan they choose sets what they can call and their limits.

After they subscribe, they copy the key from their Zyla dashboard and send it as a Bearer token:

Authorization: Bearer access_key

Zyla checks that key, applies the customer's plan, and then calls your API with the secret you configured. You do not issue a separate key on your side for each customer.

What you do not need to do:
You do not hand your own key to customers, and you do not generate a new key on your API for each subscriber. Zyla handles the customer key and the subscription billing. You keep building and maintaining the API.

If your API uses a different authentication method, write to hello@zylalabs.com before you publish and we will confirm the setup with you.