The FlowData APIs have their own address: https://api.flowdata.one/v1. The old paths under https://creativeskyline.de/api/... keep working with no end date, so there's no rush. The documentation and help only show the new address, though. To switch, you change the address; parameters and responses stay the same.
Old and new paths
Old (https://creativeskyline.de) |
New (https://api.flowdata.one) |
|---|---|
GET /api/geolocation |
GET /v1/geolocation |
GET /api/geolocation/{query} |
GET /v1/geolocation/{query} |
POST /api/geolocation/batch |
POST /v1/geolocation/batch |
GET /api/client-info |
GET /v1/client-info |
GET /api/maps/search |
GET /v1/maps/search |
GET /api/maps/geocode |
GET /v1/maps/geocode |
GET /api/maps/directions |
GET /v1/maps/directions |
GET /api/youtube/stats/{identifier} |
GET /v1/youtube/stats/{identifier} |
GET /api/emailverification/{email} |
GET /v1/email-verification/{email} |
/api/media/v1/... |
/v1/media/... |
Watch out for the two differences: for Email Verifier the path is now email-verification with a hyphen, and for media processing v1 comes first, for example POST /v1/media/jobs instead of POST /api/media/v1/jobs.
How to switch
- Replace the base address in your integration according to the table.
- Check that your key is in the
Authorization: Bearer ...header. A key in the URL is not evaluated. - Test the new address with a free request:
curl "https://api.flowdata.one/v1/client-info" \
-H "Authorization: Bearer fd_YOUR_KEY"
- Check in the area's log that the requests arrive as expected. Statistics and request log shows you how.
Your existing keys are valid on both addresses. The dashboard has a new address too: flowdata.one/dashboard. Old links to creativeskyline.de/flowdata/... forward there automatically.
Key in the URL for Email Verifier
The Email Verifier documentation used to show an address with the key in the path: /api/emailverification/{email}/{key}. This form is obsolete. The key belongs only in the Authorization header. The new address no longer has a form with the key in the path, or any further path segment after the email.
The old form is still accepted so that existing integrations don't suddenly break. However, the part with the key is not evaluated, it's masked in the log, and the response carries the Deprecation header. Your request is only authenticated through the header. If you send the old address without the header, you get HTTP 401.
URLs end up in many places you don't control: server and proxy logs, browser history, monitoring tools and error reports. Anyone who finds the key there can call FlowData in your name and use up your balance. If it was ever in a URL, you should therefore replace it:
- Change the address in your integration and set the header:
curl "https://api.flowdata.one/v1/email-verification/name%40example.com" \
-H "Authorization: Bearer fd_YOUR_KEY"
- Check in the log of the Email Verifier area that the request arrives with status 200.
- Open API keys, click Regenerate next to the affected key and confirm the Regenerate key? dialog.
- Copy the new value. It is shown only this once.
- Enter the new value in your integration.
After you regenerate a key, the old value keeps working for a transition period, and the dialog tells you how long. That gives you time to switch without your integration failing. The key keeps its name, limit and statistics; only the value changes. Regenerate is only available to the person who created the key. If someone else created it, revoke it and create a new one.
Good to know
- Creating a FlowData API key has more on keys, validity and limits.
- The Email Verifier response is the same in all forms. Checking an email address explains what it means.
- If your integration still uses a FlowSuite key, you can replace it at the same time, see Replacing FlowSuite keys.
- The new address always answers with JSON. You don't need to set an
Acceptheader.