Moogsoft · Authentication Profile
Moogsoft Authentication
Authentication
Moogsoft secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.
AIOpsIncident ManagementObservabilityAlertingEvent ManagementAnomaly DetectionCorrelationOn-CallMonitoringIT OperationsDevOpsSRE
Methods: apiKey
Schemes: 1
OAuth flows:
API key in: header
Security Schemes
ApiKeyAuth apiKey
· in: header (apiKey)
Source
Authentication Profile
generated: '2026-08-29'
method: searched
source: https://api.docs.moogsoft.com/docs/latest/branches/main/8ae0406b4fb96-authentication, https://api.docs.moogsoft.com/docs/latest/branches/main/6553f9391961d-manage-api-keys,
https://api.docs.moogsoft.com/docs/latest/branches/main/b16f03ec715a2-user-roles-and-permissions, https://api.docs.moogsoft.com/docs/latest/branches/main/f86595eca2b25-request-requirements,
and openapi/ (17 contracts)
summary:
types:
- apiKey
api_key_in:
- header
schemes:
- name: ApiKeyAuth
type: apiKey
in: header
parameter: apiKey
description: API Key for accessing Alerts/Incidents API
sources:
- openapi/moogsoft-alerts-incidents-openapi.yaml
- openapi/moogsoft-azure-service-openapi.yaml
- openapi/moogsoft-byo-api-service-openapi.yaml
- openapi/moogsoft-cloudwatch-service-openapi.yaml
- openapi/moogsoft-collectors-openapi.yaml
- openapi/moogsoft-config-openapi.yaml
- openapi/moogsoft-events-integration-openapi.yaml
- openapi/moogsoft-incident-responder-openapi.yaml
- openapi/moogsoft-metrics-integration-openapi.yaml
- openapi/moogsoft-pagerduty-service-openapi.yaml
- openapi/moogsoft-probable-rootcause-openapi.yaml
- openapi/moogsoft-similar-incidents-openapi.yaml
- openapi/moogsoft-ui-services-openapi.yaml
- openapi/moogsoft-user-management-openapi.yaml
- openapi/moogsoft-webhook-service-v2-openapi.yaml
- openapi/moogsoft-workflow-engine-service-openapi.yaml
docs: https://api.docs.moogsoft.com/docs/latest/branches/main/8ae0406b4fb96-authentication
model:
primary:
style: API key in a request header
header: apiKey
example: 'curl https://api.moogsoft.ai/v1/integrations/events -H ''Content-Type: application/json''
-H ''apiKey: <your-API-key>'''
declared_in: components.securitySchemes.ApiKeyAuth on all 17 contracts
alternative:
style: credentials embedded in the URL
form: https://<username>:<api_key>@api.moogsoft.ai/...
note: Documented on the Authentication page as "basic token authentication". A bearer-token variant
is present in the docs source but commented out and therefore not offered.
oauth2:
supported_for_inbound_api: false
note: OAuth 2.0 appears in Moogsoft only for credentials Moogsoft uses to call OUT — webhook endpoint
auth (password grant, exclusive since 2024-11-18) and the external credential store (client credentials,
added 2025-04-29). There are no inbound OAuth scopes, so no scopes/ artifact is emitted.
console_sso:
issuer: https://auth.moogsoft.ai/
platform: Auth0
discovery: well-known/moogsoft-auth-openid-configuration.json
note: Governs sign-in to app.moogsoft.ai only. SAML/SSO configuration for the tenant is managed through
the SSO endpoints of the User Management API.
key_management:
creation: Settings > API Key Management in the console, or createApiKey (POST /v2/users/{userId}/keys).
ownership: A key always belongs to the user who created it, even when another person uses it.
ceiling: A key can never be granted more permission than its creating user holds through roles and group
membership.
visibility: The secret is shown once at creation and is never retrievable afterwards.
revocation: Revoke in the console or delete via the API. Takes effect in about five minutes and cannot
be undone.
default: Users have no API key by default; one must be created explicitly.
orphans: Keys created by a deleted user remain active after that user is deleted.
docs: https://api.docs.moogsoft.com/docs/latest/branches/main/6553f9391961d-manage-api-keys
authorization:
model: role and permission based, enforced per feature area
default_roles:
- Operator (read-only, plus alert/incident status and ownership updates)
- Administrator (read and write)
- Owner (read and write)
custom_roles: true
group_roles: true
method_mapping:
GET: Read Only
POST: Full Access
PATCH: Full Access
DELETE: Full Access
note: Permission failures can present as 404 rather than 403 on some resources.
docs: https://api.docs.moogsoft.com/docs/latest/branches/main/b16f03ec715a2-user-roles-and-permissions
transport:
https_only: true
tls: TLSv1.3 observed on www.moogsoft.com
mtls: false
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/moogsoft-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.