Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zuper Purchase Orders API

Vendor purchase order management

Zuper Purchase Orders API is one of 14 APIs that Zuper publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Purchase Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, a changelog, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://{dc_region}.zuperpro.com/api, https://accounts.zuperpro.com/api.

7 operations 4 paths 1 schemas 1 DELETE2 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://accounts.zuperpro.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Zuper Purchase Orders API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key generated from Zuper Settings Developer Hub API Keys

Paths & Operations 7

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

Purchase Orders 7

Vendor purchase order management

GET
/purchase_orders
Get Purchase Orders
getPurchaseOrders 3 params → 200
POST
/purchase_orders
Create Purchase Order
createPurchaseOrder body → 200400
GET
/purchase_orders/{purchase_order_uid}
Get Purchase Order Details
getPurchaseOrderDetails 1 param → 200404
PUT
/purchase_orders/{purchase_order_uid}
Update Purchase Order
updatePurchaseOrder 1 param body → 200400
DELETE
/purchase_orders/{purchase_order_uid}
Delete Purchase Order
deletePurchaseOrder 1 param → 200404
POST
/purchase_orders/{purchase_order_uid}/send
Send Purchase Order
sendPurchaseOrder 1 param → 200
PUT
/purchase_orders/{purchase_order_uid}/status
Update Purchase Order Status
updatePurchaseOrderStatus 1 param body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is PaginatedResponse (4 properties). Each schema is shown below with its type and property counts.

PaginatedResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zuper-purchase-orders-api-openapi.yml Raw ↑

Other APIs Zuper publishes across the network.

Zuper Assets API
Zuper Authentication API
Zuper Customers API
Zuper Invoices API
Zuper Jobs API
Zuper Organizations API
Zuper Projects API
Zuper Properties API
Zuper Teams API
Zuper Timesheets API
Zuper Users API
Zuper Vendors API