Patch a contract's label, terms or billing cycle.
Every field is optional; only the ones present in the request body are applied, so a caller can move the schedule without resending the terms.
What the recurring agreement is for. A label only — it drives no logic.
Commercial terms a client sets on a contract.
The calendar schedule a contract bills on.
endsOn anchors the cycle: a day of month ("1".."31" or "last") for monthly/quarterly/yearly, a weekday name for weekly/biweekly. It is rejected for a one-time contract.
Successful Response
A recurring billing agreement.
Minimal user data embedded in contract responses.
Contract status. A contract is live the moment it is created.
Address schema for user.
Canonical field names: street_address, address_line_2, city, state, country, zip. Accepts legacy Align/IBAN field names (street_line_1, street_line_2, postal_code) for backward compatibility with existing JSONB data.
Supported invoice/contract currencies. G10 majors + AED/HKD, plus popular crypto tokens.
The resolved calendar schedule of a contract.
Flat last-invoice data embedded in contract responses.