Automate SwaggerHub Registry
HumDay reads SwaggerHub Registry’s own published API description and derives 86 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What SwaggerHub Registry is
# Overview Use SwaggerHub Registry API to access, manage, and update the following resources in SwaggerHub, bypassing the web interface: * APIs * Domains * Integrations * Projects * Templates SwaggerHub also provides the [User Management API](https://app.swaggerhub.com/apis-docs/swagger-hub/user-management-api/) to get information about organizations and manage organization members. # Base URL Use
API host: api.swaggerhub.com
What HumDay can do in SwaggerHub Registry
52 documented operations change something in SwaggerHub Registry.
- POSTAdd a new comment
/apis/{owner}/{api}/{version}/comments - POSTAdd a new comment
/domains/{owner}/{domain}/{version}/comments - POSTCreate a project in an organization
/projects/{owner} - POSTCreate or update an API
/apis/{owner}/{api} - POSTCreate or update a domain
/domains/{owner}/{domain} - POSTCreate a new API version
/apis/{owner}/{api}/{version}/clone - POSTCreate or update a template
/templates/{owner}/{templateId} - POSTCreate a new domain version
/domains/{owner}/{domain}/{version}/clone - POSTReply to a comment
/apis/{owner}/{api}/{version}/comments/{comment}/replies - POSTReply to a comment
/domains/{owner}/{domain}/{version}/comments/{comment}/replies - PUTUpdate a project's members list
/projects/{owner}/{projectId}/members - POSTUpdate the list of comments for a template
/templates/{owner}/{templateId}/{version}/comments/batch - DELETEDelete a comment
/apis/{owner}/{api}/{version}/comments/{comment} - PATCHUpdate a comment
/apis/{owner}/{api}/{version}/comments/{comment} - DELETEDelete an API
/apis/{owner}/{api} - DELETEDelete a comment
/domains/{owner}/{domain}/{version}/comments/{comment} - PATCHUpdate a comment
/domains/{owner}/{domain}/{version}/comments/{comment} - DELETEDelete a domain
/domains/{owner}/{domain} - DELETEDelete a comment reply
/apis/{owner}/{api}/{version}/comments/{comment}/replies/{reply} - PATCHUpdate a comment reply
/apis/{owner}/{api}/{version}/comments/{comment}/replies/{reply} - DELETEDelete a project
/projects/{owner}/{projectId} - PUTUpdate a project
/projects/{owner}/{projectId} - DELETEDelete a template
/templates/{owner}/{templateId} - DELETEDelete a comment reply
/domains/{owner}/{domain}/{version}/comments/{comment}/replies/{reply} - PATCHUpdate a comment reply
/domains/{owner}/{domain}/{version}/comments/{comment}/replies/{reply} - POSTCreate an integration for the specified API and version
/apis/{owner}/{api}/{version}/integrations - POSTCreate a fork for a template
/templates/{owner}/{templateId}/{version}/fork - POSTRename an API
/apis/{owner}/{api}/rename - POSTRename a domain
/domains/{owner}/{domain}/rename - PUTAdd an API or domain to a project
/projects/{owner}/{projectId}/{specType}/{name} - POSTRename a template
/templates/{owner}/{templateId}/rename - POSTBulk update comments
/apis/{owner}/{api}/{version}/comments/batch - DELETEDelete an API version
/apis/{owner}/{api}/{version} - POSTBulk update comments
/domains/{owner}/{domain}/{version}/comments/batch - DELETEDelete a domain version
/domains/{owner}/{domain}/{version} - PUTSet the default API version
/apis/{owner}/{api}/settings/default - DELETEDelete a particular version of a template
/templates/{owner}/{templateId}/{version} - PUTSet the default version for a domain
/domains/{owner}/{domain}/settings/default - PUTResolve or reopen a comment
/apis/{owner}/{api}/{version}/comments/{comment}/status/{status} - POSTFork an API
/apis/{owner}/{api}/{version}/fork - PUTResolve or reopen a comment
/domains/{owner}/{domain}/{version}/comments/{comment}/status/{status} - POSTFork a domain
/domains/{owner}/{domain}/{version}/fork - PUTSet the visibility (public or private) of an API version
/apis/{owner}/{api}/{version}/settings/private - PUTPublish or unpublish an API version
/apis/{owner}/{api}/{version}/settings/lifecycle - PUTSet the visibility (public or private) of a domain version
/domains/{owner}/{domain}/{version}/settings/private - PUTPublish or unpublish a domain version
/domains/{owner}/{domain}/{version}/settings/lifecycle - PUTUpdate visibility settings for a template
/templates/{owner}/{templateId}/{version}/settings/private - PUTUpdate lifecycle settings for a template
/templates/{owner}/{templateId}/{version}/settings/lifecycle - DELETEDelete an integration
/apis/{owner}/{api}/{version}/integrations/{integrationId} - PATCHPartially update integration settings
/apis/{owner}/{api}/{version}/integrations/{integrationId} - PUTUpdate integration settings
/apis/{owner}/{api}/{version}/integrations/{integrationId} - POSTRun an integration
/apis/{owner}/{api}/{version}/integrations/{integrationId}/execute
What HumDay can read from SwaggerHub Registry
These are the operations a schedule or a trigger can watch.
- GETSearch APIs
/apis - GETRetrieve a list of currently defined APIs, domains, and templates in APIs.json format
/specs - GETSearch domains
/domains - GETGet all projects that a user has access to
/projects - GETRetrieve a list of templates for an owner
/templates - GETGet a list of APIs of the specified owner
/apis/{owner} - GETGet a list of domains of the specified owner
/domains/{owner} - GETGet a list of API versions
/apis/{owner}/{api} - GETGet a list of domain versions
/domains/{owner}/{domain} - GETGet all projects of an organization
/projects/{owner} - GETReturn the list of comments for a template
/templates/{owner}/{templateId}/{version}/comments - GETGet project information
/projects/{owner}/{projectId} - GETRetrieve an APIs.json listing for all template versions for an owner and template
/templates/{owner}/{templateId} - GETGet comments for the specified API version
/apis/{owner}/{api}/{version}/comments - GETGet comments for the specified domain version
/domains/{owner}/{domain}/{version}/comments - GETGet project members
/projects/{owner}/{projectId}/members - GETGet the OpenAPI definition of the specified API version
/apis/{owner}/{api}/{version} - GETGet the OpenAPI definition of the specified domain version
/domains/{owner}/{domain}/{version} - GETGet the default version of an API
/apis/{owner}/{api}/settings/default - GETRetrieve a template definition
/templates/{owner}/{templateId}/{version} - GETGet the default version of a domain
/domains/{owner}/{domain}/settings/default - GETGet all integrations configured for the specified API version
/apis/{owner}/{api}/{version}/integrations - GETRetrieve the standardization errors for a given API definition
/apis/{owner}/{api}/{version}/standardization - GETGet the OpenAPI definition for the specified API version in JSON format
/apis/{owner}/{api}/{version}/swagger.json - GETGet the OpenAPI definition for the specified API version in YAML format
/apis/{owner}/{api}/{version}/swagger.yaml - GETGet the visibility (public or private) of API version
/apis/{owner}/{api}/{version}/settings/private - GETGet the OpenAPI definition for the specified domain version in JSON format
/domains/{owner}/{domain}/{version}/domain.json - GETGet the OpenAPI definition for the specified domain version in YAML format
/domains/{owner}/{domain}/{version}/domain.yaml - GETGet the published status for the specified API and version
/apis/{owner}/{api}/{version}/settings/lifecycle - GETGet the visibility (public or private) of a domain version
/domains/{owner}/{domain}/{version}/settings/private - GETGet the published status for the specified domain and version
/domains/{owner}/{domain}/{version}/settings/lifecycle - GETRetrieve visibility settings for a template
/templates/{owner}/{templateId}/{version}/settings/private - GETRetrieve lifecycle settings for a template
/templates/{owner}/{templateId}/{version}/settings/lifecycle - GETGet integration settings
/apis/{owner}/{api}/{version}/integrations/{integrationId}
How automating SwaggerHub Registry works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live SwaggerHub Registry account.
- Grant access, then go live. You approve the specific SwaggerHub Registry operations it may use — and only those.
Popular SwaggerHub Registry integrations
Connect SwaggerHub Registry to the tools people pair it with most.
- SwaggerHub Registry and OData for namespace microsoft.graphintegration
- SwaggerHub Registry and Cloudflareintegration
- SwaggerHub Registry and NetBoxintegration
- SwaggerHub Registry and GitHubintegration
- SwaggerHub Registry and Mistintegration
- SwaggerHub Registry and Loket.nlintegration
- SwaggerHub Registry and Atlassian The Jira Cloud platformintegration
- SwaggerHub Registry and Magento B2Bintegration
- SwaggerHub Registry and Stripeintegration
- SwaggerHub Registry and Zuora Reference Billingintegration
- SwaggerHub Registry and bunqintegration
- SwaggerHub Registry and DocuSignintegration
Automate SwaggerHub Registry with these
- 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
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about SwaggerHub Registry automation
- Can HumDay connect to SwaggerHub Registry?
- Yes. HumDay reads SwaggerHub Registry's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 86 operations are documented.
- Do I need to write code to automate SwaggerHub 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 SwaggerHub Registry account.
- What can HumDay do in SwaggerHub Registry?
- 52 of the 86 documented operations change something in SwaggerHub Registry, and 34 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my SwaggerHub 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 SwaggerHub Registry is held behind that approval.
Where this came from
The operations above are read from a published API description for SwaggerHub Registry at api.swaggerhub.com/apis/swagger-hub/registry-api/1.0.66. Descriptions are the provider’s own words, not ours. Last published 2023-02-17.