Wegalvanize Project types API
Project types define the structure of a project or framework, including the terminology used in the project or framework. Updates to project types apply toall active projects, archived projects, temporarily deleted projects, and frameworks associated with the project type.Each project type has an associated workflow: Workplan (`procedure`) or Internal Control (`control`). Workflows define the components available in a projector framework. The attributes `narrative_terms`, `control_test_terms`, and `test_plan_terms` are not available for a Workplan (`procedure`) workflow.When creating a new project type, only the basic defining attributes are available. After creating the project type default customizable terms and togglesare returned and available on PATCH requests for update.
Wegalvanize Project types API is one of 69 APIs that Wegalvanize publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Project Types. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 5 operations across 2 paths, and defines 6 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Wegalvanize Project types 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 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Project types define the structure of a project or framework, including the terminology used in the project or framework.
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Error (5 properties), GetProjectTypesResponse (2 properties), CreateProjectTypeRequest (1 property), GetProjectTypeResponse (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.
This is an independent, third-party profile of Wegalvanize Project types 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.