API Hub Catalog and Lint
A 5-step recipe with Apigee. We can help you get access.
Recipe · 5 steps
API Hub Catalog and Lint
with Apigee · Public API Lifecycle Management
Create an API, version, and spec in API Hub, then lint and inspect the spec.
- Create the API resource that will hold versions and specs in API Hub.
- Add a version to the API representing a specific release.
- Attach a machine-readable specification to the version with strict parsing.
- Trigger a lint of the spec, which returns a long-running operation while validation runs.
- Read the spec back to surface the lint response recorded against it.
What you'll need to have ready
- projectId: Google Cloud project id hosting the API Hub.
- locationId: Google Cloud location of the API Hub resources.
- apiId: Id to assign to the new API resource.
- apiDisplayName: Display name for the API.
- versionId: Id to assign to the new API version.
- versionDisplayName: Display name for the version.
- specId: Id to assign to the new spec.
- specDisplayName: Display name for the spec.
For your developer
Arazzo workflow apigee:catalog-and-lint-api, 5 operations: createApi → createApiVersion → createApiSpec → lintApiSpec → getApiSpec. Specs on APIs.io.