Create or replace the billing contract for an organizationhidden
hidden
Parameters
Name
Type
Req.
bodyapplication/json
objectoptionalObject Properties
Possible values
annual: The contract is managed on an annual cycle.quarterly: The contract is managed on a quarterly cycle.monthly: The contract is managed on a monthly cycle.manual: The contract does not follow a fixed automated cadence.
Possible values
pooled: One shared commitment pool may fund multiple contract items.per_item: Each contract item effectively manages its own commitment budget.
items
arrayoptionalArray of
Possible values
minute: Usage should be normalized or rounded at the minute level.second: Usage should be normalized or rounded at the second level.
Possible values
enterprise_support: Fixed or recurring enterprise support entitlement.fde: Full deployment environment or similar managed environment charge.govcloud_management: GovCloud-specific management or hosting charge.file_ingestion_conversion: Billing for the first successful conversion of a file version.licensed_api_credits: Contract-rated API usage credits.
Possible values
fixed_fee: A flat amount that does not vary with measured usage.usage_tiered: Usage is rated by one or more explicit pricing tiers.usage_commitment_bucket: Usage burns down a commitment bucket before any overage path.
rate_tiers
arrayoptionalArray of
Possible values
file: Quantity is counted in files.minute: Quantity is counted in whole or rounded minutes.second: Quantity is counted in seconds.year: Quantity is counted in years.period: Quantity is counted once per billing period.
periods
arrayoptionalArray of
Possible values
open: Period is active and may still accrue usage or adjustments.closed: Period is finalized and should be treated as read-only for billing purposes.
Possible values
stripe: Charges are ultimately collected through Stripe.manual_invoice: Charges are collected outside Stripe, usually by finance or contract workflow.
Possible values
none: Unused commitment expires at the end of the period.year1_to_year2_once: Unused year-one commitment may roll once into year two, but not beyond.
Possible values
draft: Contract terms are still being assembled and should not drive billing yet.scheduled: Contract is committed for a future start date and should not drive billing yet.active: Contract is in force and may be used for rating and funding decisions.closed: Contract finished its intended term and is no longer accruing new periods.canceled: Contract was intentionally terminated before completing its intended term.
Returns
- 200 OK
successful operation
Name
Type
Req.
body
objectoptionalObject Properties
Possible values
annual: The contract is managed on an annual cycle.quarterly: The contract is managed on a quarterly cycle.monthly: The contract is managed on a monthly cycle.manual: The contract does not follow a fixed automated cadence.
Possible values
pooled: One shared commitment pool may fund multiple contract items.per_item: Each contract item effectively manages its own commitment budget.
items
arrayoptionalArray of
Possible values
minute: Usage should be normalized or rounded at the minute level.second: Usage should be normalized or rounded at the second level.
Possible values
enterprise_support: Fixed or recurring enterprise support entitlement.fde: Full deployment environment or similar managed environment charge.govcloud_management: GovCloud-specific management or hosting charge.file_ingestion_conversion: Billing for the first successful conversion of a file version.licensed_api_credits: Contract-rated API usage credits.
Possible values
fixed_fee: A flat amount that does not vary with measured usage.usage_tiered: Usage is rated by one or more explicit pricing tiers.usage_commitment_bucket: Usage burns down a commitment bucket before any overage path.
rate_tiers
arrayoptionalArray of
Possible values
file: Quantity is counted in files.minute: Quantity is counted in whole or rounded minutes.second: Quantity is counted in seconds.year: Quantity is counted in years.period: Quantity is counted once per billing period.
periods
arrayoptionalArray of
Possible values
open: Period is active and may still accrue usage or adjustments.closed: Period is finalized and should be treated as read-only for billing purposes.
Possible values
stripe: Charges are ultimately collected through Stripe.manual_invoice: Charges are collected outside Stripe, usually by finance or contract workflow.
Possible values
none: Unused commitment expires at the end of the period.year1_to_year2_once: Unused year-one commitment may roll once into year two, but not beyond.
Possible values
draft: Contract terms are still being assembled and should not drive billing yet.scheduled: Contract is committed for a future start date and should not drive billing yet.active: Contract is in force and may be used for rating and funding decisions.closed: Contract finished its intended term and is no longer accruing new periods.canceled: Contract was intentionally terminated before completing its intended term.
put
/orgs/{id}/billing/contract200 OK
Response