TIER · Rate Limits

Tier Mobility Rate Limits

Name: Tier Mobility Rate Limits
Creator: TIER
Keywords: Mobility, Micromobility, Shared Mobility, E-Scooter, E-Bike, Transportation, Smart Cities, MaaS, GBFS, Open Data, Europe, Real-Time

Dott (formerly TIER) publishes no documented rate limits for its public GBFS feeds. The MobilityData GBFS spec recommends that consumers respect the per-feed `ttl` field returned in every response, and not poll more frequently than the publisher's update cadence. Observed cadence on the Dott feeds: real-time feeds (free_bike_status, station_status) update every few seconds with `ttl: 0` (no client-side cache), while static feeds (system_information, vehicle_types, pricing_plans, geofencing_zones) refresh on order of minutes.

Tier Mobility Rate Limits is the machine-readable rate-limit profile for TIER on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 2 backoff/retry policies defined.

Tagged areas include Mobility, Micromobility, Shared Mobility, E-Scooter, and E-Bike.

0 Limits

MobilityMicromobilityShared MobilityE-ScooterE-BikeTransportationSmart CitiesMaaSGBFSOpen DataEuropeReal-Time

Policies

No published per-IP or per-key rate limit. Excessive polling may result in CDN-level throttling.

Clients SHOULD respect the `ttl` field returned in the body of each GBFS feed. Treat `ttl: 0` as "always fetch fresh, but no more often than once per second per system."