The data APIs IP Geolocation, Client Info, Maps, Email Verifier and YouTube are part of FlowData and have their own FlowData keys (fd_…). If one of your integrations still calls them with a FlowSuite key (pk_… or at_…), that keeps working with no end date. We still recommend switching. This article shows you how to find affected integrations and switch them over in a few minutes.
What changes and what doesn't
- There is no deadline. Older keys are not being turned off on the five data areas.
- FlowData tells you where older keys are still in use. Each of these responses carries the
DeprecationandLinkheaders. The key's owner also gets a one-time email with the subject "Please switch to a FlowData key". - Your FlowSuite keys stay valid for FlowCRM, Flow Accounting and the other FlowSuite modules. You don't need to delete them.
- Media processing always needs a FlowData key. A FlowSuite key is refused there with HTTP 403.
Finding affected integrations
The FlowData Overview shows the notice FlowSuite keys on FlowData endpoints as soon as at least one FlowSuite key of your team has called a FlowData endpoint in the last 30 days.
Under API keys, below your FlowData keys, a card lists exactly those keys: name, number of requests in the last 30 days and the day of last use. The name tells you which integration you need to change.
In an area's log, requests made with an older key are also marked FlowSuite key.
How to switch
- Open API keys and click New key.
- Give the key a name that matches the integration, for example the name shown on the card.
- Click Create and copy the value shown. It appears only once.
- Replace the old key in your integration with the new one. The header stays the same:
curl "https://api.flowdata.one/v1/maps/search?q=Alexanderplatz%20Berlin&limit=5" \
-H "Authorization: Bearer fd_YOUR_KEY"
- Check in the area's log that the next requests arrive with the new key.
One FlowData key is enough for all areas, so if your integration uses several data APIs you only replace the key in one place. The step-by-step guide with screenshots is in Creating a FlowData API key.
If your integration still calls addresses under creativeskyline.de/api/..., you can move it at the same time, see Switching to api.flowdata.one.
Good to know
- The notice goes away by itself once the old key hasn't called a FlowData endpoint for 30 days.
- A FlowData key belongs to your team and draws on its balance. Billing works the same for old and new keys, see Understanding prices.
- You keep managing your FlowSuite keys in your profile or centrally in FlowConnect, see API and MCP keys.