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

OpenGov Change Order By Po API

The changeOrderByPo API from OpenGov — 10 operation(s) for changeorderbypo.

OpenGov Change Order By Po API is one of 102 APIs that OpenGov publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include changeOrderByPo. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 13 operations across 10 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://api-purchase-order.procurement.opengov.com, https://api-purchase-order.procurement.ogstaging.us, https://api-purchase-order.procurement.ogintegration.us.

13 operations 10 paths 12 schemas 2 DELETE2 GET7 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.plce.opengov.com/plce
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

OpenGov Change Order By Po API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (platformApiKey). It accepts HTTP bearer tokens (platformBearerToken). By default, every request must be authenticated.

  • platformApiKey — OpenGov Platform API Key

Paths & Operations 13

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

changeOrderByPo 13
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders
Create a new change order for a purchase order
changeOrderByPo.createChangeOrder 2 params body → 201400401403404409500
GET
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}
Get a change order with full PO context
changeOrderByPo.getChangeOrder 3 params → 200400401403404500
PUT
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}
Update a Draft change order
changeOrderByPo.updateChangeOrder 3 params body → 200400401403404409500
DELETE
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}
Delete a Draft change order
changeOrderByPo.deleteChangeOrder 3 params → 204400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/lines
Add a line to a Draft change order
changeOrderByPo.addChangeOrderLine 3 params body → 201400401403404409500
PUT
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/lines/{lineId}
Update a line on a Draft change order
changeOrderByPo.updateChangeOrderLine 4 params body → 200400401403404409500
DELETE
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/lines/{lineId}
Remove a line from a Draft change order
changeOrderByPo.removeChangeOrderLine 4 params → 204400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/clear-tolerances
Clear tolerance fields on a Draft change order
changeOrderByPo.clearCoTolerances 3 params → 200400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/submit
Submit a Draft change order for approval
changeOrderByPo.submitChangeOrder 3 params body → 200400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/cancel
Cancel a Draft change order
changeOrderByPo.cancelChangeOrder 3 params → 200400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/approve
Approve a pending change order
changeOrderByPo.approveChangeOrder 3 params → 200400401403404409500
POST
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/reject
Reject a pending change order
changeOrderByPo.rejectChangeOrder 3 params → 200400401403404409500
GET
/api/v1/po/entities/{entityId}/purchase-orders/{poId}/change-orders/{coId}/operation-errors
List unresolved operation errors for a Change Order
changeOrderByPo.listCoOperationErrors 3 params → 200400401403404500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed is OperationErrorModel.json (10 properties). Each schema is shown below with its type and property counts.

ISODate
string
a string matching the pattern ^\d{4}-\d{2}-\d{2}$
OperationErrorPhase
string
OperationErrorModel.json
object
10 properties 10 required
OperationErrorEntityType
string
OperationErrorCode
string
LineItemType
string
Line item type: Item, Service, Tax, Discount, Freight, Miscellaneous
CoChangeType
string
Change order line change type: LineModified, LineAdded
NumberFromString
string
a string to be decoded into a number
OperationErrorSeverity
string
ValueOrPercent
string
Indicates whether the input is an absolute value or a percentage
EncumbranceTrigger
string
CoChangeKind
string
Change order line/split change kind: Modify (apply delta) or Delete (remove row)

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opengov-changeorderbypo-api-openapi.yml Raw ↑

Other APIs OpenGov publishes across the network.

OpenGov Activity API
OpenGov Activity Logs API
OpenGov Admin Settings API
OpenGov Approval Steps API
OpenGov Attachment API
OpenGov Attachment Limits API
OpenGov Attachments API
OpenGov Budget API
OpenGov Categories API
OpenGov Change Order API
OpenGov Chart Of Accounts API
OpenGov Checklist Results API
Where this information came from

This is an independent, third-party profile of OpenGov Change Order By Po 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.