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

# Authentication

> Learn how to authenticate with the Fyndera API

<Warning>These API docs are under construction and prone to change.</Warning>

# Authentication

The Fyndera API uses API key authentication to secure access to our endpoints. All requests must include a valid API key in the request headers.

## API Key

Your API key is a unique identifier that authenticates your requests to the Fyndera API. You can find your API key in your account dashboard.

### Getting Your API Key

1. Create your Fyndera account
2. Contact [api-support@fyndera.be](mailto:api-support@fyndera.be) to request an API key

<Warning>
  Keep your API key secure and never expose it in client-side code or public
  repositories. API keys are only available for paid plans
</Warning>

## Making Authenticated Requests

Include your API key in the `Authorization` header of all requests:

```bash theme={null}
curl -H "Authorization: Bearer YOUR_API_KEY" \
     https://api.fyndera.be/v1/legislation
```

### Header Format

```
Authorization: Bearer YOUR_API_KEY
```

## API Key Management

### Regenerating Keys

If your API key is compromised or you need to rotate it, contact [api-support@fyndera.be](mailto:api-support@fyndera.be) to deactivate it.

## Troubleshooting

### Invalid API Key

If you receive a `401 Unauthorized` error:

* Verify your API key is correct
* Check that you're using the `Bearer` prefix
* Ensure there are no extra spaces in the header

### Expired API Key

If your API key has expired, contact [api-support@fyndera.be](mailto:api-support@fyndera.be) to obtain a new one.

## Security Best Practices

* **Never commit API keys to version control**
* **Use environment variables** to store API keys
* **Rotate keys regularly** for enhanced security
* **Monitor API usage** for unusual activity
* **Use HTTPS** for all API requests