Developer docs

Suite Profit developer documentation

These docs are for enterprise integrators building against the Suite Profit API — a group's own IT team, a systems integrator engaged by the CIO, or a third-party service consuming portfolio-tier module output. Everything below assumes a live Suite Profit portfolio contract with at least one production module deployed and Profitroom Suite connections active across every property in the group.

API reference

Every REST endpoint the Suite Profit API exposes for portfolio-tier modules running against a group's Profitroom Suite footprint.

Read docs

Webhooks

Subscribing to group and property events, HMAC signing under portfolio-scoped keys, delivery guarantees and retry policy.

Read docs

Rate limits

Per-module and per-portfolio buckets, HTTP 429 handling, X-RateLimit-* headers, negotiated enterprise quotas.

Read docs

Error codes

The SP-1001 through SP-1024 error taxonomy with remediation, including group-scoped and property-scoped failure modes.

Read docs

Base URL and versioning

All Suite Profit API endpoints are served from https://api.suiteprofit.org/v1. The API is versioned in the path. When a breaking change lands, we ship a new major version (/v2) and keep the previous major version live for at least 12 months with a written migration note for procurement. Non-breaking changes go into /v1 in place and are announced on the changelog.

Authentication

Every request requires an Authorization: Bearer <token> header. Tokens are issued from the group's Suite Profit dashboard, one per integration, with a scope selector — portfolio-read, portfolio-write, property-scoped or module-scoped. Enterprise deployments federate identity through Corporate SSO Hub; API tokens are issued under a portfolio-scoped service principal and rotate on a 90-day cadence recorded in the audit log.

Support for developers

Developer questions from an enterprise group are routed through the dedicated account manager — email support@suiteprofit.org from a domain matching the group's SSO tenant and the ticket carries the enterprise SLA automatically. Every reported bug is triaged inside one business day.