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

# 3A Brands API Reference

> Complete API reference for the 3A Brands application

<Callout type="info" emoji="ℹ️">
  This documentation provides comprehensive details about all available endpoints, request parameters, and response formats for the 3A Brands API.
</Callout>

## 🔐 Authentication

Most endpoints require authentication. After logging in, you'll receive a token that must be included in the header of subsequent requests.

## 🌐 Base URL

<div className="p-4 border rounded-md bg-gray-50 dark:bg-gray-800">
  All API endpoints are relative to the base URL:
  <code className="px-2 py-1 font-mono bg-gray-100 dark:bg-gray-700 rounded">[https://demo.nivara.io](https://demo.nivara.io)</code>
</div>

## 📦 Response Formats

Responses are returned in various formats depending on the endpoint:

<Tabs>
  <Tab title="JSON">
    Used for most data operations and CRUD functionality.
  </Tab>

  <Tab title="HTML">
    Used for page rendering and template responses.
  </Tab>

  <Tab title="File Downloads">
    Binary data streams for file downloads, reports, and exports.
  </Tab>
</Tabs>

## ⚠️ Error Handling

The API uses standard HTTP status codes to indicate the success or failure of requests.

| Status Code | Description  |
| ----------- | ------------ |
| 200         | Success      |
| 201         | Created      |
| 400         | Bad Request  |
| 401         | Unauthorized |
| 403         | Forbidden    |
| 404         | Not Found    |
| 500         | Server Error |

<Callout type="warning" emoji="🚨">
  When an error occurs, the response will include details about what went wrong in a standardized format.
</Callout>

```json theme={null}
{
  "status": 400,
  "code": "INVALID_PARAMETERS",
  "message": "The request contains invalid parameters",
  "details": {
    "field": "email",
    "issue": "Must be a valid email address"
  }
}
```