FlowData

Which data APIs does FlowData offer?

Published on 10. November 2026

FlowData is made up of several data APIs that you call with the same FlowData key under https://api.flowdata.one/v1. This article briefly explains what each area is for and shows one minimal sample request per area. All parameters and sample responses are in the API documentation.

In all examples, replace fd_YOUR_KEY with your own key. Creating a FlowData API key shows you how to get one.

IP Geolocation

Returns the country, region, city, coordinates, time zone and provider for an IP address or domain. Typical uses are placing visitors in a rough region or spotting suspicious orders.

curl "https://api.flowdata.one/v1/geolocation/8.8.8.8?lang=de" \
  -H "Authorization: Bearer fd_YOUR_KEY"

Without an address in the path (/v1/geolocation), you get the data for the IP address the request comes from. To look up several addresses at once, use POST /v1/geolocation/batch. The body is a JSON array with at most 100 entries:

curl -X POST "https://api.flowdata.one/v1/geolocation/batch" \
  -H "Authorization: Bearer fd_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '["8.8.8.8", "1.1.1.1"]'

Client Info

Returns the IP address, proxy indicators, browser and language of the calling client. This area is free and works well for a first test.

curl "https://api.flowdata.one/v1/client-info" \
  -H "Authorization: Bearer fd_YOUR_KEY"

Maps

Place search, geocoding and directions. There are three endpoints:

  • GET /v1/maps/search with q (search term), optionally limit (1 to 10) and country (for example DE)
  • GET /v1/maps/geocode with address to go from an address to coordinates, or with lat and lng for the reverse
  • GET /v1/maps/directions with origin and destination, each as "longitude,latitude", and optionally profile (driving, driving-traffic, walking, cycling)
curl "https://api.flowdata.one/v1/maps/geocode?address=Alexanderplatz%201,%20Berlin" \
  -H "Authorization: Bearer fd_YOUR_KEY"

Email Verifier

Checks whether an email address is deliverable, for example before you add it to your newsletter list. The response contains the checked address (email_address) and the result (status and result). The key always goes in the header, never in the URL:

curl "https://api.flowdata.one/v1/email-verification/name%40example.com" \
  -H "Authorization: Bearer fd_YOUR_KEY"

The API answers an address with an invalid format with HTTP 400.

YouTube

Returns metrics for a YouTube channel. As the identifier, pass the handle (for example @YouTube) or the channel ID.

curl "https://api.flowdata.one/v1/youtube/stats/@YouTube" \
  -H "Authorization: Bearer fd_YOUR_KEY"

Media processing

Resizes and compresses video, images and audio, applies watermarks and creates thumbnails. Unlike the other areas, media processing works with jobs that run in the background. To get started, see Starting a media job.

Good to know

  • You pay for what you use: per 1,000 successful requests in the data areas, and per started output minute or per image in media processing. Client Info is free. Failed requests, a Maps search with no results and the email result unknown cost nothing. The amounts are on the pricing page.
  • Every request appears in the log of its area, so you can see right away whether your integration is asking correctly, see Statistics and request log.
  • Always call the APIs from your server so your key doesn't end up in the browser.

Was this article helpful?

Back to Getting started & API keys