How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ordoro Purchase Order API

The Purchase Order API from Ordoro — 12 operation(s) for purchase order.

Ordoro Purchase Order API is one of 27 APIs that Ordoro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Purchase Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 22 operations across 12 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.ordoro.com/.

22 operations 12 paths 24 schemas 4 DELETE7 GET8 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.ordoro.com/
Resource Areas
1

Paths & Operations 22

Across 12 paths, the API surfaces 22 operations — 4 DELETE, 7 GET, 8 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Purchase Order 22
POST
/product/{sku}/buy/{supplier_id}/
Create a Purchase Order by SKU and Supplier ID
ProductBuyBySkuAndSupplierId_POST 2 params body → 200201
GET
/purchase_order/
List Purchase Orders
PurchaseOrder_GET 14 params → 200
POST
/purchase_order/
Create a Purchase Order
PurchaseOrder_POST body → 201
GET
/purchase_order/counts/
Get Purchase Order Counts
PurchaseOrderCounts_GET → 200
DELETE
/purchase_order/{po_id}/
Delete a Purchase Order by ID
PurchaseOrderByPoId_DELETE 1 param → 200
GET
/purchase_order/{po_id}/
Get a Purchase Order by ID
PurchaseOrderByPoId_GET 9 params → 200
PUT
/purchase_order/{po_id}/
Update a Purchase Order by ID
PurchaseOrderByPoId_PUT 1 param body → 200
POST
/purchase_order/{po_id}/comment/
Create a Purchase Order Comment by PO ID
PurchaseOrderCommentByPoId_POST 1 param body → 200
GET
/purchase_order/{po_id}/comment/
Retrieve Comments
PurchaseOrderCommentByPoId_GET 1 param → 200
POST
/purchase_order/{po_id}/create_goods_receipt/
Create a Purchase Order Goods Receipt by PO ID
PurchaseOrderCreateGoodsReceiptByPoId_POST 1 param body → 201
POST
/purchase_order/{po_id}/line/
Create a Purchase Order Line by PO ID
PurchaseOrderLineByPoId_POST 1 param body → 200
DELETE
/purchase_order/{po_id}/line/{po_item_id}/
Delete a Purchase Order Line by PO ID and PO Line ID
PurchaseOrderLineByPoIdAndPoItemId_DELETE 2 params → 200
PUT
/purchase_order/{po_id}/line/{po_item_id}/
Update a Purchase Order Line by PO ID and PO Line ID
PurchaseOrderLineByPoIdAndPoItemId_PUT 2 params body → 200
GET
/purchase_order/{po_id}/send/
Preview a Purchase Order
PurchaseOrderSendByPoId_GET 1 param → 200
POST
/purchase_order/{po_id}/send/
Send a Purchase Order to the Supplier
PurchaseOrderSendByPoId_POST 1 param → 200
POST
/purchase_order/tag/
Create a Purchase Order Tag
PurchaseOrderTags_POST body → 201
GET
/purchase_order/tag/
Get Purchase Order Tags
PurchaseOrderTags_GET → 200
GET
/purchase_order/tag/{name}/
Get Purchase Order Tag by Name
PurchaseOrderTag_GET → 200
PUT
/purchase_order/tag/{name}/
Update a Purchase Order Tag by Name
PurchaseOrderTags_PUT body → 200
DELETE
/purchase_order/tag/{name}/
Delete a Purchase Order Tag by Name
PurchaseOrderTags_DELETE → 200
POST
/purchase_order/{po_id}/tag/{tag_name}/
Apply a Purchase Order Tag to Purchase Order
PurchaseOrderTagPO_POST → 200
DELETE
/purchase_order/{po_id}/tag/{tag_name}/
Remove a Purchase Order Tag from a Purchase Order
PurchaseOrderTagPO_DELETE → 200

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are product_base (35 properties), supplier (20 properties), purchase_order (20 properties), address (15 properties). Each schema is shown below with its type and property counts.

v3_tag_list
object
4 properties 4 required
post_v3_tag
object
2 properties 2 required
v3_tag
object
3 properties 3 required
PurchaseOrderSort
string
product_base
object
35 properties
post_purchase_order
object
11 properties 1 required
put_v3_tag
object
2 properties
supplier
object
20 properties 10 required
warehouse
object
6 properties 5 required
post_buy_more
object
5 properties 2 required
post_purchase_order_item
object
4 properties 1 required
address
object
15 properties 10 required
put_purchase_order
object
11 properties
purchase_order_item
object
4 properties 2 required
post_purchase_order_goods_receipt
object
1 property
post_comment
object
1 property 1 required
put_purchase_order_item
object
3 properties
purchase_order
object
20 properties
purchase_order_list
object
4 properties
PurchaseOrderStatus
string
comment
object
3 properties
purchase_order_counts
object
6 properties 6 required
supplier_shipping_method_map
object
9 properties 9 required
goods_receipt
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ordoro-purchase-order-api-openapi.yml Raw ↑

Other APIs Ordoro publishes across the network.

Ordoro Address API
Ordoro Api Key API
Ordoro Authenticated API
Ordoro Cart API
Ordoro Company API
Ordoro Goods Receipt API
Ordoro Integration API
Ordoro Label API
Ordoro Manufacturing Order API
Ordoro Order API
Ordoro Packing List API
Ordoro Postage Account API
Where this information came from

This is an independent, third-party profile of Ordoro Purchase Order API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.