Monoova PayTo Async API
The `AsyncResponse` is used in operations where the request is accepted, but the processing is not immediate. This response format provides information for tracking and checking the request status.This API adheres to the Microsoft [async-request-reply pattern](https://learn.microsoft.com/en-us/azure/architecture/patterns/async-request-reply), ensuring efficient handling of non-immediate requests.Featuring high throughput and generous rate limits, this API is optimal for bulk operations, allowing for the efficient processing of larger datasets.### HTTP Status Code- **202 Accepted**: - *Description*: Indicates that the request has been accepted for processing but has not been completed.### HTTP Headers- **Location**: - *Description*: Provides the URL where the client can check the status of the asynchronous operation.Clients should periodically poll this URL to retrieve the final result of the request. - *Example*: `https://sand-api.monoova.com/...`- **Retry-After**: - *Description*: Suggests the number of seconds the client should wait before polling the LocationURL again. This helps manage server load by preventing requests that are too frequent. - *Example*: `10`
Monoova PayTo Async API is one of 31 APIs that Monoova publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include PayTo Async API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 8 operations across 8 paths, and defines 17 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 PayTo Async 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 8
Across 8 paths, the API surfaces 8 operations — 2 GET, 4 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
The AsyncResponse is used in operations where the request is accepted, but the processing is not immediate. This response format provides information for tracking and checking the…
Schemas 17
The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PayerDetailsDto (8 properties), PaymentDetailsDto (7 properties), PayeeDetailsDto (7 properties), PaymentTermsDto (6 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 PayTo Async 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.