Momo Vn MoMo API
Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Authenticate against MoMo and access merchant resources for Vietnam's leading mobile e-wallet payments platform.
Use for: Get an authentication token for the MoMo API, List all available MoMo merchant resources, Retrieve a specific MoMo resource by ID, Check whether a MoMo resource exists
Not supported: Does not handle non-Vietnamese payment methods, accounting reconciliation, or KYC verification - use for MoMo merchant authentication and resource lookup only.
Jentic publishes the only available OpenAPI specification for MoMo API, keeping it validated and agent-ready. MoMo is Vietnam's leading mobile e-wallet platform, used by millions of consumers for in-app payments, bill pay, and merchant transactions. The API exposed in this spec covers token issuance for authenticating against MoMo and resource lookup endpoints for accessing merchant-level resources programmatically. It targets Vietnamese merchants and platforms that need to integrate with the dominant local mobile payment provider.
Install Jentic One Beta
Connect the MoMo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MoMo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmomo.vn%2Fmomo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmomo.vn%2Fmomo" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with MoMo API.
Authenticate to MoMo by exchanging credentials for an access token
List merchant-level resources available on a MoMo account
Retrieve a specific MoMo resource by ID for downstream processing
Integrate Vietnamese mobile e-wallet flows into a multi-region payment stack
Pull MoMo resource metadata for reconciliation against internal records
Use Cases
Patterns agents use MoMo API for, with concrete tasks.
★ Vietnamese E-Wallet Merchant Onboarding
Authenticate a merchant against MoMo and pull the resources tied to that merchant account during initial onboarding. The token endpoint exchanges credentials for a session-bound token, and the resources endpoints expose what is configured on the merchant side. Suitable for cross-border platforms adding Vietnam coverage where MoMo is the dominant consumer payment method.
Call POST /auth/token with the client credentials, then GET /resources to list merchant resources for the authenticated account.
Resource Lookup for Reconciliation
Retrieve specific MoMo resources by ID to reconcile platform-side records against MoMo's view of the merchant account. The single-resource endpoint returns structured metadata that can be matched against internal databases without exporting from the MoMo dashboard. Useful for finance-ops teams running periodic reconciliation across multiple regional payment providers.
Call GET /resources/{id} with the resource ID and compare the response fields against the platform-side record.
Token Lifecycle Management
Manage the MoMo authentication token lifecycle by calling the token endpoint at startup and refreshing before expiry, so downstream resource calls always carry a valid X-API-Key. The token-first design separates credential exchange from data access and keeps secrets short-lived. Practical for platforms with strict secret-rotation requirements.
Call POST /auth/token to obtain a session token, store it, and call POST /auth/token again before the documented expiry to refresh.
Agent-Driven Vietnamese Payment Lookups
AI agents handling cross-region payment-ops queries call MoMo through Jentic to authenticate and retrieve merchant resources without holding the API key in their context. Jentic's spec is the only structured definition for this API, so schema-aware agents rely on it for tool selection and parameter validation.
Search Jentic for 'list momo merchant resources', load GET /resources, and execute against the authenticated account.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for momo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Exchange credentials for a MoMo access token
GET
/resources
List merchant resources
GET
/resources/{id}
Retrieve a specific merchant resource by ID
POST
/auth/token
Exchange credentials for a MoMo access token
GET
/resources
List merchant resources
GET
/resources/{id}
Retrieve a specific merchant resource by ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the MoMo API by hand means exchanging merchant credentials for an X-API-Key at the token endpoint, then setting that header on every resource call yourself. Through Jentic you install once, import the MoMo API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
MoMo puts the resource id in the URL path (/resources/{id}), so a rule can pin your agent to one resource for lookups. You choose the operations it may call, so the agent gets only the token and resource reads you allow.
Credential isolation
Your MoMo merchant credentials and the resulting X-API-Key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'authenticate to MoMo' or 'list MoMo resources', and Jentic returns the matching token or resource operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Global payment processing platform with broad card and wallet coverage outside of Vietnam
Choose Stripe for global card-first markets; use MoMo specifically when Vietnamese consumers expect to pay via the MoMo e-wallet.
FAQs
Specific to using MoMo API through Jentic.
Why is there no official OpenAPI spec for MoMo API?
MoMo publishes developer documentation but does not provide a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MoMo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the MoMo API use?
MoMo uses an API key sent in the X-API-Key request header. Obtain the key by calling POST /auth/token with merchant credentials. Through Jentic, both the merchant credentials and the resulting key are held encrypted in the credential vault so they never enter agent context.
Can I list merchant resources with the MoMo API?
Yes. After authenticating with POST /auth/token, call GET /resources to list resources for the merchant account, and GET /resources/{id} to retrieve a single resource by ID. The response shape is consistent across both endpoints.
What are the rate limits for the MoMo API?
MoMo does not document rate limits in this OpenAPI spec. Production rate limits are typically configured per merchant account on the MoMo developer portal at https://developers.momo.vn - confirm current limits there before running batch operations.
How do I get a MoMo access token through Jentic?
Run pip install jentic, search for 'authenticate to momo', load POST /auth/token, and execute it with the merchant credentials held in your Jentic One instance. Jentic returns the access token, which subsequent operations use automatically.
Is the MoMo API free?
Access to the API itself does not have a published flat fee - pricing for actual MoMo transactions is set by merchant agreement. Confirm with MoMo's merchant team for the commercial terms applicable to your account.
Can I limit what my agent is allowed to do with the MoMo API?
Yes. Because you run Jentic One yourself, your own rules decide which MoMo operations and credentials the agent may use, so you can allow only POST /auth/token and GET /resources while withholding anything else. Since MoMo puts the resource ID in the URL path at GET /resources/{id}, a rule can pin the agent to a single resource for lookups rather than the full list. The agent gets only the token exchange and resource reads you grant it.
GET STARTED