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

Leadping Notifications API

Manages user notifications, announcements, and push-notification installations. Use these endpoints to retrieve notification feeds and unread counts, update read state, and register or remove client push installations.

Leadping Notifications API is one of 29 APIs that Leadping 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, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 8 operations across 8 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.leadping.ai.

8 operations 8 paths 11 schemas 1 DELETE2 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.leadping.ai
Authentication
HTTP Bearer, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Leadping Notifications API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT or organization API key) (Bearer). It accepts HTTP bearer tokens (Leadping source key) (SourceKey).

  • Bearer — Authorization header using the Bearer scheme. Accepted values are Leadping user JWT access tokens and WorkOS organization API keys beginning with sk.
  • SourceKey — Leadping source key for lead ingestion endpoints only using the Authorization header. Example: "Authorization: Bearer lpsrc...".

Paths & Operations 8

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

Notifications 8

Manages user notifications, announcements, and push-notification installations. Use these endpoints to retrieve notification feeds and unread counts, update read state, and regist…

GET
/notifications/{id}
Get a current-user notification
Notifications_GetForCurrentUser 1 param → 200404401429
POST
/notifications/me
List notifications for current user
Notifications_GetAllForCurrentUser 2 params body → 200400500401429
GET
/notifications/unread-count
Get unread notifications for current user
Notifications_GetUnreadCount → 200400500401429
POST
/notifications/{id}/mark-read
Mark a current-user notification as read
Notifications_MarkAsRead 1 param → 200400404500401429
POST
/notifications/mark-all-read
Mark all current-user notifications as read
Notifications_MarkAllAsRead → 200400500401429
POST
/notifications/announcements
List announcements for current user
Notifications_GetAnnouncements body → 200400500401429
PUT
/notifications/push/installations/current
Register a current-user mobile push installation
Notifications_RegisterPushInstallation body → 200400401429
DELETE
/notifications/push/installations/{installationId}
Unregister a current-user mobile push installation
Notifications_UnregisterPushInstallation 1 param → 200401429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are NotificationResponse (16 properties), NotificationTableRow (14 properties), PushInstallationRequest (11 properties), RequestDataOptions (8 properties). Each schema is shown below with its type and property counts.

NotificationResponse
object
Describes notification data used in Leadping API requests and responses.
16 properties
RequestDataOptions
object
Defines cursor pagination, sorting, search, exact-match filters, and range filters for a structured API query.
8 properties
NotificationTableRow
object
Describes notification data returned by Leadping.
14 properties
NotificationPriority
string
Ranks the urgency and presentation importance of a Leadping user notification.
PushInstallationRequest
object
Describes a mobile push installation. Identity and Azure tags are derived by the API.
11 properties
PagedResultOfNotificationTableRow
object
Returns one page of query results together with page-size, optional total-count, and opaque continuation-cursor metadata.
4 properties
OrderByOption
object
Defines one field and direction used to order an API query result set.
2 properties
ExactMatchFilter
object
Selects records whose named field equals a supplied scalar value.
2 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
RangeFilter
object
Selects records by applying inclusive or exclusive lower and upper bounds to a named comparable field.
5 properties
NotificationType
string
Identifies the Leadping workflow or account event communicated by a user notification.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-notifications-api-openapi.yml Raw ↑

Other APIs Leadping publishes across the network.

Leadping MCP Servers
Leadping Webhook Events
Leadping Analytics API
Leadping Automations API
Leadping Call Events API
Leadping Calls API
Leadping Contact API
Leadping Conversations API
Leadping Events API
Leadping Feedback API
Leadping Leads API
Leadping Lead Status Changes API
Where this information came from

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