Introduction

Here you will find all the documentation related to each product we are or have worked on.

note

The documents in this site are not meant to outline how to use the API endpoints, rather how to build and maintain it. We outline what it's capabilities should be, once you have built them, you can create documentation for our clients on how to utilize them on the BackBone site.

Products

Products

📄️BackBone

This handles all client accounts, projects and the APIs they use as well as all thier projects users.

📄️CMS

A content managment system.

📄️Commerce

Core API details.

📄️Finance

Core API details.

API

intro

Headers

"Content-Type":"application/json"

note

use this for all endpoints

Parameters

{
  "token": "your_token_here"
}

tip

if you don't have one use calm commerce dashboard to create one

---

sidebar_position: 1

Intro

Welcome to the BackBone CMS API documentation. This guide outlines the base requirements and common patterns used throughout the API.

---

Headers

All requests must include the following header:

{
  "Content-Type": "application/json"
}

---

Parameters

Authentication is done via a token provided in the request payload or headers, depending on the endpoint.

{
  "token": "your_token_here"
}

---

API Structure

While this document doesn’t go into full details for every endpoint, here’s what you should know about the conventions used:

General Structure

• All endpoints are RESTful.

• Routes are grouped by resource (/assets, /projects, /users, etc.).

• Standard HTTP verbs are used:

  • GET for fetching data
  • POST for creating new entries
  • PUT/PATCH for updates
  • DELETE for deletions

Asset Base Routes

| Method | Route | Description | Doc | | -------- | ---------------------- | --------------------------- | Doc | | GET | /assets | Get all assets | Doc | | GET | /assets/:id | Get asset by ID | Doc | | POST | /assets | Create a new asset | Doc | | PUT | /assets/:id | Update an existing asset | Doc | | DELETE | /assets/:id | Delete an asset | Doc | | GET | /projects/:id/assets | Get all assets in a project | Doc |

Most update/create endpoints expect full or partial JSON objects matching the schema from the Data Model docs.

---

Testing the API

You can test the API using Postman or any other HTTP client. Be sure to:

1. Set Content-Type: application/json in headers.
2. Include your token in the request body or headers.
3. Use the proper route and payload format.

---

Notes

• API is subject to rate limits — if your requests are throttled, try again after a short delay.
• For real-time updates or webhooks, check the Integrations section (coming soon).
• All DateTime fields are in ISO 8601 format (e.g., "2025-07-04T12:00:00Z").

---

For specific endpoints, go to the Assets or Projects documentation pages.