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

Payt notifications API

Operations about notifications

Payt notifications API is one of 20 APIs that Payt 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, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.paytsoftware.com, https://demo-api.paytsoftware.com.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://api.paytsoftware.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Payt notifications API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth2 access token or static API token. See [Authorization](/authentication/authorization) for how to obtain one.

Paths & Operations 2

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

notifications 2

Operations about notifications

GET
/v1/notifications
Get administration notifications
getV1Notifications 9 params → 200401403
GET
/v1/notifications/{id}
Get administration notification by id
getV1NotificationsId 3 params → 200401403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are CustomerApi_V1_NotificationEntity (12 properties), CustomerApi_V1_UserEntity (3 properties), CustomerApi_NotificationsPageEntity (2 properties), CustomerApi_ErrorEntity (2 properties). Each schema is shown below with its type and property counts.

CustomerApi_V1_NotificationDetailsEntity
object
1 property
CustomerApi_ErrorEntity
object
CustomerApiErrorEntity model
2 properties 2 required
CustomerApi_V1_NotificationEntity
object
CustomerApiV1NotificationEntity model
12 properties 7 required
CustomerApi_V1_UserEntity
object
3 properties 3 required
CustomerApi_NotificationsPageEntity
object
CustomerApiNotificationsPageEntity model
2 properties 1 required
CustomerApi_PaginationEntity
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payt-notifications-api-openapi.yml Raw ↑

Other APIs Payt publishes across the network.

Payt administrations API
Payt companies API
Payt contacts API
Payt credit_cases API
Payt debtors API
Payt files API
Payt invoices API
Payt messages API
Payt notes API
Payt order_lines API
Payt orders API
Payt payment_conditions API
Where this information came from

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