The Vendors API lets external systems read and update individual vendor records. To create or bulk-update vendors, use the Import API instead. The most common use of this API is lifecycle transitions: signaling that a vendor is offboarding, suspending a vendor pending review, or unblocking a procurement record once an assessment completes.Documentation Index
Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
Use this file to discover all available pages before exploring further.
Retrieve a vendor
GET /v1/vendors/{vendor_id}Path parameters
The Coverbase vendor ID (
cbvndr_...).Example request
cURL
Example response
Response fields
The Coverbase vendor ID.
External system identifier (e.g., an Ariba request ID) if one was provided during import.
Vendor name.
Vendor website URL.
Vendor description.
Headquarters location.
The vendor’s current status as a
CbStatus object with id, label, and group fields. The group is one of unstarted, started, completed, or canceled.Array of tag objects, each with
id and name fields.User IDs of assigned risk analysts.
User IDs of relationship owners.
ID of the scale level representing inherent risk.
ID of the scale level representing residual risk.
Raw IRQ (Inherent Risk Questionnaire) score.
Type of engagement with this vendor.
How the vendor is used within the organization.
Unix timestamp of the next scheduled assessment.
Outcome of the most recent assessment.
Unix timestamp when the vendor record was created.
Unix timestamp of the last update.
Update a vendor
PATCH /v1/vendors/{vendor_id}vendor.updated and, if status changes, vendor.status_changed webhooks.
Updatable fields
ID of a
CbStatus record to transition to. Must be a valid, non-archived vendor status for the org.Vendor name.
Vendor website URL. Send an empty string to clear.
Vendor description.
Headquarters location.
Replace the entire set of risk analyst user IDs.
Replace the entire set of relationship owner user IDs.
Replace the entire tag set using
CbTag IDs.Scale level ID for inherent risk.
Scale level ID for residual risk.
Raw IRQ score value.
Unix timestamp of the next scheduled assessment.
How the vendor is used within the organization.
Type of engagement with this vendor.
Array of custom field value objects for org-specific fields.
Example request
Example response
This update fires both
vendor.updated and vendor.status_changed webhooks. Any workflow bound to those events will run, for example the offboarding sequence described in Workflow C: Vendor offboarding.Vendor statuses
Vendor statuses are org-customizable. Each status belongs to a group (unstarted, started, completed, canceled). Use the dashboard or a list statuses endpoint to see available statuses for your org.
Any valid, non-archived vendor status ID can be set via status_id. Status transitions are not enforced — you can move a vendor to any status that exists for your org.
Statuses are
CbStatus records with target_type=VENDOR. Each org defines their own status labels, colors, and groups. If you need to discover available statuses programmatically, query the statuses list endpoint filtered by target type.Error responses
| Status | Code | When |
|---|---|---|
| 400 | invalid_status_id | The provided status_id doesn’t exist, is archived, or isn’t a vendor status for this org. |
| 400 | missing_required_field | A required field was omitted. |
| 404 | vendor_not_found | The provided vendor_id does not exist or is not accessible to the API key. |