Foursquare review

Foursquare is a hosted location-intelligence platform, not a single mapping library or self-hosted server. Its product stack includes the Places API for venue data, marketing services for attribution and audience targeting, and geospatial applications such as Spatial Workbench, Spatial Desktop and Spatial Studio. That puts it across several parts of a stack: place lookup in an app, location-based campaign measurement, and spatial analysis for business or GIS teams.

The platform is intended to connect real-world behavior with business outcomes. The homepage describes a database of 100M+ points of interest across 200+ countries, with 9B+ monthly visits from 500M+ devices. Those figures describe Foursquare’s stated data scale, not a service-level guarantee. Developers can use place data for discovery and location analysis; geospatial teams can work with maps and H3-indexed features. Marketing products cover campaign attribution, behavioral audiences and custom geofences. The right product depends on whether the job is app data, analysis or advertising.

The named developer surfaces are Places API, which provides venue data, and Movement SDK, which the homepage describes as a tool for personalizing in-app content. The homepage does not name the API protocol, supported programming languages, client libraries, CLI, webhooks or plugins. Confirm SDK and protocol support in Foursquare’s docs before selecting a language or designing an integration.

Foursquare also offers Spatial Workbench for analysis, compute and visualization, Spatial Desktop for geospatial computing, Spatial Studio for cloud mapping and analytics, and H3 Hub for enriching models with H3-indexed features. The Workbench plan lists a SQL workbench; that does not establish which SQL dialects or external connectors are supported. The homepage says Foursquare data is accessible through 550+ integrated partners, including AWS and The Trade Desk, and via preferred sources and formats. Ask which delivery formats and partner integrations cover your use case. For production, verify authentication, pagination, error behavior, versioning and request limits in the API documentation.

The Places API Pro endpoints have a free 0–500-call band. The listed rates then move through $15 per 1,000 calls at 501–100,000, $12 at 100,001–500,000 and $9 above 500,000. Premium endpoints start at $18.75 per 1,000 calls and include Tips and Photos; their listed bands fall to $15 and then $11.25 as volume rises. Ask API Pro and Premium fields cost $30 and $36 per 1,000 calls, respectively. Ask API rate limits differ from other endpoints.

For spatial tools, Spatial Studio Community is free with 1 GB of cloud storage, limited catalog access, one connector and public map publishing. FSQ Spatial Desktop – Basic is free through 2026 and includes 3 GB storage and five shared projects. FSQ Spatial Desktop – Standard is $25 monthly; Pro is $100. FSQ Spatial Workbench – Developer Plan lists $250 monthly, a 30-day trial with no subscription fee, and usage-billed compute and storage. MotherDuck compute, storage and Spatial Agent tokens can add charges. Check which API band applies to your billing volume and what limits apply before estimating production spend.

Foursquare’s homepage lists open-source access to POI data for location-driven projects. It does not name a license or explain which data, files or tools that access covers. Check the license and permitted uses before redistributing data or incorporating it into a commercial product; the general label is not enough to establish rights.

The products described are hosted services, and the vendor does not describe a self-hosted version of its Places API or geospatial platform on the homepage. Ask whether data can be exported in a portable format, which fields are included, and whether exports remain available after a contract ends. A migration from the Places API would likely require replacing its venue data and adapting lookup logic, but the effort depends on how much your application relies on Foursquare-specific fields. Keep a provider boundary around place records and avoid coupling internal identifiers or schemas to the API until you have reviewed its data and export terms.

The pricing lists establish call-volume bands, but the API’s general rate limits are not published there. Foursquare says Ask API rate limits differ; ask for the exact limits, burst behavior and quota-reset rules for the endpoints you plan to use. Confirm how the service handles timeouts, errors, retries, pagination and version changes before putting it on a latency-sensitive path.

The homepage says its location technology uses stop-detection and describes privacy controls, including consumer control over data and regular audits of partners. Those statements do not define your contractual obligations, available compliance reports, retention terms or security controls. Request the relevant privacy and security documentation, data-processing terms and service-level commitments. For spatial workloads, account for compute and storage billed by usage, and verify what happens when project or storage limits are reached. Foursquare describes data at substantial global scale, but your team should validate geographic coverage and venue freshness for its target markets rather than assume uniform quality.