Overview
Learn how the gospace API is structured, versioned, and secured for production use.
The gospace API powers the Platform. Every endpoint uses JSON over HTTPS and stable, versioned URLs.
Base URLs & versioning
- Production:
https://api.gospace.ai - UAT/sandbox:
https://api.uat.gospace.ai
Requests are versioned under /v1. Example:
GET https://api.gospace.ai/v1/system/health
Surface map
- Auth (
/v1/auth) — Login, tokens, and workspace API keys. - System (
/v1/system) — Health, workspaces, usage, and workspace variables. - Data (
/v1/data) — Data sources, sync, and search. - Integrations (
/v1/integrations) — Manage connected providers. - Agents (
/v1/agents) — Agents and blueprints. - AI (
/v1/ai) — Run agents and chat endpoints. - Webhooks (
/v1/webhooks) — Register webhook endpoints and event filters. - Audit (
/v1/audit) — Audit logs and compliance exports. - Notifications (
/v1/notifications) — Notification settings and events. - Billing (
/v1/billing) — Plans, invoices, and usage. - Solutions (
/v1/solutions) — Packaged workflows (for example workplace forecasting). - MCP (
/api/v1/mcp) — Model Context Protocol JSON-RPC endpoint.
See API Reference for a concise endpoint index.
Common guidance:
Rate limits
Rate limits vary by tenant and service. When you hit a limit, the API returns 429 Too Many Requests with Retry-After. Back off with jitter and retry.
Need more throughput? Contact support@gospace.ai with your workload profile.