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

Broadlume Purchase Order API

The Purchase Order API from Broadlume — 13 operation(s) for purchase order.

Broadlume Purchase Order API is one of 28 APIs that Broadlume 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, an API reference, and authentication docs.

This API exposes 16 operations across 13 paths. It is described by OpenAPI 3.2.0, at version v1.

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

16 operations 13 paths 0 schemas 12 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.rmaster.com/api
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Broadlume Purchase Order API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (apiKeyAuth). An API key is passed in the header as token (sessionToken). By default, every request must be authenticated.

  • apiKeyAuth — API key issued by Broadlume, required on every request.
  • sessionToken — User session token obtained from POST /{alias}/token. Sessions expire after a server-specified idle timeout (default 5 minutes); refresh with the keepalive end…

Paths & Operations 16

Across 13 paths, the API surfaces 16 operations — 12 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Purchase Order 16
PATCH
/{alias}/po
Update PO
updatePo 24 params → 200
GET
/{alias}/purchaseorderlines
Read purchase order lines that are open
readPurchaseOrderLinesThatAreOpen 2 params body → 200
GET
/{alias}/purchaseorderheader
Purchase order detail
purchaseOrderDetail 4 params → 200
GET
/{alias}/purchaseorderheaders
List of purchase orders by date
listOfPurchaseOrdersByDate 7 params → 200
GET
/{alias}/shipvia
PO Shipvia
poShipvia 2 params → 200
GET
/{alias}/freightterms
PO Freight Terms
poFreightTerms 2 params → 200
GET
/{alias}/smop
PO Shipment Method of Payment
poShipmentMethodOfPayment 2 params → 200
GET
/{alias}/vendortypes
Vendor Type List
vendorTypeList 2 params → 200
GET
/{alias}/customertype
Customer Type List
customerTypeList 2 params → 200
POST
/{alias}/ponote
Creates a PO Note
createsAPoNote 1 param body → 200
PATCH
/{alias}/ponote
Edits a PO Note
editsAPoNote 7 params → 200
GET
/{alias}/ponote
Reads PO Notes
readsPoNotes 6 params → 200
POST
/{alias}/polinecomments
Create PO Line Comment
createPoLineComment 1 param body → 200
GET
/{alias}/polinecomments
Get PO line commments
getPoLineCommments 5 params → 200
GET
/{alias}/popointers
Get PO Pointers
getPoPointers 5 params → 200
GET
/{alias}/pos
Get Purchase Order File Data - SQL Format
getPurchaseOrderFileDataSqlFormat 5 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Broadlume publishes across the network.

Broadlume Accounts Receivable API
Broadlume Audit API
Broadlume Authentication API
Broadlume Build Order API
Broadlume Bundle API
Broadlume Charge It Pro API
Broadlume Committed API
Broadlume Company API
Broadlume Customer API
Broadlume Dashboard API
Broadlume Edocs API
Broadlume General API
Where this information came from

This is an independent, third-party profile of Broadlume 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.