Automate Maif Otoroshi Admin

What Maif Otoroshi Admin is

Admin API of the Otoroshi reverse proxy

API host: otoroshi-api.oto.tools

What HumDay can do in Maif Otoroshi Admin

62 documented operations change something in Maif Otoroshi Admin.

• POSTCreate a new service group/api/groups
• POSTCreate a new script/api/scripts
• POSTCreate a new service descriptor/api/services
• POSTCreate a new data exporter config/api/data-exporter-configs
• POSTCreate a new data exporter configs/api/data-exporter-configs/_bulk
• POSTCreate one global auth./api/auths
• POSTImport the full state of Otoroshi as a file/api/import
• POSTCreate one global JWT verifiers/api/verifiers
• POSTCreate one certificate/api/certificates
• POSTCreate one validation authorities/api/client-validators
• POSTCreate a new api key for a group/api/groups/{groupId}/apikeys
• POSTCreate a new api key for a service/api/services/{serviceId}/apikeys
• PATCHUpdate the global configuration with a diff/api/globalconfig
• PUTUpdate the global configuration/api/globalconfig
• POSTAdd a target to a service descriptor/api/services/{serviceId}/targets
• POSTCreate a service descriptor error template/api/services/{serviceId}/template
• POSTImport the full state of Otoroshi/api/otoroshi.json
• POSTCompile a script/api/scripts/_compile
• POSTStop the Snow Monkey/api/snowmonkey/_stop
• POSTStart the Snow Monkey/api/snowmonkey/_start
• PATCHUpdate current Snow Monkey config/api/snowmonkey/config
• PUTUpdate current Snow Monkey config/api/snowmonkey/config
• DELETEReset Snow Monkey Outages for the day/api/snowmonkey/outages
• DELETEDelete one global auth./api/auths/{id}
• PATCHUpdate one global auth./api/auths/{id}
• PUTUpdate one global auth./api/auths/{id}
• DELETEDelete a data exporter config/api/data-exporter-configs/_bulk
• PATCHUpdate a data exporter configs with a diff/api/data-exporter-configs/_bulk
• PUTUpdate a data exporter configs/api/data-exporter-configs/_bulk
• DELETEDelete one certificate by id/api/certificates/{id}
• PATCHUpdate one certificate by id/api/certificates/{id}
• PUTUpdate one certificate by id/api/certificates/{id}
• DELETEDelete a script/api/scripts/{scriptId}
• PATCHUpdate a script with a diff/api/scripts/{scriptId}
• PUTUpdate a script/api/scripts/{scriptId}
• DELETEDelete a service descriptor/api/services/{serviceId}
• PATCHUpdate a service descriptor with a diff/api/services/{serviceId}
• PUTUpdate a service descriptor/api/services/{serviceId}
• DELETEDelete one validation authorities by id/api/client-validators/{id}
• PATCHUpdate one validation authorities by id/api/client-validators/{id}
• PUTUpdate one validation authorities by id/api/client-validators/{id}
• DELETEDelete one global JWT verifiers/api/verifiers/{verifierId}
• PATCHUpdate one global JWT verifiers/api/verifiers/{verifierId}
• PUTUpdate one global JWT verifiers/api/verifiers/{verifierId}
• DELETEDelete a service group/api/groups/{serviceGroupId}
• PATCHUpdate a service group with a diff/api/groups/{serviceGroupId}
• PUTUpdate a service group/api/groups/{serviceGroupId}
• DELETEDelete a data exporter config/api/data-exporter-configs/{dataExporterConfigId}
• PATCHUpdate a data exporter config with a diff/api/data-exporter-configs/{dataExporterConfigId}
• PUTUpdate a data exporter config/api/data-exporter-configs/{dataExporterConfigId}
• DELETEDelete a service descriptor target/api/services/{serviceId}/targets
• PATCHUpdate a service descriptor targets/api/services/{serviceId}/targets
• DELETEDelete a service descriptor error template/api/services/{serviceId}/template
• PUTUpdate an error template to a service descriptor/api/services/{serviceId}/template
• DELETEDelete an api key/api/groups/{groupId}/apikeys/{clientId}
• PATCHUpdate an api key with a diff/api/groups/{groupId}/apikeys/{clientId}
• PUTUpdate an api key/api/groups/{groupId}/apikeys/{clientId}
• DELETEDelete an api key/api/services/{serviceId}/apikeys/{clientId}
• PATCHUpdate an api key with a diff/api/services/{serviceId}/apikeys/{clientId}
• PUTUpdate an api key/api/services/{serviceId}/apikeys/{clientId}
• DELETEReset the quota state of an api key/api/groups/{groupId}/apikeys/{clientId}/quotas
• DELETEReset the quota state of an api key/api/services/{serviceId}/apikeys/{clientId}/quotas

What HumDay can read from Maif Otoroshi Admin

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

• GETGet a template of an Otoroshi service group/new/group
• GETGet a template of an Otoroshi Api Key/new/apikey
• GETGet a template of an Otoroshi service descriptor/new/service
• GETGet all environments/lines
• GETReturn current Otoroshi health/health
• GETGet global otoroshi stats/api/live
• GETGet all global auth. module configs/api/auths
• GETGet all service groups/api/groups
• GETGet all api keys/api/apikeys
• GETGet all scripts/api/scripts
• GETGet all services/api/services
• GETGet all global JWT verifiers/api/verifiers
• GETGet all certificates/api/certificates
• GETGet the full configuration of Otoroshi/api/globalconfig
• GETGet all validation authoritiess/api/client-validators
• GETGet all data exporter configs/api/data-exporter-configs
• GETExport the full state of Otoroshi/api/otoroshi.json
• GETGet current Snow Monkey config/api/snowmonkey/config
• GETGet all current Snow Monkey ourages/api/snowmonkey/outages
• GETGet live feed of otoroshi stats/api/live/{id}
• GETGet one global auth. module configs/api/auths/{id}
• GETGet all data exporter configs/api/data-exporter-configs/_template
• GETGet one certificate by id/api/certificates/{id}
• GETGet all services for an environment/lines/{line}/services
• GETGet a script/api/scripts/{scriptId}
• GETGet a service descriptor/api/services/{serviceId}
• GETGet one validation authorities by id/api/client-validators/{id}
• GETGet one global JWT verifiers/api/verifiers/{verifierId}
• GETGet a service group/api/groups/{serviceGroupId}
• GETGet a data exporter config/api/data-exporter-configs/{dataExporterConfigId}
• GETGet all api keys for the group of a service/api/groups/{groupId}/apikeys
• GETGet all api keys for the group of a service/api/services/{serviceId}/apikeys
• GETGet a service descriptor targets/api/services/{serviceId}/targets
• GETGet a service descriptor error template/api/services/{serviceId}/template
• GETGet all services descriptor for a group/api/groups/{serviceGroupId}/services
• GETGet an api key/api/groups/{groupId}/apikeys/{clientId}
• GETGet an api key/api/services/{serviceId}/apikeys/{clientId}
• GETGet the group of an api key/api/services/{serviceId}/apikeys/{clientId}/group

How automating Maif Otoroshi Admin 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 Maif Otoroshi Admin account.
4. Grant access, then go live. You approve the specific Maif Otoroshi Admin operations it may use — and only those.

Automate Maif Otoroshi Admin 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

• Developer tools

Questions about Maif Otoroshi Admin automation

Can HumDay connect to Maif Otoroshi Admin?

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

Do I need to write code to automate Maif Otoroshi Admin?

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 Maif Otoroshi Admin account.

What can HumDay do in Maif Otoroshi Admin?

62 of the 102 documented operations change something in Maif Otoroshi Admin, and 40 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Maif Otoroshi Admin 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 Maif Otoroshi Admin is held behind that approval.

Where this came from

The operations above are read from a published API description for Maif Otoroshi Admin at raw.githubusercontent.com/MAIF/otoroshi/master/docs/manual/code/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-30.