capabilities.work

Registry Catalog an API Version

A 4-step recipe with Apigee. We can help you get access.

Recipe · 4 steps

Registry Catalog an API Version

with Apigee · Public API Lifecycle Management

Create an API, version, spec, and deployment in the Registry.

  1. Create the API entry that groups the version, spec, and deployment.
  2. Add a version to the API in the Registry.
  3. Attach a specification document to the version with a filename and MIME type.
  4. Record an API deployment that ties the cataloged API to a runtime endpoint.
What you'll need to have ready
  • projectId: Google Cloud project id hosting the Registry.
  • locationId: Google Cloud location of the Registry resources.
  • apiId: Id to assign to the new API.
  • apiDisplayName: Display name for the API.
  • versionId: Id to assign to the new version.
  • versionDisplayName: Display name for the version.
  • specId: Id to assign to the new spec.
  • specFilename: Filename for the spec document.
  • mimeType: MIME type of the spec content.
  • deploymentId: Id to assign to the new deployment record.
  • endpointUri: Runtime endpoint URI for the deployment.
For your developer

Arazzo workflow apigee:catalog-registry-version, 4 operations: createApi → createApiVersion → createApiSpec → createApiDeployment. Specs on APIs.io.

More recipes with Apigee

Set Up Analytics Export and Read StatsOnboard an App GroupAPI Hub Catalog and LintDecommission an API ProxyAPI Hub Discover and SearchTear Down an EnvironmentGrant an App Access to a New ProductIntegration Auth SetupIntegration Execution MonitorPublish and Execute an Integration