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

Opply Notifications API

The Notifications API from Opply — 12 operation(s) for notifications.

Opply Notifications API is one of 47 APIs that Opply 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.

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

Requests are made against the base URL https://api.opply.com.

12 operations 12 paths 16 schemas 3 GET7 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.0
Base URL
https://api.opply.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Opply Notifications API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as sessionid (cookieAuth). An API key is passed in the header as Authorization (tokenAuth).

  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 12

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

Notifications 12
GET
/api/v1/notifications/emails/brand/
Unsubscribe groups endpoints
api_v1_notifications_emails_brand_list → 200
POST
/api/v1/notifications/emails/brand/all/
Unsubscribe groups endpoints
api_v1_notifications_emails_brand_all_create body → 200
PUT
/api/v1/notifications/emails/brand/on-off-unsubscribe-groups/
Activate or deactivate unsubscribe groups for users
api_v1_notifications_emails_brand_on_off_unsubscribe_groups_update body → 200
GET
/api/v1/notifications/emails/supplier/
Unsubscribe groups endpoints
api_v1_notifications_emails_supplier_list → 200
POST
/api/v1/notifications/emails/supplier/all/
Unsubscribe groups endpoints
api_v1_notifications_emails_supplier_all_create body → 200
PUT
/api/v1/notifications/emails/supplier/on-off-unsubscribe-groups/
Activate or deactivate unsubscribe groups for users
api_v1_notifications_emails_supplier_on_off_unsubscribe_groups_update body → 200
GET
/api/v1/notifications/notifications/
Retrieve a list of notifications
api_v1_notifications_notifications_list 2 params → 200
POST
/api/v1/notifications/notifications/{uuid}/action-mark-clear/
Mark a notification action as clear by the user
api_v1_notifications_notifications_action_mark_clear_create 1 param → 204
POST
/api/v1/notifications/notifications/{uuid}/action-mark-read/
Mark a notification action as read by the user
api_v1_notifications_notifications_action_mark_read_create 1 param → 204
POST
/api/v1/notifications/notifications/{uuid}/mark-read/
Mark a general notification as read by the user
api_v1_notifications_notifications_mark_read_create 1 param → 204
POST
/api/v1/notifications/notifications/action-mark-related-cleared/
Mark action notification with the given relatedobjectuuid as cleared
api_v1_notifications_notifications_action_mark_related_cleared_create body → 204
POST
/api/v1/notifications/notifications/mark-related-read/
Mark all notifications with the given relatedobjectuuid as read
api_v1_notifications_notifications_mark_related_read_create body → 204404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Notification (19 properties), EmailNotifications (5 properties), PaginatedNotificationList (5 properties), ShortUser (3 properties). Each schema is shown below with its type and property counts.

ActionTypeEnum
string
order - Order request - Request contracts - Contracts onboarding - Onboarding samples - Samples quotes - Quotes
TitleEnum
string
Kriya KYB Reminder - Kriya Kyb Reminder New Quote - New Quote New Quote Reminder - New Quote Reminder New Request - New Request New Request Reminder - New Requ…
BlankEnum
MarkRelatedRead
object
2 properties 2 required
MarkRelatedCleared
object
3 properties 3 required
PaginatedNotificationList
object
5 properties 2 required
EmailNotifications
object
5 properties 3 required
ShortUser
object
3 properties 2 required
ActionClearTriggerEnum
string
Mark samples as dispatched - Mark Samples Dispatched Reject samples request - Reject Samples Request Buyer marks samples as delivered - Buyer Marks Samples Del…
EmailNotificationsTypeEnum
string
bsnewmessage - bsnewmessage bsdailymessagesummary - bsdailymessagesummary bpaymentconfirmation - bpaymentconfirmation bpaymentdue - bpaymentdue bpaymentreminde…
UsedForEnum
string
generalnotifications - General Notifications actions - Actions
NotificationTypeEnum
string
trigger-based - Triggerbased time-based - Timebased user-specific - Userspecific global - Global
Notification
object
19 properties 12 required
AllEmailNotifications
object
1 property 1 required
NotificationCategoryEnum
string
tasks - Tasks taskmentions - Task Mentions updates - Updates system - System
NullEnum

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opply-notifications-api-openapi.yml Raw ↑

Other APIs Opply publishes across the network.

Opply Activity Feed API
Opply Admin panel API
Opply Agents API
Opply Agreements API
Opply api API
Opply App Orders API
Opply Brain API
Opply Brands API
Opply Buyer Documents API
Opply Buyer Financial Documents API
Opply Buyer Onboarding API
Opply Buyer self-onboarding API
Where this information came from

This is an independent, third-party profile of Opply Notifications 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.