---
title: "Get purchase order details"
method: GET
path: "/v1/erp/payouts/purchase_orders/{id}"
tags: ["Purchase Order"]
---

# Get purchase order details

`GET /v1/erp/payouts/purchase_orders/{id}`

## Request

- Base URL: `https://api.cardda.com`
- URL: `https://api.cardda.com/v1/erp/payouts/purchase_orders/{id}`
- Auth: HTTP bearer

Returns detailed information about a specific purchase order including all items, linked invoices, and business partner information.

## Response Structure
The response includes complete purchase order details with:
- **business_partner**: Full vendor/supplier information
- **items**: All purchase order items with approval status
- **payables**: All fiscal invoices linked to any item in this purchase order

## Authorization
- User must be a member of the company that owns the purchase order

## Path parameters

- `id` string, uuid, required

## Parameters

- `#/paths/~1v1~1erp~1payouts~1rules/get/parameters/0` (unresolved $ref)

## Response `200`

Purchase order details retrieved successfully

- Schema (unresolved $ref)

## Other responses

- `401`: Unauthorized — invalid/missing authentication token, or the caller is not authorized for this purchase order (Pundit policy). **The response body is empty** (Pundit renders nothing); branch on the status code, not the body.
- `404`: Purchase order not found (also returned when the `company-id` header points to a company the caller cannot access, or the id is not scoped to it).

---

[API](https://skmtc.dev/cardda/apis/erp-api.md) - [All operations](https://skmtc.dev/cardda/apis/erp-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cardda/apis/erp-api/revisions/0730ed26bc3c?raw)
