Get Account Validation by Filter

GET

https://sand-api.monoova.com/au/cop/payman-v2/AccountValidation

Returns a paged list of Confirmation of Payee validations that match the supplied filters.

All filters are combined with AND. Omit every filter to return the most recent validations for your account. Results are split into pages using pageNumber and pageSize, and the paging object in the response reports the totals.

createdStartDatestringOptional — Start of the creation-date window. Enter a full ISO 8601 date-time including the UTC offset, for example <code>2026-09-01T00:00:00+10:00</code>. Cannot be a future date. Validations created on or after this point are returned.

createdEndDatestringConditional — End of the creation-date window. Enter a full ISO 8601 date-time including the UTC offset, for example <code>2026-09-23T23:59:59+10:00</code>. Set the time to the end of the day to include everything recorded on that date. Cannot be earlier than <code>createdStartDate</code>, so supply it together with <code>createdStartDate</code> when bounding a range.

lastModifiedStartDatestringOptional — Start of the last-modified window. Enter a full ISO 8601 date-time including the UTC offset, for example <code>2026-09-01T00:00:00+10:00</code>. Cannot be a future date. Use it to pick up validations whose result has changed since your last poll.

lastModifiedEndDatestringConditional — End of the last-modified window. Enter a full ISO 8601 date-time including the UTC offset, for example <code>2026-09-23T23:59:59+10:00</code>. Set the time to the end of the day to include everything recorded on that date. Cannot be earlier than <code>lastModifiedStartDate</code>, so supply it together with <code>lastModifiedStartDate</code> when bounding a range.

subMerchantIdstringOptional — Monoova submerchant Id to filter on. Returns only the validations recorded against that submerchant. Up to 36 characters: letters, digits, hyphen and underscore.

pageNumberinteger<int32>Optional — Page to be returned after records are split as per <code>pageSize</code>. Whole number, minimum 1. Falls back to 1 when omitted.

pageSizeinteger<int32>Optional — Number of records per page. Whole number between 1 and 500. Falls back to 50 when omitted.

200200 OK. A page of validations matching the filters, plus a <code>paging</code> object describing the position in the result set. An empty <code>resultData</code> array means no validation matched the filters — it is not an error.

400400 Bad Request. The request failed validation before it reached the name-matching service. The <code>errors</code> array names each failing field through <code>errorCode</code>, with a human-readable <code>errorMessage</code>. Correct the values and resend — retrying the identical request returns the same 400.

401401 Unauthorized. The bearer token is missing, malformed, or has expired. Generate a new token from the Monoova developer portal and send it in the <code>Authorization</code> header as <code>Bearer <token></code>. Do not retry with the same token.

403403 Forbidden. The token was accepted, but the account behind it is not permitted to perform this call — Confirmation of Payee is not enabled on the account, is not yet configured, or the <code>subMerchantId</code> supplied is not associated with it. This is an entitlement problem, not a data problem: the same request will keep returning 403 until Monoova updates the account configuration. Do not retry automatically.

404404 Not Found. No validation matches the <code>id</code> in the path — either it was never created, or it belongs to a different account. Check the value against the <code>accountValidationUniqueId</code> sent on the create request. A filter search that matches nothing returns 200 with an empty <code>resultData</code> array instead of a 404.

500500 Internal Server Error. An unexpected error occurred while processing an otherwise valid request. The request may or may not have been recorded, so re-send it with the same <code>accountValidationUniqueId</code> rather than a new one. Quote the <code>traceId</code> when contacting Monoova support.

502502 Bad Gateway. The request was valid, but an upstream service — the NPP gateway that performs the name match — returned an error, so no result could be produced. The validation was not completed. Retry with the same <code>accountValidationUniqueId</code> after a short delay, and escalate with the <code>traceId</code> if it persists.

504504 Gateway Timeout. An upstream service did not respond in time. Unlike a 502, the outcome is genuinely unknown — the validation may still have been recorded. Re-send with the same <code>accountValidationUniqueId</code> rather than a new one so the original record is reused, or call Get Account Validation by Id first to see whether a result already exists.

curl --request GET \
     --url 'https://sand-api.monoova.com/au/cop/payman-v2/AccountValidation?createdStartDate=2026-09-01T00%3A00%3A00%2B10%3A00&createdEndDate=2026-09-23T23%3A59%3A59%2B10%3A00&lastModifiedStartDate=2026-09-01T00%3A00%3A00%2B10%3A00&lastModifiedEndDate=2026-09-23T23%3A59%3A59%2B10%3A00&subMerchantId=SUBM-0001234&pageNumber=1&pageSize=50' \
     --header 'accept: application/json'