How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Immuta Notification API

APIs for managing notifications

Immuta Notification API is one of 12 APIs that Immuta publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Notification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 18 operations across 12 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{global-segment}.api.immutacloud.com/marketplace.

18 operations 12 paths 16 schemas 2 DELETE8 GET2 PATCH3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://na.api.immutacloud.com/marketplace
Authentication
HTTP Bearer
Contact
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Immuta Notification API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer).

Paths & Operations 18

Across 12 paths, the API surfaces 18 operations — 2 DELETE, 8 GET, 2 PATCH, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Notification 18

APIs for managing notifications

GET
/api/notification/user-preferences
Get user preferences
getUserPreferences → 200
PUT
/api/notification/user-preferences
Update user preferences
updateUserPreferences body → 200
PUT
/api/notification/user-provider-configs
updateUserProviderConfigs body → 200
GET
/api/notification/inbox/messages
Get inbox messages
getInboxMessages 3 params → 200
GET
/api/notification/inbox/messages/{id}
Get inbox message by ID
getInboxMessage 1 param → 200
PATCH
/api/notification/inbox/messages/{id}
Set inbox message read status
setInboxMessageReadStatus 1 param body → 200
PATCH
/api/notification/inbox/messages/update-bulk
Bulk update inbox message read status
batchUpdateInboxMessage body → 200
GET
/api/notification/webhook
Get webhooks
getWebhooks → 200
POST
/api/notification/webhook
Create webhook
createWebhook body → 200
GET
/api/notification/webhook/{id}
Get webhook by ID
getWebhook 1 param → 200
PUT
/api/notification/webhook/{id}
Update webhook
updateWebhook 1 param body → 200
DELETE
/api/notification/webhook/{id}
Delete webhook
deleteWebhook 1 param → 204
GET
/api/notification/webhook/{id}/history
Get webhook history
getWebhookHistory 3 params → 200
POST
/api/notification/webhook/{id}/test
Test webhook
testWebhook 1 param → 200
POST
/api/notification/webhook/test
Test webhook configuration
testWebhookConfig body → 200
GET
/api/notification/slack/configuration
Get Slack notifications configuration
getSlackConfiguration → 200
DELETE
/api/notification/slack/configuration
Delete Slack notifications configuration
deleteSlackConfiguration → 200
GET
/api/notification/slack/test
Test Slack notifications configuration
testSlackConnection → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are InboxMessage (8 properties), Webhook (5 properties), UpdateWebhook (3 properties), WebhookTestResult (3 properties). Each schema is shown below with its type and property counts.

WebhookTestResult
object
3 properties 2 required
GetSlackConfigurationResponse
object
2 properties 2 required
CreateWebhook
object
3 properties 1 required
UpdateWebhook
object
3 properties
UpdateUserPreferencesResponse
object
2 properties 2 required
UpdateUserPreferencesRequest
object
1 property 1 required
PaginatedInboxMessages
object
2 properties 2 required
InboxMessage
object
8 properties 6 required
TestSlackConnectionResponse
object
2 properties 1 required
UpdateUserProviderConfigsResponse
object
2 properties 2 required
Webhook
object
5 properties 2 required
PaginatedWebhookHistory
object
2 properties 2 required
GetUserPreferencesResponse
array
UpdateUserProviderConfigsRequest
object
1 property 1 required
BatchUpdateInboxMessage
array
UpdateInboxMessage
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

immuta-notification-api-openapi.yml Raw ↑

Other APIs Immuta publishes across the network.

Immuta Govern API
Immuta Access Request API
Immuta Asset API
Immuta Auth API
Immuta Data Product API
Immuta Data Source API
Immuta Data Use Agreement API
Immuta Health API
Immuta Metadata API
Immuta Request Form API
Immuta Settings API
Where this information came from

This is an independent, third-party profile of Immuta Notification API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.