# Foursquare integrations: places and place content

> Foursquare provides location data and APIs, including a global database of points of interest with details, photos and tips for each place.

**Canonical page:** https://tray.ai/connectors/foursquare-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Foursquare provides location data and APIs, including a global database of points of interest with details, photos and tips for each place. Tray.ai connects to Foursquare through the HTTP Connector, so your workflows can call the Foursquare API alongside the rest of your stack.

## Use cases

### Places

Read places in Foursquare from any Tray.ai workflow. The Foursquare API covers calls such as search for places and get place details.

- Search for places
- Get place details
- Match a place

### Place content

Read place content in Foursquare from any Tray.ai workflow. The Foursquare API covers calls such as get place photos and get place tips.

- Get place photos
- Get place tips

### Place edits

Read and update place edits in Foursquare from any Tray.ai workflow. The Foursquare API covers calls such as suggest a new place and edit a place.

- Suggest a new place
- Edit a place
- Flag a place

## Challenges Tray.ai solves

### Keeping Foursquare credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Foursquare credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Foursquare API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Foursquare API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Foursquare?

Yes. Tray.ai connects to Foursquare through the HTTP Connector, which calls the Foursquare API directly. Any call the Foursquare API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Foursquare?

The Foursquare API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Foursquare connector?

Foursquare runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Foursquare connector from the Foursquare API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/