Documentation Index
Fetch the complete documentation index at: https://docs.gateways.app/llms.txt
Use this file to discover all available pages before exploring further.
Utility Resources (Terminals, Bucket Explorers, DB Monitors)
Utility resources share a common table (utility_resources) and consistent CRUD patterns. Each resource type is identified by resource_type:
terminal— connect to instances via SSH/WebSocketbucket_explorer— browse S3 buckets or static websitesdb_monitor— attach metadata for DB health/metrics dashboards
Create
POST /api/:projectSlug/:environmentSlug/terminalsPOST /api/:projectSlug/:environmentSlug/bucket-explorersPOST /api/:projectSlug/:environmentSlug/db-monitors
name(string, required)positionX,positionY(optional canvas coords)metadata(optional JSON; used by db_monitors for config, by bucket_explorers for bucket info)
nameis the S3 bucket name (must follow AWS rules, globally unique). Region optional; will auto-detect when importing existing buckets.
List
GET /api/:projectSlug/:environmentSlug/terminalsGET /api/:projectSlug/:environmentSlug/bucket-explorersGET /api/:projectSlug/:environmentSlug/db-monitors
id, name, status, metadata, position, timestamps.
Get one
GET /api/:projectSlug/:environmentSlug/terminals/:terminalIdGET /api/:projectSlug/:environmentSlug/bucket-explorers/:bucketExplorerIdGET /api/:projectSlug/:environmentSlug/db-monitors/:monitorId
Update
PATCH /api/:projectSlug/:environmentSlug/terminals/:terminalIdPATCH /api/:projectSlug/:environmentSlug/bucket-explorers/:bucketExplorerIdPATCH /api/:projectSlug/:environmentSlug/db-monitors/:monitorId
name, status, metadata, positionX, positionY.
Delete
Deletion is performed only via the unified resources API. Use the resource’s database ID (from the list or get-one response):DELETE /api/:projectSlug/:environmentSlug/resources/:resourceId
resource_connections and then soft-deletes the utility resource.
DB Monitor Pulse/Metrics
GET /api/:projectSlug/:environmentSlug/db-monitors/:monitorId/pulse- Get database metrics using DB monitor (CPU, connections, memory, storage, I/O, network)
- Fetches real-time and historical metrics from AWS CloudWatch for the connected database
- Automatically resolves the connected database from the resource connection between the DB monitor and database
- Returns CPU utilization, database connections, memory, storage, read/write latency, IOPS, and network throughput
- Supports custom time ranges and aggregation periods
- Note: The DB monitor must be connected to a database via resource connections for this endpoint to work
monitorId- DB monitor database ID
startTime(optional): ISO 8601 timestamp for start time (default: 1 hour ago)endTime(optional): ISO 8601 timestamp for end time (default: now)period(optional): Period in seconds for metric aggregation (default: 300 = 5 minutes, minimum: 60)
- Values are the most recent (latest) single data point from CloudWatch
cpu: CPU utilization percentage (0-100)ram: Freeable memory in bytesconnections: Number of active database connections- If a metric has no data available, it will be
null
Positions
All utility resources includeposition in responses and can be updated via:
PATCH /api/:projectSlug/:environmentSlug/resources/:resourceId/position(use resource’s database ID)
Resources listing
Utility resources are returned by:GET /api/:projectSlug/:environmentSlug/resources(project/environment scope; filter withtype=db_monitors,type=bucket_explorers, ortype=terminals)- Resource detail:
GET /api/:projectSlug/:environmentSlug/resources/:resourceId(use resource’s database ID)