Skip to content
AveraAveraAvera Documentation

Overview

Lifecycles & signatures 1.0.0

Section titled “Lifecycles & signatures 1.0.0”

The lifecycles & signatures surface of the Avera REST API: Lifecycles · Endorsements · Signatures · Signing credentials · Signing credentials (admin).

Information

  • License: Proprietary
  • OpenAPI version: 3.1.0

Lifecycles

Section titled “Lifecycles”
POST
/api/v1/projects/{projectId}/lifecycles
POST
/api/v1/projects/{projectId}/lifecycles/{lifecycleId}/states
POST
/api/v1/projects/{projectId}/lifecycles/{lifecycleId}/transitions
DELETE
/api/v1/projects/{projectId}/lifecycles/states/{stateId}
DELETE
/api/v1/projects/{projectId}/lifecycles/transitions/{transitionId}
DELETE
/api/v1/projects/{projectId}/lifecycles/{lifecycleId}
GET
/api/v1/projects/{projectId}/lifecycles/{lifecycleId}
GET
/api/v1/projects/{projectId}/lifecycles
PUT
/api/v1/projects/{projectId}/lifecycles/{lifecycleId}/initial-state
PUT
/api/v1/projects/{projectId}/lifecycles/states/{stateId}
PUT
/api/v1/projects/{projectId}/lifecycles/transitions/{transitionId}/policy

Endorsements

Section titled “Endorsements”
POST
/api/v1/items/{itemId}/transitions/{transitionId}/endorsements
GET
/api/v1/items/{itemId}/transitions/{transitionId}/endorsements

Signatures

Section titled “Signatures”
POST
/api/v1/signatures
GET
/api/v1/items/{itemId}/signatures
POST
/api/v1/signatures/{id}/revoke
POST
/api/v1/signatures/sign
POST
/api/v1/signatures/{id}/verify

Signing credentials

Section titled “Signing credentials”
POST
/api/v1/signing-credentials
GET
/api/v1/signing-credentials/me

Signing credentials (admin)

Section titled “Signing credentials (admin)”
POST
/api/v1/tenants/{tenantId}/users/{userId}/signing-credentials/reset

Authentication

Section titled “Authentication”

bearerAuth

Section titled “bearerAuth”

Every request carries a bearer token: the session token issued at sign-in, or an OAuth 2.1 access token from a connector grant. HTTP basic is disabled (see SecurityConfig), and the requirement is declared once here rather than on each operation, since it is the same for the whole API.

Security scheme type: http

Bearer format: JWT