# Introduction (/developers/api/introduction)



Use the Pandabase HTTP API to manage your store from any language that can send HTTP requests. See [API tokens](/developers/learn/api-tokens) for authentication.

## API Basics [#api-basics]

| Environment | URL                        | Protocols           |
| ----------- | -------------------------- | ------------------- |
| Production  | `https://api.pandabase.io` | HTTP/1.1-2 over TLS |

## Additional Information [#additional-information]

* All endpoints are accessible under the specified URLs.
* The API follows the REST architecture principles.
* Both production and sandbox environments support HTTP/1.1 and HTTP/2 protocols.
* All communications are secured using TLS (Transport Layer Security).

### Domains and IP addresses [#domains-and-ip-addresses]

<Callout type="warn">
  Only `HTTPS` requests are allowed, any requests made with `HTTP` will be
  redirected.
</Callout>

### Content Type [#content-type]

All requests must be encoded as JSON with the Content-Type: `application/json`
header. If not otherwise specified, responses from the Pandabase API, including
errors, are encoded exclusively as JSON as well.

### Versioning [#versioning]

The API uses major versions for breaking changes and dated updates for backward-compatible changes.

**How It Works**

1. **Major Versions**: Released when there are breaking changes that require code updates
   * Breaking changes include endpoint restructuring, renamed fields, or removed functionality
   * Each major version is maintained separately to give you time to migrate
   * Current version: **V2** (released March 7, 2026)

2. **Date-Based Increments** (YYYY/MM/DD): Added to major versions for non-breaking updates
   * Non-breaking changes include new features, additional fields, bug fixes, and performance improvements
   * Format: `YYYY/MM/DD-v2` (e.g., `2026/03/09-v2`)
   * These updates are backward compatible within the same major version

**Version Header**

The `X-Version` response header identifies the API version used for the request.

### Request IDs [#request-ids]

Every API response includes the following headers:

| Header         | Description                                                |
| -------------- | ---------------------------------------------------------- |
| `X-Request-ID` | Unique request identifier for tracking and troubleshooting |
| `X-Version`    | Current API version in `YYYY/MM/DD-v2` format              |

Include the `X-Request-ID` when contacting support so we can find the request.