Developer Integration Manual

A simple, clear guide to connecting your application to the Spacebase Cloud database platform.

How it Works

Spacebase gives you isolated database containers. Instead of sharing a single giant database with other users, your account gets its own independent sandbox environment. Everything runs through a central web router API.

🔒 Strict Privacy: Your database names are completely hidden on the server. When you create a database, the system assigns it a random, scrambled code identifier (like a UUID). The system always verifies that you own a database before letting you read or modify any data.

Authentication

To keep your data safe, every request you send (except for signing up or logging in) must include your secret token. You pass this key inside the standard Authorization header like this:

Authorization: Bearer sk_v2_f8b1c4e2a...

Automatic Name Cleanup

To prevent broken file links or weird path errors, Spacebase cleans up database names behind the scenes. If you include any blank spaces or special punctuation characters, the engine automatically turns them into nice, neat underscores (_).

What You Type How the Server Saves It
"my tracking data" "my_tracking_data"
"Client Logs v3!" "Client_Logs_v3"

API Endpoint Specifications

Send all your API calls to this single base URL address:
http://spacebase.iquipe.cloud/v3

POST PUBLIC ?action=register

Registers a new developer account and hands back your first active secret access token.

What to Send in the Request Body: 
{
  "action": "register",
  "email": "developer@iquipe.cloud",
  "password": "MySuperSecretPassword123!"
}
What the Server Returns (Success Response): 
{
  "success": true,
  "data": {
    "user_id": 109,
    "email": "developer@iquipe.cloud",
    "token": "sk_v2_f8b1c4e2a739d482c19a3b65ef0192bc",
    "message": "Account successfully created and provisioned."
  }
}
POST PUBLIC ?action=get_token

Logs you in using your email and password. Use this if you lose your token or need to clear your local cache variables.

What to Send in the Request Body: 
{
  "action": "get_token",
  "email": "developer@iquipe.cloud",
  "password": "MySuperSecretPassword123!"
}
What the Server Returns (Success Response): 
{
  "success": true,
  "data": {
    "email": "developer@iquipe.cloud",
    "token": "sk_v2_f8b1c4e2a739d482c19a3b65ef0192bc",
    "message": "Authentication successful. Token retrieved."
  }
}
POST Bearer Required ?action=list_databases

Returns a summary list of all your active databases. It includes overall platform analytics like disk file sizes (in MB/GB) and exact read/write transaction histories.

What to Send in the Request Body: 
{
  "action": "list_databases"
}
What the Server Returns (Success Response): 
{
  "success": true,
  "total_databases": 1,
  "account_summary": {
    "total_reads_across_all_databases": 142,
    "total_writes_across_all_databases": 56
  },
  "databases": [
    {
      "friendly_name": "deep_space_telemetry",
      "uuid_filename": "b9ea32f1-c42a-4ce7-8822-1ba4e320d912",
      "created_at": "2026-05-19 13:36:00",
      "total_reads": 142,
      "total_writes": 56,
      "size_metrics": {
        "bytes": 24576,
        "mb": "0.0234 MB",
        "gb": "0.000023 GB"
      }
    }
  ]
}
POST Bearer Required ?action=create&db_name=alpha base db

Creates a brand new empty database container file on the hosting platform server. Note how our input parameter cleans up the spaces automatically.

Required URL Query Parameters:
Key Name Example Value
action create
db_name alpha base db (Becomes alpha_base_db)
What the Server Returns (Success Response): 
{
  "success": true,
  "message": "Database 'alpha_base_db' successfully registered and created."
}
POST Bearer Required ?action=connect&db_name=alpha_base_db

Opens a connection pipeline to a specific database container so you can prepare to pass queries.

Required URL Query Parameters:
Key Name Example Value
action connect
db_name alpha_base_db
What the Server Returns (Success Response): 
{
  "success": true,
  "message": "Pipeline connected to 'alpha_base_db' successfully."
}
POST Bearer Required ?action=execute&db_name=alpha_base_db

Runs your standard raw SQL commands directly inside your isolated database container file.

💡 Automatic Feedback Reflection: When you send an INSERT or UPDATE data mutation query, the API doesn't just return an empty status message. It loops back the exact contents of the data row you just added or changed, alongside the auto-incremented last_insert_id number.
What to Send in the Payload Body (INSERT Example): 
{
  "sql": "INSERT INTO devices (name, status) VALUES ('Sensor Alpha', 'Active');"
}
What the Server Returns (Reflected Row Output): 
{
  "success": true,
  "operation": "INSERT",
  "last_insert_id": 12,
  "data": {
    "id": 12,
    "name": "Sensor Alpha",
    "status": "Active"
  },
  "affected_rows": 1
}
POST Bearer Required ?action=drop&db_name=alpha_base_db

Permanently deletes a database container file from the server cluster and purges its record entries from your profile tracking registry maps.

⚠️ Permanent Action Notice: This action instantly cuts active pipeline connections and unlinks physical disk allocation clusters. Dropped data is non-recoverable.
Required URL Query Parameters:
Key Name Example Value
action drop
db_name alpha_base_db
What the Server Returns (Success Response): 
{
  "success": true,
  "message": "Database 'alpha_base_db' successfully dropped from space assets."
}
POST Bearer Required ?action=view_my_logs

Returns a running list of every single command run across your profile. The logs are sorted cleanly from **Newest to Oldest** and record your incoming connection's actual remote IP location string.

What to Send in the Request Body: 
{
  "action": "view_my_logs",
  "limit": 2
}
What the Server Returns (Success Response): 
{
  "success": true,
  "logs": [
    {
      "database_name": "alpha_base_db",
      "executed_query": "SELECT * FROM devices;",
      "remote_ip": "192.168.1.105",
      "executed_at": "2026-05-20 21:05:10"
    },
    {
      "database_name": "alpha_base_db",
      "executed_query": "INSERT INTO devices...",
      "remote_ip": "192.168.1.105",
      "executed_at": "2026-05-20 21:02:14"
    }
  ]
}
POST Bearer Required ?action=view_database_logs

Pulls history logs filtered for one single database container by providing its secret tracking UUID key handle.

What to Send in the Request Body: 
{
  "action": "view_database_logs",
  "uuid_filename": "b9ea32f1-c42a-4ce7-8822-1ba4e320d912",
  "limit": 1
}
What the Server Returns (Filtered Database Logs): 
{
  "success": true,
  "logs": [
    {
      "database_name": "deep_space_telemetry",
      "executed_query": "SELECT * FROM matrix;",
      "remote_ip": "45.33.2.11",
      "executed_at": "2026-05-20 18:44:02"
    }
  ]
}
POST Bearer Required ?action=view_user_collection_logs

Fetches a unified transaction stream across all database instances using a numeric user ID. Standard application keys can only query logs matching their own token ID signature parameters.

What to Send in the Request Body: 
{
  "action": "view_user_collection_logs",
  "user_id": 109,
  "limit": 1
}
What the Server Returns (Success Response): 
{
  "success": true,
  "user_id": 109,
  "email": "developer@iquipe.cloud",
  "total_records": 1,
  "logs": [
    {
      "database_name": "alpha_base_db",
      "executed_query": "SELECT * FROM devices;",
      "remote_ip": "192.168.1.105",
      "executed_at": "2026-05-20 21:05:10"
    }
  ]
}