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 Vendors API

The vendors API from OpenGov — 5 operation(s) for vendors.

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

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

This API exposes 7 operations across 5 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

7 operations 5 paths 31 schemas 1 DELETE1 GET1 PATCH4 POST

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
HTTP Bearer
Resource Areas
1

Authentication & Security 1

OpenGov Vendors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT Authorization header using the Bearer scheme

Paths & Operations 7

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

vendors 7
GET
/api/v1/entities/{entityId}/vendors/{vendorKey}
vendors.getVendorById 4 params → 200400401403404500
PATCH
/api/v1/entities/{entityId}/vendors/{vendorKey}
vendors.updateVendor 3 params body → 200400401403404500
DELETE
/api/v1/entities/{entityId}/vendors/{vendorKey}
vendors.deleteVendor 3 params → 204400401403404500
POST
/api/v1/entities/{entityId}/vendors
vendors.createVendor 2 params body → 200400401403404500
POST
/api/v1/entities/{entityId}/vendors/{vendorKey}/submit
vendors.submitVendor 3 params → 200400401403404500
POST
/api/v1/entities/{entityId}/vendors/{vendorKey}/promote
vendors.promoteVendor 3 params body → 200400401403404500
POST
/api/v1/entities/{entityId}/vendors/{vendorKey}/availability
vendors.updateVendorAvailability 3 params body → 200400401403404500

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are VendorModel (46 properties), ContactModel.json (13 properties), AddressModel.json (12 properties), PaymentMethodModel.json (10 properties). Each schema is shown below with its type and property counts.

AddressModel.jsonCreate
object
7 properties 5 required
ContactId
number
Unique identifier for a contact
PaymentMethodModel.json
object
10 properties 5 required
CertificateId
number
Unique identifier for a certificate
NotFoundHttpError
object
3 properties 2 required
CertificateModel.jsonCreate
object
4 properties
PaymentId
number
Unique identifier for a payment method
VendorCategoriesModel.jsonUpdate
object
4 properties 4 required
AddressModel.json
object
12 properties 6 required
ContactModel.json
object
13 properties 1 required
VendorCategoriesModel.json
object
9 properties 5 required
NonEmptyString
string
a non empty string
PaymentMethodModel.jsonCreate
object
5 properties 4 required
VendorCategoriesModel.jsonCreate
object
4 properties 4 required
CategoryId
number
Unique identifier for a category
UnauthenticatedHttpError
object
2 properties 2 required
Issue
object
Represents an error encountered while parsing a value to match the schema
3 properties 3 required
AddressId
number
Unique identifier for an address
AttachmentModel.json
object
10 properties 6 required
VendorModel
object
46 properties 8 required
InternalServerHttpError
object
2 properties 2 required
BadRequestHttpError
object
4 properties 2 required
CertificateModel.json
object
10 properties 1 required
EntityNotFoundError
object
2 properties 2 required
HttpApiDecodeError
object
The request did not match the expected schema
3 properties 3 required
VendorKey
number
Unique identifier for a vendor
AuthError
object
2 properties 1 required
UnauthorizedHttpError
object
3 properties 2 required
AttachmentId
number
Unique identifier for an attachment
PropertyKey
ContactModel.jsonCreate
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opengov-vendors-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 Change Order By Po API
OpenGov Chart Of Accounts API
Where this information came from

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