PortOne · Rate Limits

Portone Rate Limits

PortOne does not publish explicit numeric rate limits for the V2 (api.portone.io) or legacy V1 (api.iamport.kr) REST APIs in its developer documentation. As a payment gateway, effective throughput is bounded by the merchant's account standing and, critically, by the rate and fraud controls of the downstream PSP handling each transaction. Standard HTTP 429 handling with exponential backoff is the recommended client posture. Specific per-endpoint values are not reconciled in this artifact.

Portone Rate Limits is the machine-readable rate-limit profile for PortOne on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and transactions.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Payments, Payment Orchestration, Korea, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-17.
Written by API Evangelist on 2026-07-17 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsPayment OrchestrationKoreaRate LimitingQuotasThrottling

Limits

V2 REST API (api.portone.io) account
requests
see provider documentation
No published numeric limit; bounded by account standing and PSP throughput.
V1 REST API (api.iamport.kr) account
requests
see provider documentation
Legacy Iamport API; token-authenticated; no published numeric limit.
Payment (acting) endpoints account
transactions
bounded by downstream PSP
Card / virtual-account / easy-pay throughput and fraud controls are enforced by the connected PSP, not PortOne.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and idempotently retry payment lookups (not acting operations without idempotency keys).
Webhook Reconciliation
Rather than polling aggressively, rely on registered webhooks for payment status changes and use the resend-webhook operation to recover missed events.

Sources

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/portone-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.