GET/v1/{metro}/nearbyall plans

List nearby listings

Takes a point (lat/lng) and returns a flat, distance-ordered list — no address resolution and no grouping, unlike /around, which takes an address and returns grouped, ranked results. Use this when the caller already has coordinates; use /around when the caller has an address.

Returns published, active rows with coordinates within radius_m of lat/lng, nearest first, with the distance in metres on every row. Only rows with something still ahead of them: places always, events that have not started, and classes and camps whose term has not ended.

Paged by cursor only (there is no page); meta.next_cursor is "<distance_m>:<listing_id>", the key of the last row returned, so the page cannot drift as rows are written.

Results are confined to {metro}; a point outside it returns an empty page rather than the neighboring metro's rows. lat/lng choose where in the metro to look, never which metro to look in.

Use types to narrow; each type requested must be in the key's scopes.types. Returns 503 when this endpoint is unavailable.

Try this requestRun it with sample data, no key needed. Paste a key to run it live.

Example request

curl -sS \
  -H "X-API-Key: $TAILEND_API_KEY" \
  "https://api.tailend.dev/v1/philadelphia/nearby"

Example response · 200

{
  "data": [
    {
      "listing_id": "00000000-0000-4000-8000-000000000001",
      "type": "event",
      "name": "example",
      "distance_m": 1
    }
  ],
  "meta": {
    "limit": 1,
    "count": 1,
    "has_more": false
  }
}

API key Remember for this tab

Try any request with sample data, no key needed. Available on every plan.

metrostringrequiredpath

Metro slug from /v1/metros (e.g. philadelphia).

latnumberrequiredquery

Latitude of the point to search around.

lngnumberrequiredquery

Longitude of the point to search around.

Optional parameters (4)

radius_mintegeroptionalquery

Radius in metres.

typesarray of stringoptionalquery

Restrict to these listing types.

cursorstringoptionalquery

meta.next_cursor from the previous page: "<distance_m>:<listing_id>".

limitintegeroptionalquery

Response

A 200 returns application/json with these fields.

dataarray of NearbyItemalways present
- listing_idstring (uuid)always present
- typestringalways present
  The listing's type. ongoing rows are served only on /v1/changes today.
  eventclasscampplaceongoing
- namestringalways present
- slugstring · nullable
- distance_mintegeralways present
  Great-circle metres from the requested point.
- latnumber · nullable
- lngnumber · nullable
- next_atstring (date-time) · nullable
- is_freeboolean
- type_hintstring · nullable
  play_spacemuseumparklibrarytheatersports_facilityfarmrestaurantothernull
- categoriesarray of string
  arts_creativemusic_movementsports_active_playnature_outdoorsstorytime_booksstem_learningcooking_foodsocial_play_spaces
- age_bandsarray of string
  babytoddleryoung_kidsbigger_kids
- source_urlstring · nullable
metaobjectalways present
- metrostring
- pointobject
  - latnumber
  - lngnumber
- radius_minteger
- applied_filtersobject
  The radius and types used, whether sent or defaulted.
  - radius_minteger
  - typesarray of string
- defaults_appliedarray of string
  The names in applied_filters whose value came from a default rather than your request, for example ["from", "to", "min_confidence", "audience"]. Empty when you named every filter that has a default. A default that narrows a result (the 30-day event window, the confidence floor, the adult-audience exclusion) is listed here so a smaller-than-expected set can be explained from the response alone.
- typesarray of string
  eventclasscampplace
- limitintegeralways present
- countintegeralways present
- has_morebooleanalways present
- next_cursorstring · nullable
- generated_atstring (date-time)

Status codes

200
A page of nearby items, nearest first.
400
Malformed or contradictory parameters (lat without lng, to before from, unknown category), or a cursor this API did not issue for this exact request — replayed from another endpoint, resource, metro or filter set, hand-crafted, or altered.
401
Missing, unknown or revoked X-API-Key. Also returned when the key record itself does not validate — the server fails closed and logs why rather than assuming anything about a row it cannot vouch for, and when the value is not shaped like a key (tl_ + 8 hex + _ + 48 hex). The message is invalid API key; the reason is not disclosed. The one exception is a credential shaped like a different kind of token, whose 401 explains it is the wrong credential for /v1 rather than repeating the generic message.
403
Two different reasons share this status. Read error.code.
Show more
forbidden — the key is valid but its scopes exclude this metro or resource type, or the client is inactive. Returned when the caller named the metro or type it was refused — in the path, or in ?metro=. Where the caller supplied only an identifier, an out-of-scope resource is a 404 instead; see NotFound.

include_not_permitted (endpoints that take include= only) — the key is valid and in scope, but is not entitled to a requested include= add-on (details.include names it). Add include_mode=lenient to get a 200 without the block instead of this. See Shaping responses.
404
No published, active resource with that id (or unknown metro).
Show more
Also returned when the resource exists but sits in a metro outside the key's scopes.metros, on the routes that take an identifier rather than a metro: /v1/{type}/{id}, /v1/{type}/slug/{slug} and /v1/organizations/{id}. The metro there is discovered from the row, not named by the caller, so a 403 would confirm that a guessed id or slug is real and say which metro it is in. The two cases are deliberately indistinguishable — same code, same message, same absent details.

Naming the metro is a different question and still gets the explicit 403 with the key's own scopes: /v1/boston/events, or ?metro=boston on a slug lookup.
405
The path exists; the method does not. Every route on this API is a read, so Allow is always GET, HEAD, OPTIONS. A method on a path that does not exist is a 404 instead — 405 is only ever sent where there is a target resource to refuse.
429
A limit was reached. Branch on error.code, not on the status — two different limits share this status:
Show more
- rate_limited — the per-minute rate. Retry-After is seconds, and retrying after it succeeds.
- rate_limited can also mean address lookups are temporarily unavailable. The response explains the condition and provides Retry-After; callers that already have coordinates can send lat/lng instead.
- quota_exceeded — the monthly allowance, or a client's hard cap. Retry-After points at the start of the next UTC month and can therefore be very large; details carries plan, monthly_limit, used and resets_at. Backing off will not help before the reset — the plan has to change. This is a 429; 402 is reserved.
500
A bug on our side. The message is always the constant internal error; details are never included in the body. Retry once with backoff, then contact support with the request_id.
501
This endpoint or feature is not available and will not become available without a configuration change — for ?address=, this means no geocoder is configured.
Show more
Nothing is failing, so do not retry and do not back off: there is no Retry-After, and the answer will not change inside any timeout you set. Treat the feature as switched off, disable it in your UI, and use the alternative the message names where there is one (lat/lng instead of address).

The message is a constant per endpoint family and names no internal object. Include the request_id when contacting support.
503
A transient outage: a dependency could not be reached or did not answer in time. This is the 5xx worth retrying — Retry-After says how long, and the same request is expected to succeed afterwards.

Like every other error here, the message names no internal detail.

Every error uses the same envelope; branch on error.code. See Errors.

Ctrl Enter to send

Request

GEThttps://api.tailend.dev/v1/philadelphia/nearby

curl -sS \
  -H "X-API-Key: $TAILEND_API_KEY" \
  "https://api.tailend.dev/v1/philadelphia/nearby"

const res = await fetch("https://api.tailend.dev/v1/philadelphia/nearby", {
  headers: { 'X-API-Key': '$TAILEND_API_KEY' },
});
const body = await res.json();
console.log(res.status, body);

import os
import requests

response = requests.get(
    "https://api.tailend.dev/v1/philadelphia/nearby",
    headers={'X-API-Key': os.environ['TAILEND_API_KEY']},
)
response.raise_for_status()
print(response.json())

ResponseSample

Showing sample data. Paste a key to run it live. Get a key

A page of nearby items, nearest first.

{
  "data": [
    {
      "listing_id": "00000000-0000-4000-8000-000000000001",
      "type": "event",
      "name": "example",
      "distance_m": 1
    }
  ],
  "meta": {
    "limit": 1,
    "count": 1,
    "has_more": false
  }
}

Malformed or contradictory parameters (lat without lng, to before from, unknown category), or a cursor this API did not issue for this exact request — replayed from another endpoint, resource, metro or filter set, hand-crafted, or altered.

{
  "error": {
    "code": "bad_request",
    "message": "radius_m: must be at least 100",
    "details": {
      "param": "radius_m"
    },
    "request_id": "req_dfbc3295a8382b05"
  }
}

Missing, unknown or revoked X-API-Key.

{
  "error": {
    "code": "unauthorized",
    "message": "missing X-API-Key header",
    "request_id": "req_90e63908273f6bff"
  }
}

Two different reasons share this status.

{
  "error": {
    "code": "forbidden",
    "message": "key is not scoped to metro 'boston'",
    "details": {
      "metros": [
        "philadelphia"
      ]
    },
    "request_id": "req_9e7a750acef48ab2"
  }
}

No published, active resource with that id (or unknown metro).

{
  "error": {
    "code": "not_found",
    "message": "unknown metro 'boston'",
    "request_id": "req_7431b51e10ec2b77"
  }
}

The path exists; the method does not.

{
  "error": {
    "code": "method_not_allowed",
    "message": "POST is not allowed on this path; this API is read-only",
    "details": {
      "allow": [
        "GET",
        "HEAD",
        "OPTIONS"
      ]
    },
    "request_id": "req_01J9Z3"
  }
}

A limit was reached.

{
  "error": {
    "code": "rate_limited",
    "message": "3 requests per minute exceeded",
    "request_id": "req_06bfd3c2d5e8aa9f"
  }
}

A bug on our side.

{
  "error": {
    "code": "internal",
    "message": "internal error",
    "request_id": "req_01J9Z3"
  }
}

This endpoint or feature is not available and will not become available without a configuration change — for ?address=, this means no geocoder is configured.

{
  "error": {
    "code": "not_implemented",
    "message": "this endpoint is not enabled on this deployment; it is not a fault and retrying will not help",
    "request_id": "req_01J9Z3"
  }
}

A transient outage: a dependency could not be reached or did not answer in time.

{
  "error": {
    "code": "unavailable",
    "message": "the service is temporarily unable to serve this request; retry after the interval in Retry-After",
    "request_id": "req_01J9Z3"
  }
}