Moyasar Rate Limits
Moyasar does not publish fixed numeric per-account or per-endpoint rate limits for its REST API in the public documentation. Standard payment-gateway hygiene applies: authenticate every request over HTTPS with a valid API key, use the `given_id` idempotency field on payment creation to avoid duplicate charges on retries, and implement exponential backoff with jitter on transient errors. Webhook delivery is retried by Moyasar (up to six attempts) when the merchant endpoint does not return a 2xx quickly.
Moyasar Rate Limits is the machine-readable rate-limit profile for Moyasar on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and attempts.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Payments, Payment Gateway, Saudi Arabia, mada, and Rate Limiting.
Limits
Policies
Sources
- https://docs.moyasar.com/
- https://docs.moyasar.com/api/authentication
- https://docs.moyasar.com/api/other/webhooks/webhook-reference/
Work with this as data
Every rate limit 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 rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit 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
curl "https://apis.io/api/v1/rate-limits/moyasar-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.