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

Wegalvanize Compliance Maps API

You can use Compliance Maps to associate industry standards and regulations with your control frameworks.Learn more.

Wegalvanize Compliance Maps API is one of 69 APIs that Wegalvanize publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Compliance Maps. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 19 operations across 9 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

Requests are made against a single base URL, {protocol}://{server}/v1.

19 operations 9 paths 18 schemas 4 DELETE7 GET4 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0
Base URL
https://apis-us.highbond.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wegalvanize Compliance Maps API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (oauth2) (bearerToken). By default, every request must be authenticated.

  • bearerToken — HighBond offers the industry-standard OAuth 2.0 flow for connecting to the HighBond platform. OAuth 2.0 provides a safe and secure way to access data, while pr…

Paths & Operations 19

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

Compliance Maps 19

You can use Compliance Maps to associate industry standards and regulations with your control frameworks. Learn more .

GET
/orgs/{org_id}/compliance_regulations
Get compliance regulations
getComplianceRegulations 8 params → 200400401403404413415
POST
/orgs/{org_id}/compliance_regulations
Create a compliance regulation
createComplianceRegulation 2 params body → 201400401403404415422
GET
/orgs/{org_id}/compliance_regulations/{id}
Get a compliance regulation
getComplianceRegulation 3 params → 200400401403404413415
PATCH
/orgs/{org_id}/compliance_regulations/{id}
Update a compliance regulation
updateComplianceRegulation 3 params body → 200400401403404415422
DELETE
/orgs/{org_id}/compliance_regulations/{id}
Delete a compliance regulation
deleteComplianceRegulation 2 params → 204401403404
GET
/orgs/{org_id}/compliance_regulations/{compliance_regulation_id}/compliance_requirements
Get compliance requirements
getComplianceRequirements 10 params → 200400401403404413415
POST
/orgs/{org_id}/compliance_regulations/{compliance_regulation_id}/compliance_requirements
Create a compliance requirement
createComplianceRequirement 4 params body → 201400401403404415422
GET
/orgs/{org_id}/compliance_requirements/{id}
Get a compliance requirement
getComplianceRequirement 4 params → 200400401403404413415
PATCH
/orgs/{org_id}/compliance_requirements/{id}
Update a compliance requirement
updateComplianceRequirement 4 params body → 200400401403404415422
DELETE
/orgs/{org_id}/compliance_requirements/{id}
Delete a compliance requirement
deleteComplianceRequirement 2 params → 204401403404
POST
/orgs/{org_id}/related_requirements
Create a link between requirements
postRelatedRequirement 2 params body → 201400401403404415
GET
/orgs/{org_id}/related_requirements/{id}
Get a link between requirements
getRelatedRequirement 3 params → 200400401403404415
PATCH
/orgs/{org_id}/related_requirements/{id}
Update a link between requirements
updateRelatedRequirement 3 params body → 200400401403404415422
DELETE
/orgs/{org_id}/related_requirements/{id}
Delete a link between requirements
deleteRelatedRequirement 2 params → 204401403404
GET
/orgs/{org_id}/compliance_requirements/{compliance_requirement_id}/related_requirements
Get related compliance requirements
getRelatedRequirements 5 params → 200400401403404415
POST
/orgs/{org_id}/compliance_mappings
Create a compliance mapping
createComplianceMapping 2 params body → 201400401403404409415422
GET
/orgs/{org_id}/compliance_mappings/{id}
Get a compliance mapping
getComplianceMapping 3 params → 200400401403404413415
PATCH
/orgs/{org_id}/compliance_mappings/{id}
Update a compliance mapping
updateComplianceMapping 3 params body → 200400401403404415422
DELETE
/orgs/{org_id}/compliance_mappings/{id}
Delete a compliance mapping
deleteComplianceMapping 2 params → 204401403404

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Error (5 properties), GetComplianceRequirementsResponseWithIncludes (3 properties), GetComplianceMappingResponseWithIncludes (2 properties), GetComplianceRegulationsResponse (2 properties). Each schema is shown below with its type and property counts.

GetComplianceMappingResponseWithIncludes
object
The data associated with the resource.
2 properties 1 required
GetComplianceRegulationResponse
object
The data associated with the resource.
1 property 1 required
CreateComplianceMappingRequest
object
The data associated with the resource.
1 property 1 required
UpdateComplianceRequirementRequest
object
The data associated with the resource.
1 property 1 required
CreateComplianceRequirementRequest
object
The data associated with the resource.
1 property 1 required
CreateComplianceRegulationRequest
object
The data associated with the resource.
1 property 1 required
Error
object
5 properties 1 required
UpdateRelatedRequirementRequest
object
The data associated with the resource.
1 property 1 required
GetRelatedRequirementsResponse
object
The data associated with the resource.
2 properties 1 required
CreateRelatedRequirementResponse
object
The data associated with the resource.
1 property 1 required
UpdateComplianceRegulationRequest
object
The data associated with the resource.
1 property 1 required
Errors
object
1 property
CreateRelatedRequirementRequest
object
The data associated with the resource.
1 property 1 required
GetRelatedRequirementResponse
object
The data associated with the resource.
1 property 1 required
GetComplianceRegulationsResponse
object
The data associated with the resource.
2 properties 2 required
UpdateComplianceMappingRequest
object
The data associated with the resource.
1 property 1 required
GetComplianceRequirementsResponseWithIncludes
object
The data associated with the resource.
3 properties 2 required
GetComplianceRequirementResponseWithIncludes
object
The data associated with the resource.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wegalvanize-compliance-maps-api-openapi.yml Raw ↑

Other APIs Wegalvanize publishes across the network.

Wegalvanize Actions API
Wegalvanize Activities API
Wegalvanize Analyses API
Wegalvanize Attachments API
Wegalvanize Collaborators API
Wegalvanize Collections API
Wegalvanize Control performance schedules API
Wegalvanize Control test plans API
Wegalvanize Control tests API
Wegalvanize Controls API
Wegalvanize Custom attributes API
Wegalvanize Entities API
Where this information came from

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