Skip to content

Introduction to the Registry Service REST API (1.0)

Registry Service REST APIs to use with Flexnet Operations. Almost all of these APIs will require you to pass the tenant-id using x-publisherid request header.

Languages
Servers
Mock server
https://fnoapi.redocly.app/_mock/apis/rest/registry-service/softwarecontainerdelivery
Replace {siteID} with your FlexNet Operations instance. Replace {domainExtension} with the extension for your FlexNet Operations instance, such as com, eu, etc.
https://{siteID}.flexnetoperations.{domainExtension}/registry/api/v1

Software Container Delivery Public APIs

The Software Container Delivery REST API enables producers who distribute containerized applications using the Revenera registry to manage their projects directly, without using the Docker or Helm command-line interface (CLI). This allows producers to incorporate relevant functionality into their own portal implementations.

Operations

auth-controller

Auth Controller

Operations

Get JWT Token for a User

Request

When calling the Software Container Delivery REST API, a producer user must authenticate themselves, using the "/authenticate" endpoint. The FlexNet Operations producers pass their credentials to the "/authenticate" endpoint, which creates a JSON Web Token (JWT) that can be used to authorize access to any endpoint of the Software Container Delivery REST API. Credentials are a Base64-encoded combination of the producer's user name and password separated by a colon (:).

Headers
Authorizationstringrequired

Authorization

curl -i -X GET \
  https://fnoapi.redocly.app/_mock/apis/rest/registry-service/softwarecontainerdelivery/api/v1/authenticate \
  -H 'Authorization: string'

Responses

All OK

Bodyapplication/json
dataobject
statusCodeinteger(int32)
statusMessagestring
Response
application/json
{ "data": {}, "statusCode": 0, "statusMessage": "string" }