Documentation

Technical reference for integrating with Old West Solutions — APIs for provisioning, status, billing hooks, and event streams. All examples use TLS 1.2+ and JSON unless noted.

Base URL: api.oldwestsolutions.comAPI version: v1

Authentication

Use OAuth 2.0 client credentials for server-to-server calls, or long-lived API keys scoped to environments (sandbox / production). Rotate keys from the operator portal when it is enabled for your org.

curl -s https://api.oldwestsolutions.com/v1/status \
  -H "Authorization: Bearer $OWS_TOKEN" \
  -H "Accept: application/json"

REST API highlights

Idempotent writes where applicable; Idempotency-Key header supported on POST.

Method	Endpoint	Description
GET	/v1/status	Account and region health snapshot.
GET	/v1/services	Managed services and SKUs on contract.
POST	/v1/events/ingest	Inbound application events (signed payload).
GET	/v1/domains	Domains under management (read-only).
POST	/v1/tickets	Open support or change request.

Webhooks

Subscribe to deployment.completed, invoice.finalized, and incident.updated. Each delivery includes an OWS-Signature header (HMAC-SHA256) for verification.

{
  "id": "evt_8f2a…",
  "type": "deployment.completed",
  "created": 1710000000,
  "data": { "environment": "production", "revision": "abc123" }
}

SDKs & tools

▸OpenAPI 3.1 — Download the machine-readable spec from your onboarding pack; public export coming to this portal.
▸Terraform provider — Infrastructure modules for common managed patterns (beta by request).
▸CLI — Authenticate, tail logs, and trigger approved runbooks from your terminal.

Limits & SLA

Default rate limit: 1200 requests / minute per API key (burst allowed). Higher tiers available in enterprise agreements. API availability targets match your managed services schedule of services.

Need a signed PDF, IP allowlist, or dedicated endpoint cluster?

Contact solutions engineering