Skip to content

Ramp: Get a unified request — response body — value request status: APPROVED, DRAFT, REJECTED, SUBMITTED, restricted request type: SPEND ALLOCATION, spend request type: SPEND LIMIT, unified request type: SPEND REQUEST, unified spend request type: SPEND ALLOCATION accounting auto mark ready rule enabled, accounting rules, approval chain data, approval events, archive date, available actions, available actions v2, blank canvas execution id, default transaction memo, members, spending restrictions, submission policy id, travel metadata, trip accounting rules item tracking category option receiving types

Get a unified request: response body, field value / request_status: APPROVED, DRAFT, REJECTED, SUBMITTED, restricted_request_type: SPEND_ALLOCATION, spend_request_type: SPEND_LIMIT, unified_request_type: SPEND_REQUEST, unified_spend_request_type: SPEND_ALLOCATION / accounting_auto_mark_ready_rule_enabled, accounting_rules, approval_chain_data, approval_events, archive_date, available_actions, available_actions_v2, blank_canvas_execution_id, default_transaction_memo, members, spending_restrictions, submission_policy_id, travel_metadata, trip / accounting_rules / item / tracking_category_option / receiving_types. Complete fields and constraints for contract 2026-10-27.

API reference · Contract 2026-10-27

SDK schema: Get a unified request — response body — value / request_status: APPROVED, DRAFT, REJECTED, SUBMITTED, restricted request type: SPEND ALLOCATION, spend request type: SPEND LIMIT, unified request type: SPEND REQUEST, unified spend request type: SPEND ALLOCATION accounting auto mark ready rule enabled, accounting rules, approval chain data, approval events, archive date, available actions, available actions v2, blank canvas execution id, default transaction memo, members, spending restrictions, submission policy id, travel metadata, trip accounting rules item tracking category option receiving types

FieldTypePresenceDescription and constraints
$objectRootHow a PO line coded to an inventory item may be received.
available_typesarrayRequired within parentReceiving types a PO line coded to this inventory item may use.
available_types[]stringEach itemHow a purchase order line is received and matched: by quantity or by amount.
Known values: by_amount, by_quantity
default_typestringRequired within parentHow a purchase order line is received and matched: by quantity or by amount.
The item’s default receiving type. Always one of available_types.
Known values: by_amount, by_quantity
Default: by_quantity

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.