Property Developers · Search API

Government land records, inside your own software.

One REST API for 100+ automated government searches. Paid per search, and refunded in full when a search fails.

Read the API docsGet an API key
One key per workspaceUp to 50 searches per requestWebhooks or polling
title-checkIllustrative, not final
# Illustrative only. Paths and fields are in the API docs.
curl -X POST "https://legiscore.in/api/v1/<endpoint>" \
  -H "Authorization: Bearer $LEGISCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "<field>": "<value>"
  }'

Base URL and Bearer key match the public docs. Anything in angle brackets is a placeholder: read the API docs before you build.

Integration flow

Your software asks. LegiScore searches.

Four moves from your code to official records. Every call is in the public docs.

  1. 1 · Authenticate

    Get a key

    One API key per workspace. Send it as a Bearer token or in an X-API-Key header.

  2. 2 · Request

    Send searches

    Send up to 50 searches in one request, straight from your own software.

  3. 3 · LegiScore

    Searches run

    Run and wait, or submit and poll with a live status stream. Webhooks tell your system when results land.

  4. 4 · Billing

    Pay per search

    Each search is paid from a credit wallet on your workspace. A failed search is refunded in full.

What you get

Records in your software, on fair terms.

Two APIs: one for government searches, one for full reports from your loan system.

Search API

Government land records in your own software, paid per search.

Report API for loan systems

Start reports from your loan system. Webhooks keep a stored payload, with self-service retry.

Secure document links

Documents are shared through time-limited secure links.

Refund on failure

When a search fails, the credit goes back to your wallet in full.

Repeat searches reused

An identical repeat search within 24 hours reuses the result, free.

One key per workspace

Bearer token or X-API-Key header. Every call is tied to your workspace.

Public docs

Read the docs before you talk to us.

Authentication, the search lifecycle, errors, webhooks and credits are all at legiscore.in/docs. No sales call needed to start.

Open the API docsTalk to our team
LegiScore Search APIlegiscore.in/docs
Getting started

From docs to first search.

  1. Read the docs

    Start with the quickstart and the search lifecycle at legiscore.in/docs.

  2. Get an API key

    One key per workspace. The docs show how to get yours.

  3. Run a search

    Try it on properties you know. A failed search is refunded in full.

  4. Go live

    Talk to us about volume pricing for your workspace.

FAQ

Questions developers ask us.

They are public at legiscore.in/docs: authentication, quickstart, search lifecycle, errors, webhooks and credits.

There is one API key per workspace. Send it as a Bearer token or in an X-API-Key header.

Per search, from a credit wallet on your workspace. For volume pricing, talk to us.

You get a full refund of that search.

No. An identical repeat search within 24 hours reuses the result, free.

Yes, by webhook. You can also run and wait, or submit and poll with a live status stream.

Only the base URL and the Bearer key style. Paths and fields are placeholders. The real ones are in the API docs.

For developers

Put government records in your product.

Read the docs, get a key and run your first search. Talk to us when you need volume pricing.

Read the API docsGet an API key