Revenue schedules API
12 endpoints. All requests need an Authorization header — see Authentication. API keys additionally need the matching scope.
| Method | Path | Description |
|---|---|---|
GET |
/api/revenue-schedules/ |
List Revenue Schedules Query: revenue_stage, account_id, owner_id, include_breakdown, limit, offset. |
POST |
/api/revenue-schedules/backfill |
Backfill Revenue Schedules Query: initial_stage. |
GET |
/api/revenue-schedules/by-account |
Get By Account |
GET |
/api/revenue-schedules/pipeline |
Get Pipeline Query: account_id, owner_id, per_stage. |
GET |
/api/revenue-schedules/projection |
Get Projection |
GET |
/api/revenue-schedules/summary |
Get Summary |
POST |
/api/revenue-schedules/sync-all |
Sync All From Opportunities |
GET |
/api/revenue-schedules/{rs_id} |
Get Revenue Schedule |
PATCH |
/api/revenue-schedules/{rs_id} |
Update Revenue Schedule Accepts a JSON body. |
DELETE |
/api/revenue-schedules/{rs_id} |
Delete Revenue Schedule |
POST |
/api/revenue-schedules/{rs_id}/sync |
Sync From Opportunity |
POST |
/api/revenue-schedules/{rs_id}/transition |
Transition Stage Accepts a JSON body. |
Try it
The full request/response schema for every endpoint is in the OpenAPI spec served by your own workspace.