Skip to main content
Pandabase HTTP API allows developers to interact programmatically with their Pandabase resources using HTTP requests. The API supports any programming language or framework that can send HTTP requests. You can use the commands listed below with curl by providing your token.

​
API Basics

EnvironmentURLProtocols
Productionhttps://api.pandabase.ioHTTP/1.1-2 over TLS
Sandboxhttps://api.sandbox.pandabase.ioHTTP/1.1-2 over TLS

​
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

Only HTTPS requests are allowed, any requests made with HTTP will be redirected.

​
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

The Pandabase API uses a hybrid versioning system that combines major versions with date-based increments to ensure stability while providing continuous improvements. How It Works:
  1. Major Versions (v1, v2): 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: Every API response includes the current version in the X-API-Version header, allowing you to track which version you’re using. Migration Timeline:
  • V1 endpoints will be available until April 1st, 2026
  • See the changelog for detailed version history

​
Request IDs

Every API response includes the following headers:
HeaderDescription
X-Request-IDUnique request identifier for tracking and troubleshooting
X-API-VersionCurrent API version in YYYY/MM/DD-v2 format
X-Version-CommitGit commit SHA of the deployed version
X-Served-ByRegion and machine that served the request
If you encounter an issue with our service, providing the X-Request-ID to our support team will expedite the resolution process.