Introduction

Use the Pandabase HTTP API to manage your store from any language that can send HTTP requests. See API tokens for authentication.

API BasicsCopy Anchor Link

Additional InformationCopy Anchor Link

• 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 addressesCopy Anchor Link

Content TypeCopy Anchor Link

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.

VersioningCopy Anchor Link

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 IDsCopy Anchor Link

Every API response includes the following headers:

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