Ramp: Get a unified request — response body — value agreement contract type: ONE TIME, PERPETUAL, RENEWABLE, request status: APPROVED, DRAFT, REJECTED, SUBMITTED, spend request type: APPROVAL ONLY, unified request type: SPEND REQUEST, unified spend request type: APPROVAL ONLY agreement contract type: ONE TIME, PERPETUAL, RENEWABLE agreement contract type: ONE TIME, PERPETUAL, RENEWABLE agreements item source
Get a unified request: response body, field value / agreement_contract_type: ONE_TIME, PERPETUAL, RENEWABLE, request_status: APPROVED, DRAFT, REJECTED, SUBMITTED, spend_request_type: APPROVAL_ONLY, unified_request_type: SPEND_REQUEST, unified_spend_request_type: APPROVAL_ONLY / agreement_contract_type: ONE_TIME, PERPETUAL, RENEWABLE / agreement_contract_type: ONE_TIME, PERPETUAL, RENEWABLE / agreements / item / source. Complete fields and constraints for contract 2026-10-27.
API reference · Contract 2026-10-27
SDK schema: Get a unified request — response body — value / agreement_contract_type: ONE TIME, PERPETUAL, RENEWABLE, request status: APPROVED, DRAFT, REJECTED, SUBMITTED, spend request type: APPROVAL ONLY, unified request type: SPEND REQUEST, unified spend request type: APPROVAL ONLY agreement contract type: ONE TIME, PERPETUAL, RENEWABLE agreement contract type: ONE TIME, PERPETUAL, RENEWABLE agreements item source
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | string | Root | Enum for the source of the PayeeAgreementSpendRequestMapping model. There are three cases where we map a SpendRequest to a PayeeAgreement: 1. There is a document uploaded on a SpendRequest that ultimately creates a PayeeAgreement 2. There is a renewal SpendRequest that is created for a particular PayeeAgreement 3. A SpendRequest is manually linked to an existing PayeeAgreement Known values: EXPANSION_REQUEST, RENEWAL, REQUEST_APPROVAL, REQUEST_LINKED_TO_AGREEMENT |