REST API quickstart#

Production access unverified

No dedicated test key was available for an authenticated production read. Use this example only after the release preflight confirms the API contract.

The API uses JSON over HTTPS. Its production origin is:

https://www.lindavia.com/api/v1

1. Create a key#

Create and copy a key in the developer console. Put it in a server environment variable:

export LINDAVIA_API_KEY='lnd_live_replace_me'

2. Search the directory#

country is required. This example asks for published Madrid records whose primary phone appears technically capable of receiving WhatsApp messages:

curl --get 'https://www.lindavia.com/api/v1/businesses' \
  --header "X-API-Key: $LINDAVIA_API_KEY" \
  --data-urlencode 'country=es' \
  --data-urlencode 'city=madrid' \
  --data-urlencode 'whatsapp=true' \
  --data-urlencode 'limit=25'

3. Read the response#

{
  "businesses": [
    {
      "id": "ChIJ…",
      "name": "Salón Example",
      "phone": "+34600111222",
      "phoneType": "mobile",
      "whatsappEligible": true,
      "verified": false,
      "profileUrl": "https://www.lindavia.com/es/es/madrid/salon-example/"
    }
  ],
  "page": {
    "count": 1,
    "hasMore": false,
    "nextCursor": null
  }
}

Continue with the complete Businesses endpoint and pagination contracts.

Public records

The API returns only records whose publication status is published, through an explicit field allowlist. Internal crawl and publication metadata is never part of the response.