Properties
| Name | Type | Description |
|---|---|---|
| message | string | Optional response message. |
| receiver.accountTitle | string | Name associated with the account. |
| receiver.accountStatus | string | Account status. |
| receiver.accountCurrency | string | Currency of the account. |
| receiver.nameMatchPercentage | string | Percentage match between the beneficiary name and the institution's records. |
| receiver.accountType | string | Type of account. |
| error.code | string | MoneyGram-defined error code. |
| error.message | string | Human‑readable error message. |
| error.target | string | Field causing the error. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/moneygram/main/json-schema/moneygram-post-v1-accounts-validate-response-schema.json",
"title": "PostV1AccountsValidateResponse",
"x-generated": "2026-10-15",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_ae-authored/moneygram-openapi-generated.yml#/components/schemas/PostV1AccountsValidateResponse",
"type": "object",
"properties": {
"message": {
"type": "string",
"description": "Optional response message."
},
"receiver.accountTitle": {
"type": "string",
"description": "Name associated with the account."
},
"receiver.accountStatus": {
"type": "string",
"description": "Account status."
},
"receiver.accountCurrency": {
"type": "string",
"description": "Currency of the account."
},
"receiver.nameMatchPercentage": {
"type": "string",
"description": "Percentage match between the beneficiary name and the institution's records."
},
"receiver.accountType": {
"type": "string",
"description": "Type of account."
},
"error.code": {
"type": "string",
"description": "MoneyGram-defined error code."
},
"error.message": {
"type": "string",
"description": "Human‑readable error message."
},
"error.target": {
"type": "string",
"description": "Field causing the error."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/moneygram-post-v1-accounts-validate-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.