OpenVibe.Services API
Generated at from
openvibe-contracts v0.114.0 and
openvibe-sdk v0.35.1.
Server https://openvibe.services. 9 routes performing 3 capabilities. OpenAPI 3.1 document.
GET /api/v1/apps/{app}/releases
Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything).
- Capabilities
- services.release.read
- Visibility
- public
- Parameters
app(path, required)
- Response
application/jsonservices.release-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.read</strong> (public): Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything). Drafts are never returned. Public; no token needed.</p>POST /api/v1/apps/{app}/releases
An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional rep
- Capabilities
- services.release.manage
- Visibility
- public
- Parameters
app(path, required)
- Request body
application/jsonservices.release-manage-request@1- Response
application/jsonservices.release-manage-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.manage</strong> (public): An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the console at openvibe.services with their project role instead. Trust tiers are not part of this capability (staff metadata only).</p>GET /api/v1/apps/{app}/trust
Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything).
- Capabilities
- services.release.read
- Visibility
- public
- Parameters
app(path, required)
- Response
application/jsonservices.release-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.read</strong> (public): Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything). Drafts are never returned. Public; no token needed.</p>GET /api/v1/releases/{id}
Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything).
- Capabilities
- services.release.read
- Visibility
- public
- Parameters
id(path, required)
- Response
application/jsonservices.release-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.read</strong> (public): Read public release metadata: an app's published, deprecated and revoked releases with their manifests, compatibility ranges and the app's trust tier (metadata only; it never grants anything). Drafts are never returned. Public; no token needed.</p>POST /api/v1/releases/{id}/deprecate
An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional rep
- Capabilities
- services.release.manage
- Visibility
- public
- Parameters
id(path, required)
- Request body
application/jsonservices.release-manage-request@1- Response
application/jsonservices.release-manage-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.manage</strong> (public): An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the console at openvibe.services with their project role instead. Trust tiers are not part of this capability (staff metadata only).</p>POST /api/v1/releases/{id}/publish
An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional rep
- Capabilities
- services.release.manage
- Visibility
- public
- Parameters
id(path, required)
- Request body
application/jsonservices.release-manage-request@1- Response
application/jsonservices.release-manage-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.manage</strong> (public): An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the console at openvibe.services with their project role instead. Trust tiers are not part of this capability (staff metadata only).</p>POST /api/v1/releases/{id}/revoke
An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional rep
- Capabilities
- services.release.manage
- Visibility
- public
- Parameters
id(path, required)
- Request body
application/jsonservices.release-manage-request@1- Response
application/jsonservices.release-manage-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.release.manage</strong> (public): An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the console at openvibe.services with their project role instead. Trust tiers are not part of this capability (staff metadata only).</p>GET /api/v1/resources
Services' merged resource index over every authority that serves one (ADR-048), readable by a first-party service token holding the capability or by a person's user token scoped to a project they own
- Capabilities
- services.resource.read
- Visibility
- first-party
- Response
application/jsoncommon.resource-list-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>services.resource.read</strong> (first-party): Services' merged resource index over every authority that serves one (ADR-048), readable by a first-party service token holding the capability or by a person's user token scoped to a project they own or belong to (one project per request).</p>GET /api/v1/resources/{ovrn}
Services' merged resource index over every authority that serves one (ADR-048), readable by a first-party service token holding the capability or by a person's user token scoped to a project they own
- Capabilities
- services.resource.read
- Visibility
- first-party
- Parameters
ovrn(path, required)
- Response
application/jsoncommon.resource-list-result@1- Errors
- errors.problem@1 (application/problem+json)