# Start your integration with a clear scope.

> Access Legichain API documentation, SDK resources and integration information. Review request, response and error scenarios.

Canonical URL: https://legichain.com/en/developers
Language: en
Other language: https://legichain.com/developers

Review the API structure, required data fields and responses. Define the control flow that fits your product.

- [Open the API documentation](https://panel.legichain.com/api-docs)
- [Python SDK](https://github.com/legichain/legichain-python)

**Request** — POST · name screening

```
// Sent server-side with the secret API key
{
  "subject": {
    "type": "person",
    "name": "Ali Örnek",
    "birth_year": 1978,
    "country": "TR"
  },
  "reference": "customer-2481"
}
```

**Response** — 200 · sample response

```
{
  "screening_id": "scr_example_7730",
  "status": "review_required",
  "matches": [
    {
      "candidate": "ALI ORNEK",
      "source": {
        "name": "Sanctions list (sample source)",
        "record_id": "SL-0419",
        "data_as_of": "2026-08-28"
      },
      "matched_fields": ["name", "birth_year"],
      "match_confidence": 0.72,
      "risk_indicator": "high",
      "recommendation": "review"
    }
  ],
  "decision": null
}
```

**Error state** — 422 · validation error

```
{
  "error": {
    "type": "validation_error",
    "message": "subject.name is required",
    "retryable": false
  }
}
// Retry only errors with retryable=true,
// with the same reference and increasing back-off.
```

## First integration steps.

In four steps, define the scope, set up access securely and implement not only the successful response but also the review and error states.

- **Choose the product.** — Define the check you need and its scope.
- **Configure authentication.** — Use the API credentials in a secure server environment.
- **Run the sample request.** — Follow the usage terms of the test environment.
- **Implement error and review states.** — Do not design only the successful response.

## Resources.

- **API reference** — Request fields, response schema and error codes.
  - https://panel.legichain.com/api-docs
- **Python SDK** — Public package and usage examples.
  - https://github.com/legichain/legichain-python
- **System status** — Current service information.
  - https://legichain.com/en/status

## Check before going to production.

Assess authorisation, rate limits, retry behaviour, logging and sensitive-data handling together with your application's requirements. Features such as webhooks or idempotency should be used only within the scope documented for the relevant endpoint.

- **Authorisation** — Secret key server-side only; never in client code.
- **Rate limits** — Implement limit responses and back-off behaviour.
- **Retry** — Only for retryable errors; with the same reference.
- **Logging** — Identity and wallet data are masked in logs.
- **Sensitive data handling** — Retention and access consistent with the contract scope.
- **Review state** — A team flow is defined for the "review_required" response.

## About integration.

### Can I put the API key in a client application?

Do not place secret credentials in publicly accessible client code. Follow the authorisation model of the relevant integration.

### Are the sample responses live data?

Documentation examples are labelled as samples. Live product responses and test data are kept separate.

## Do you have a technical question?

Share your integration scenario. Let's clarify the required product and data scope together.

- [Request a technical call](https://legichain.com/en/contact?topic=integration)

---
Legichain — technology for identity verification, AML and blockchain screening. Contact: contact@legichain.com