---
title: "Authentication Overview | Tajo"
description: "Brevo connector: authentication methods of the Brevo API (API keys, OAuth 2.0, JWT tokens)"
url: https://tajo.io/docs/authentication/
markdown: https://tajo.io/docs/authentication.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
---

# Authentication Overview

[Set Noa](https://tajo.io/set-noa/)

Brevo API supports multiple authentication methods to secure your API requests.

## Authentication Methods

### API Keys

The most common method for server-to-server communication.

- [Get your API key](https://tajo.io/docs/authentication/api-keys)
- Simple and straightforward
- Perfect for backend integrations

### OAuth 2.0

For applications that need user authorization.

- [OAuth 2.0 setup guide](https://tajo.io/docs/authentication/oauth)
- Secure user consent flow
- Ideal for third-party applications

### JWT Tokens

For advanced authentication scenarios.

- [JWT implementation guide](https://tajo.io/docs/authentication/jwt-tokens)
- Stateless authentication
- Enhanced security features

## Security Best Practices

1. **Never expose API keys in client-side code**
2. **Use environment variables for sensitive data**
3. **Rotate keys regularly**
4. **Implement proper error handling**
5. **Use HTTPS for all requests**

## Rate Limiting

All authentication methods are subject to rate limiting:

- **Free accounts**: 300 requests/hour
- **Paid accounts**: 3000 requests/hour
- **Enterprise**: Custom limits available