ramp-manage-procurement

First resolve the vendor UUID with ramp vendors search, then filter purchase orders by payee_uuids using ramp purchase_orders search with a JSON filter. The filters.search field matches PO numbers, request names, and owner names but not vendor names.

Run ramp requests get to confirm approval_workflow.needs_user_action is true, show the user the request details, then call ramp requests approve with the unified_request_id and action APPROVE. Approval acts on the unified request UUID, not the purchase order ID.

The spend request may still be pending and the PO not yet issued. Search unified requests scoped to PURCHASE_ORDER type with ramp requests search to find the request before PO issuance.

purchase_order_id identifies the issued PO for lookup and detail, while unified_request_id identifies the request used for search, pending queues, approval, and rejection. Request list rows do not expose purchase_order_id; call requests get to retrieve it.

Do not use it to create, edit, or submit draft requests (use ramp-submit-procurement-request), to track sourcing events or RFPs (use ramp-manage-sourcing), or for cross-product approval queues (use ramp-approval-dashboard). It also excludes bill approval, reimbursements, and card transactions.