Automate OpenAPI space
HumDay reads OpenAPI space’s own published API description and derives 15 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 OpenAPI space is
This is the API for OpenAPI space.
API host: openapi.space
What HumDay can do in OpenAPI space
10 documented operations change something in OpenAPI space.
- POSTCheck whether or not you are authenticated
/auth/ping - POSTLog in to OpenAPI space
/auth/login - POSTLog out from OpenAPI space
/auth/logout - POSTRegister to OpenAPI space
/auth/register - POSTLog in to OpenAPI space using an APInf account
/auth/login/apinf - POSTLog in to OpenAPI space using an APInf authentication token
/auth/login/apinf_token - DELETEDeletes the specified API
/apis/{owner}/{api} - POSTSaves the provided Swagger definition
/apis/{owner}/{api} - DELETEDeletes a particular version of the specified API
/apis/{owner}/{api}/{version} - POSTPublish a particular version of the specified API
/apis/{owner}/{api}/{version}
What HumDay can read from OpenAPI space
These are the operations a schedule or a trigger can watch.
- GETRetrieves a list of currently defined APIs in API meta list format.
/apis - GETRetrieves an API meta listing of all APIs defined for this owner
/apis/{owner} - GETRetrieves an API meta listing for all API versions for this owner and API
/apis/{owner}/{api} - GETRetrieves the Swagger definition for the specified API and version in JSON format
/apis/{owner}/{api}/{version}/swagger.json - GETRetrieves the Swagger definition for the specified API and version in YAML format
/apis/{owner}/{api}/{version}/swagger.yaml
How automating OpenAPI space 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 OpenAPI space account.
- Grant access, then go live. You approve the specific OpenAPI space operations it may use — and only those.
Automate OpenAPI space 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 OpenAPI space automation
- Can HumDay connect to OpenAPI space?
- Yes. HumDay reads OpenAPI space's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 15 operations are documented.
- Do I need to write code to automate OpenAPI space?
- 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 OpenAPI space account.
- What can HumDay do in OpenAPI space?
- 10 of the 15 documented operations change something in OpenAPI space, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my OpenAPI space 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 OpenAPI space is held behind that approval.
Where this came from
The operations above are read from a published API description for OpenAPI space at openapi.space/api/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2018-06-20.