> For the complete documentation index, see [llms.txt](https://docs.legal-data-analytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legal-data-analytics.com/legal-data-analytics-v1/api-basics/rest-api-requests-usage-and-throttling.md).

# REST API, Requests, Usage and Throttling

## REST API

The Legal Data Hub can be accessed on the high-level API via REST API.

## Request

We follow the widely accepted description: "\[...] an API call is a request by a software application to access data or any other service from another application or any other server." (see [Source](https://www.geeksforgeeks.org/websites-apps/what-is-an-api-call/)).

Based on this, the Legal Data Hub considers every API call as a request. E.g., an execution of a semantic search query via the [Semantic Search](/legal-data-analytics-v1/api-specification/semantic-search.md) endpoint is one API call is counted as one request.

## API Usage

The API usage is secured by the authorisation and the [access token](/legal-data-analytics-v1/api-basics/login-authorisation.md). The access token contains the information which data assets can be accessed. 

## Throttling

The REST API is throttled to avoid misuse and increase security. If too many requests are sent from one client the API returns a [http 429 response](https://developer.mozilla.org/de/docs/Web/HTTP/Reference/Status/429). The throttling counter will be reseted after a time period.