> ## Documentation Index
> Fetch the complete documentation index at: https://docs-neevlegal.neeved.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> How to authenticate requests to the NeevLegal API.

All endpoints require authentication via an API key passed in the `X-API-Key` header.

## The X-API-Key Header

```http theme={null}
X-API-Key: <your_api_key>
```

## Example

```bash theme={null}
curl -X POST https://api-neevlegal.neeved.com/api/v1/case-detail/searchByCnr \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "cnrNumber": "MHPN010123456789" }'
```

## Key Management

API keys can be generated and managed through the Developer Portal at [neevlegal.neeved.com/api-keys](https://neevlegal.neeved.com/api-keys). You can create keys with specific permission scopes, rotate a key to get a new value without changing its configuration, and revoke keys that are no longer needed. Rotating a key immediately invalidates the existing value.

## Security Practices

> [!NOTE]
>
> Keep API keys out of source code and version control. Use a dedicated secrets manager to inject keys at runtime. Assign each integration its own key with the minimum scopes needed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.