Local & Maps

Search Local Finder · Local Finder API

POST/local/search
$min $0.01

Run one live Local Finder search — the expanded local-pack listing — and receive ranked local places for a query, including title, address, rating, phone, and booking links.

Request
curl https://api.unifapi.com/local/search \
  -H "Authorization: Bearer $UNIFAPI_KEY"
Overview

This operation is part of the Local Finder API in the local & maps category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs Local Finder public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.

Common agent workflows

  • Search Local Finder for public mentions, creators, posts, or topics matching a user query.
  • Feed ranked Local Finder results into research, monitoring, and enrichment workflows.
  • Give an AI agent a stable Local Finder data source without building a per-platform integration.
  • Normalize Local Finder responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 10 credits ($0.01) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Billing

This operation charges 1 credit per billable record, with a 10 credits ($0.01) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Platform-caused failures can be refunded.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Related endpoints

More Local Finder operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.