Monoova Manage Payment Agreements API
Methods to handle the payment agreement lifecycle. There are 2 ways in which a payment agreement can be amended – unilaterally (no payer approval needed), and Bilaterally (payer approval required)
Monoova Manage Payment Agreements API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Manage Payment Agreements. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 5 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against 2 base URLs: https://api.monoova.com, https://sand-api.monoova.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Monoova Manage Payment Agreements API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
It accepts HTTP basic authentication (BasicAuth).
By default, every request must be authenticated.
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 4 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Methods to handle the payment agreement lifecycle. There are 2 ways in which a payment agreement can be amended – unilaterally (no payer approval needed), and Bilaterally (payer a…
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are PayerDetailsDto (8 properties), CreatePaymentAgreementResponse (7 properties), PaymentDetailsDto (7 properties), PayeeDetailsDto (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Monoova 12
Other APIs Monoova publishes across the network.
This is an independent, third-party profile of Monoova Manage Payment Agreements 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.