Wegalvanize Mitigations API
> **Note —**Only controls in projects that have an `"active"` state can be accessed using the API.
Wegalvanize Mitigations API is one of 69 APIs that Wegalvanize publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Mitigations. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.2, at version 1.1.0.
Requests are made against a single base URL, {protocol}://{server}/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Wegalvanize Mitigations 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 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Note — Only controls in projects that have an "active" state can be accessed using the API.
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Error (5 properties), UpdateMitigationRequest (1 property), GetMitigationResponse (1 property), Errors (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wegalvanize 12
Other APIs Wegalvanize publishes across the network.