Datafy Data API

The Datafy Data API is a beta JSON-over-HTTP reporting API that returns aggregated visitation analytics for a destination. It is RPC-shaped rather than resource-shaped: three fixed endpoints, with the request body — not the path — selecting what comes back. POST / generates or retrieves a dataset from a single envelope of levels, filters and limits; POST /options enumerates the levels, level values and authorized destinations a token is entitled to; GET /progress reports how many data requests are still in flight per destination. A request that has not been processed before is queued and answered with a status message, and the caller re-sends the identical body to collect the result. Responses most often carry four standard KPIs — Total Trips, Visitor Days, Unique Visitors and Avg Trip Length — with privacy filtering and level-dependent weighted averaging applied inside the response. Access is by a user-specific 30-day bearer JWT generated in the Datafy portal, and Datafy states the API is "provided as a convenience and an alternative to receiving a scheduled report directly from the Datafy Team".

API entry from apis.yml

apis.yml Raw ↑
name: Datafy Data API
description: 'The Datafy Data API is a beta JSON-over-HTTP reporting API that returns aggregated visitation
  analytics for a destination. It is RPC-shaped rather than resource-shaped: three fixed endpoints, with
  the request body — not the path — selecting what comes back. POST / generates or retrieves a dataset
  from a single envelope of levels, filters and limits; POST /options enumerates the levels, level values
  and authorized destinations a token is entitled to; GET /progress reports how many data requests are
  still in flight per destination. A request that has not been processed before is queued and answered
  with a status message, and the caller re-sends the identical body to collect the result. Responses most
  often carry four standard KPIs — Total Trips, Visitor Days, Unique Visitors and Avg Trip Length — with
  privacy filtering and level-dependent weighted averaging applied inside the response. Access is by a
  user-specific 30-day bearer JWT generated in the Datafy portal, and Datafy states the API is "provided
  as a convenience and an alternative to receiving a scheduled report directly from the Datafy Team".'
humanURL: https://www.datafy.com/docs
baseURL: https://api.datafy.com/
image: https://www.datafy.com/favicon.ico
tags:
- Analytics
- Location Intelligence
- Visitation Data
- Reporting
- Tourism
properties:
- type: Documentation
  url: https://www.datafy.com/docs
- type: APIReference
  url: https://www.datafy.com/docs
x-evidence:
  verified: '2026-08-12'
  method: docs read + live endpoint probe
  docs_describe: https://www.datafy.com/docs names the base URL https://api.datafy.com/, three endpoints
    (/, /options, /progress), the Authorization header scheme, the full JSON request envelope (destination,
    levels, filters, limits) with worked cURL / JavaScript / Python examples, and the response semantics.
  endpoint_check: 'All three documented endpoints answer live. GET https://api.datafy.com/ and GET https://api.datafy.com/progress
    and POST https://api.datafy.com/options each returned HTTP 500 "Error: No authorization token was
    found" anonymously; a malformed bearer returned "jwt malformed" and an unaccepted bearer returned
    "invalid token" — real, distinguishable application responses from a live API server, not a parked
    host or marketing page.'
  spec_published: false
  note: 'The prior round of this profile recorded "does not currently publish a public developer API,
    SDKs, or API documentation." That was wrong on two of the three counts and is corrected here: the
    public API documentation and the live API host both exist. No SDK exists.'