The Assessments API lets external systems start and manage assessments without going through the dashboard. The most common use case is a GRC tool or scheduled job kicking off a reassessment of a known vendor.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.
Start an assessment
POST /v1/assessmentsRequest body
The Coverbase vendor ID (
cbvndr_...) the assessment runs against.Array of control set IDs (
cbcset_...) to evaluate the vendor against. Assessments can evaluate against one or more policy control sets.Assessment risk type. Values come from the
RiskType enum and include security-oriented types. Verify available values for your org through the dashboard.Assessment name. Required unless
assessment_name_format is provided.If provided (even as an empty string), auto-generates the assessment name using the built-in format. Use this OR
name, not both.Optional array of service IDs (
cbsvc_...) the assessment covers. An assessment can cover multiple services.Optional name of a workflow to invoke. If omitted, any workflow bound to
assessment.created runs by default. If specified, that named workflow runs instead.Optional user ID to assign the assessment to. Defaults to the vendor’s risk owner.
Optional array of document IDs (
cbdoc_...) to attach as evidence.How evidence is collected. Values come from the
DocCollectionMode enum.Optional array of product name strings associated with this assessment.
Headers
Bearer <api-key>Optional. If the same key is sent twice within 24 hours, the second call returns the original response without starting a new assessment. Recommended for retries on network failure.
Example request
Example response
Response fields
The new assessment ID.
The vendor the assessment runs against.
The assessment name, either provided directly or auto-generated from
assessment_name_format.The services the assessment covers, if any were specified.
The control sets being evaluated.
The risk type passed in the request.
Current status. The assessment status system uses org-customizable labels (via
CbStatus), so initial values vary by org configuration.The assigned user, if any.
The workflow run that this assessment triggered, when applicable. Use this to correlate downstream webhooks.
Unix timestamp when the assessment was initiated. May differ from
created_at if the assessment is created in a pending state before initiation.Unix timestamp when the assessment was created.
Retrieve an assessment
GET /v1/assessments/{assessment_id}Example request
cURL
Example response
Response fields
Score as a decimal between 0 and 1 representing the assessment outcome.
Derived count of evaluations flagged as findings within this assessment. This is a computed value, not a stored field.
Unix timestamp when the assessment was initiated.
Error responses
| Status | Code | When |
|---|---|---|
| 400 | missing_required_field | One of vendor_id, control_set_ids, or risk_type was omitted. |
| 400 | invalid_control_set_ids | One or more IDs in control_set_ids do not exist or are not accessible to the API key. |
| 404 | vendor_not_found | The provided vendor_id does not exist or is not accessible to the API key. |
| 404 | workflow_not_found | The provided trigger_workflow name is not configured for this org. |
| 409 | idempotency_conflict | An assessment already exists for this idempotency key. The original response is returned in the body. |