canonical: https://jentic.com/apis/moneygram.com/moneygram

# MoneyGram API

The MoneyGram API creates and settles money transfers and their disbursements. For a transaction it quotes the fees and exchange rate, updates the transfer details, and commits it to send, with the same quote-update-commit flow available on the disbursement side. A status endpoint reports where a transaction stands, and reference-data endpoints return the supported countries, currencies, and enumerations. Agent-locator and FX-rate endpoints return pickup locations and current rates. All calls use an OAuth2 access token.

## For AI agents

Quote, update, and commit MoneyGram money transfers and disbursements, check transaction status, and read reference data like countries, currencies, exchange rates, and pickup locations.

## Scope

Covers transfer and disbursement quoting, sending, status, and the supporting reference data. Does not handle card processing, account management, or compliance screening.

## Capabilities

- Quote the fees and exchange rate for a transfer transaction
- Update a transfer's details and commit it to send
- Run the same quote, update, and commit flow for a disbursement
- Check the status of a transaction
- Read supported countries, currencies, and enumerations
- Look up agent pickup locations and current FX rates

## Use cases

### Agent-Assisted Transfer

A finance assistant can walk a transfer from quote to send with human confirmation on the money-moving step. The agent quotes the transaction, updates the recipient details, and, once a person approves, commits it, so a supported send runs through the API while the commit stays a deliberate, reviewed action.

Example prompt: Quote a transfer, update its details, and commit it once a human approves

### Transfer Status Tracking

A support agent can answer 'where is my transfer' without opening a console. It calls the status endpoint for a transaction, reads back the current state, and relays it to the customer, so a status question is answered from the live record rather than a stale note.

Example prompt: Fetch the status of a transaction and report its current state to the customer

### Corridor and Rate Lookup

A planning agent can tell a user what a corridor supports and what it will cost before starting a transfer. It reads the countries, currencies, and FX-rate endpoints, and finds nearby pickup locations, so a question like 'can I send to this country and at what rate' is answered from reference data.

Example prompt: Read the supported countries, currencies, and current rate for a corridor and list nearby pickup locations

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/transfer/v1/transactions/{transactionID}/quote` | Quote a transfer transaction |
| PUT | `/transfer/v1/transactions/{transactionID}/commit` | Commit a transfer to send |
| GET | `/status/v1/transactions/` | Check transaction status |
| GET | `/reference-data/v1/countries` | List supported countries |
| GET | `/agent-locator/v1/locations` | Find agent pickup locations |
| GET | `/fxrate/v1/rates` | Get current exchange rates |

## Key resources

- **Transfers** — Quote, update, and commit endpoints that create and send a transfer transaction
- **Disbursements** — The parallel quote, update, and commit flow for disbursing a transaction
- **Status** — The endpoint that reports where a transaction stands
- **Reference data** — Countries, currencies, enumerations, agent locations, and FX rates

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 68 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 85 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/moneygram.com/moneygram/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the MoneyGram API by hand means handling its OAuth2 flow and sequencing the quote, update, and commit calls correctly for both transfers and disbursements. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the transfer, status, and reference-data operations.
- **Permission scoping:** MoneyGram puts the transaction id in the URL path (`/transfer/v1/transactions/{transactionID}`), so a rule can scope your agent to one transaction and allow only the quote and status operations, keeping the commit step out of scope until you add it. You decide which operations are in scope, and every action is logged.
- **Credential handling:** Your MoneyGram OAuth2 token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'quote a money transfer' or 'check a transaction status', and Jentic returns the matching MoneyGram operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **PayPal Payments** — Online payments and payouts across a large merchant network.
- **Payoneer** — Cross-border payouts and mass payment distribution.
- **Flutterwave** — Payments and transfers across African markets.

## FAQ

### What authentication does the MoneyGram API use?

The MoneyGram API authenticates with an OAuth2 access token, per its OpenAPI spec. When you call it through Jentic, that token is held by your own self-hosted instance and injected at execution time, so it never appears in the agent's prompt or logs.

### Can I quote and commit a transfer with the MoneyGram API?

Yes. Post to the quote endpoint for a transaction to get its fees and rate, update the transaction details, then call the commit endpoint to send it. The disbursement endpoints follow the same quote, update, and commit sequence.

### What are the rate limits for the MoneyGram API?

The OpenAPI spec for the MoneyGram API does not define rate limits. Check MoneyGram's partner documentation for the limits that apply to your credentials before running high-volume quoting or status polling.

### Is there a MoneyGram API MCP server?

You don't need an MCP server to give your agent the MoneyGram API. Jentic connects it directly from the API Directory: import it, store the OAuth2 token once, and your agent calls the transfer, status, and reference-data operations without another server's tool definitions loaded into its context.

### Can I limit what my agent is allowed to do with the MoneyGram API?

Yes. MoneyGram puts the transaction id in the URL path (`/transfer/v1/transactions/{transactionID}`), so a rule can scope your agent to one transaction and allow only the quote and status operations, leaving the commit step out of scope until you add it. The permitted set is yours to choose, and each action the agent takes is recorded.

### How do I quote a transfer with the MoneyGram API through Jentic?

Search Jentic with an intent like 'quote a money transfer', and it returns the quote operation with its input schema so the agent submits the transaction and reads back the fees and rate. To run it on your own infrastructure, install Jentic One from its GitHub repo.