Automate Apigee Registry

What Apigee Registry is

The Registry service allows teams to manage descriptions of APIs.

API host: apigee.local

What HumDay can do in Apigee Registry

21 documented operations change something in Apigee Registry.

• POSTCreateApi creates a specified API./v1/projects/{project}/locations/{location}/apis
• POSTCreateArtifact creates a specified artifact./v1/projects/{project}/locations/{location}/artifacts
• POSTCreateApiVersion creates a specified version./v1/projects/{project}/locations/{location}/apis/{api}/versions
• POSTCreateApiDeployment creates a specified deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments
• DELETEDeleteApi removes a specified API and all of the resources that it owns./v1/projects/{project}/locations/{location}/apis/{api}
• PATCHUpdateApi can be used to modify a specified API./v1/projects/{project}/locations/{location}/apis/{api}
• DELETEDeleteArtifact removes a specified artifact./v1/projects/{project}/locations/{location}/artifacts/{artifact}
• PUTReplaceArtifact can be used to replace a specified artifact./v1/projects/{project}/locations/{location}/artifacts/{artifact}
• POSTTagApiDeploymentRevision adds a tag to a specified revision of a deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}:tagRevision
• POSTCreateApiSpec creates a specified spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs
• DELETEDeleteApiVersion removes a specified version and all of the resources that it owns./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}
• PATCHUpdateApiVersion can be used to modify a specified version./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}
• DELETEDeleteApiDeployment removes a specified deployment, all revisions, and all child resources (e.g./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}
• PATCHUpdateApiDeployment can be used to modify a specified deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}
• POSTRollbackApiDeployment sets the current revision to a specified prior revision./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}:rollback
• POSTTagApiSpecRevision adds a tag to a specified revision of a spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}:tagRevision
• DELETEDeleteApiDeploymentRevision deletes a revision of a deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}:deleteRevision
• DELETEDeleteApiSpec removes a specified spec, all revisions, and all child resources (e.g./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}
• PATCHUpdateApiSpec can be used to modify a specified spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}
• POSTRollbackApiSpec sets the current revision to a specified prior revision./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}:rollback
• DELETEDeleteApiSpecRevision deletes a revision of a spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}:deleteRevision

What HumDay can read from Apigee Registry

These are the operations a schedule or a trigger can watch.

• GETListApis returns matching APIs./v1/projects/{project}/locations/{location}/apis
• GETListArtifacts returns matching artifacts./v1/projects/{project}/locations/{location}/artifacts
• GETGetApi returns a specified API./v1/projects/{project}/locations/{location}/apis/{api}
• GETGetArtifact returns a specified artifact./v1/projects/{project}/locations/{location}/artifacts/{artifact}
• GETGetArtifactContents returns the contents of a specified artifact./v1/projects/{project}/locations/{location}/artifacts/{artifact}:getContents
• GETListApiVersions returns matching versions./v1/projects/{project}/locations/{location}/apis/{api}/versions
• GETListApiDeployments returns matching deployments./v1/projects/{project}/locations/{location}/apis/{api}/deployments
• GETGetApiVersion returns a specified version./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}
• GETGetApiDeployment returns a specified deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}
• GETListApiDeploymentRevisions lists all revisions of a deployment./v1/projects/{project}/locations/{location}/apis/{api}/deployments/{deployment}:listRevisions
• GETListApiSpecs returns matching specs./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs
• GETGetApiSpec returns a specified spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}
• GETGetApiSpecContents returns the contents of a specified spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}:getContents
• GETListApiSpecRevisions lists all revisions of a spec./v1/projects/{project}/locations/{location}/apis/{api}/versions/{version}/specs/{spec}:listRevisions

How automating Apigee Registry works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Apigee Registry account.
4. Grant access, then go live. You approve the specific Apigee Registry operations it may use — and only those.

Automate Apigee Registry with these

• Apigee Marketcheck71 operations
• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Gitea .321 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations

Categories

• Developer tools

Questions about Apigee Registry automation

Can HumDay connect to Apigee Registry?

Yes. HumDay reads Apigee Registry's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 35 operations are documented.

Do I need to write code to automate Apigee Registry?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Apigee Registry account.

What can HumDay do in Apigee Registry?

21 of the 35 documented operations change something in Apigee Registry, and 14 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Apigee Registry account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Apigee Registry is held behind that approval.

Where this came from

The operations above are read from a published API description for Apigee Registry at raw.githubusercontent.com/apigee/registry/main/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.