When a new subscription is created, Nadles makes an exclusive copy of the respective API product for it, so that changes in the main product do not affect the subscription.
Before the introduction of test access keys, in order to test changes in the main product, API providers needed to create a new subscription and use a new access key each time a product changes. That was quite annoying, especially when creating a new product from scratch.
The new feature simplifies the process of configuring API products on Nadles a lot.
Now you don’t need to create a subscription in order to test whether the product is configured correctly: just use test access keys.
Using test access keys, you can make calls to your API via Nadles API Gateway as if the access key was from a real subscription.
The gateway will proxy the request, perform all configured actions, calculate billable metrics usage and return a real response.
All changes to the product configuration are almost immediately picked up by the API gateway.
The differences with real-life operation are:
- Requests made with test access keys do not appear in the analytics.
- Billable metrics usage is calculated for each request, but not recorded. So the total usage and remaining quota values stay the same.
- Calls with test access keys are rate-limited at 1 req/s.
Nadles offers the fastest way to onboard your customers of your API. Try it now on www.nadles.com.
