> ## Documentation Index
> Fetch the complete documentation index at: https://slovakapi.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Use the RPO API to find any legal entity and retrieve its full detail.

***

## What is RPO?

The **RPO API** is the public REST API for Slovakia’s central register of legal entities, entrepreneurs, and public authorities. Use it to look up an organization by **IČO**, search by name or other filters, and retrieve structured entity data for company lookup, verification, and enrichment.

***

## When to use RPO

Use RPO when you need to:

* look up an entity by **IČO**
* verify that an organization exists
* get entity details such as names, addresses, legal form, status and activities
* build a company lookup or enrichment flow

<Tip>If you need all records from the RPO dataset at once — for example, to seed your own database — use [Local storage](/rpo/getting-started/local-storage) instead of calling the API record by record.</Tip>

***

## API endpoints

RPO has two types of endpoints:

| Type                                                      | What it does                                                              |
| --------------------------------------------------------- | ------------------------------------------------------------------------- |
| **[Search](/rpo/api-reference/search-entities)**          | Returns entities matching your filters (IČO, name, address, dates, etc.). |
| **[Entity detail](/rpo/api-reference/get-entity-detail)** | Returns the full record for one entity by `id`.                           |

## How to start

For most integrations, the fastest path is to look up an entity by IČO, and then fetch the full entity detail by its ID.

```mermaid placement="top-right" theme={null}
flowchart LR
  A[Search entity] --> B[Read entity ID] --> C[Fetch full detail]
```

<Steps>
  <Step title="Search for an entity by IČO">
    Send a request to the Search endpoint with the `identifier` parameter.

    ```bash Search request example theme={null}
    curl "https://api.statistics.sk/rpo/v1/search?identifier=31333565"
    ```
  </Step>

  <Step title="Copy the entity ID">
    The search response returns matching entities in `results`. Copy the entity `id` from the first matching record.

    ```json Search response example theme={null}
    {
      "results": [
        {
          "id": 12345678,
          "identifiers": [{ "value": "31333565" }],
          "fullNames": [{ "value": "Example s.r.o." }]
        }
      ]
    }
    ```
  </Step>

  <Step title="Fetch the full entity detail">
    Use the returned `id` with the Detail endpoint.

    ```bash Full detail request example theme={null}
    curl "https://api.statistics.sk/rpo/v1/entity/12345678"
    ```
  </Step>

  <Step title="Review the full entity record">
    The detail response gives you the full entity record, including identifiers, names, legal form, legal status, addresses, activities, stakeholders, and statutory bodies.

    ```json Full detail response example theme={null}
    {
      "id": 12345678,
      "fullNames": [{ "value": "Example s.r.o.", "validFrom": "1991-01-01", "validTo": null }],
      "identifiers": [{ "value": "31333565", "validFrom": "1991-01-01", "validTo": null }],
      "establishment": "1991-01-01",
      "termination": null,
      "addresses": [],
      "activities": [],
      "statutoryBodies": []
    }
    ```
  </Step>
</Steps>

***

## Considerations

* Data updates **once per day**. Overnight changes may not appear immediately.
* Search requires **at least one filter**. Fulltext filters need a minimum of 3 characters.
* Boolean parameters only treat the literal `true` as true.
* `null` fields are often omitted.

***

## Resources

<CardGroup cols={2}>
  <Card title="Search API reference" icon="search" href="/rpo/api-reference/search-entities">
    Detailed specification of the `/search` endpoint.
  </Card>

  <Card title="Detail API reference" icon="list-tree" href="/rpo/api-reference/get-entity-detail">
    Detailed specification of the `/detail` endpoint.
  </Card>

  <Card title="Local storage" icon="database" href="/rpo/getting-started/local-storage">
    Download the full register as compressed JSON.
  </Card>

  <Card title="Data models" icon="layers" href="/rpo/concepts/data-models">
    Types, fields, and the conventions that apply across the entire API.
  </Card>
</CardGroup>