ZetaSafe's API Management system is changing

For many years, ZetaSafe has used Tyk as our API management platform, which third-party developers have been able to use to integrate with ZetaSafe data. 

The platform we will be using is changing, but functionality will be the same. 

What do I need to do and by when?

We will be moving the service on 15th October 2025. You will need to migrate to the new service by then.

If you are a developer currently using this service, we will send you an invite from our new API Management system. The invite link will start with portal-api-prod.zetasafe.net. Invites for our DEV APIs will be from portal-api-dev.zetasafe.net.

Below is an example invite email.

Clicking the link will send you to our new developer portal, where you can set your password.

Once your password has been set, you can log in to https://portal-api-prod.zetasafe.net/signin

From here, you can view our list of products, which are the same as the Tyk policies used previously.

You can then subscribe to one or multiple of our API subscriptions.

We will then need to approve this product subscription, and your subscription will be in a Submitted state.

You will receive the following email when approved.

From your profile page, you will be able to view and generate API keys.

This will replace your existing key used in the Authorisation header when making API calls to api.zetasafe.net

All URLs and API slugs will not change for production.

You will need to switch over to these new API keys on or before 15th October 2025

 This process will be similar to accessing our DEV APIs. However, the API calls must be sent to api-dev.zetasafe.net. All API slugs will remain the same.

Your existing policy subscriptions on Tyk can be viewed on your API dashboard.
https://portal-api.zetasafe.net/member/

How can I migrate before the deadline?

To migrate your production APIs to our new APIM system ahead of time requires two changes. 

1. Generate new API keys using the method described above
2. Change the base URL from api.zetasafe.net to api-prod.zetasafe.net

After the switch over date, both URLs (api.zetasafe.net and api-prod.zetasafe.net) will point to our new system. 

What happens if I don't switch over in time?

Any requests made to api.zetasafe.net with your old API key from TYK made after the switch over date will result in an 401 status code and the following message.