Rate Limits

The NGN Market API uses a monthly call quota rather than a per-second rate limit. Each plan comes with a fixed number of calls per calendar month. Every response includes a meta object showing how many calls you have used, how many remain, and when your quota resets.

Monthly call quotas

Plan	Monthly calls
Free	3,000
Hobby	10,000
Starter	100,000
Pro	250,000
Business	2,000,000
Enterprise	Unlimited

Quotas reset on your billing renewal date, the same day of the month you first subscribed. Unused calls do not roll over.

Per-minute burst limits

In addition to monthly quotas, each plan enforces a per-minute request cap to prevent burst abuse. Exceeding this limit returns HTTP 429 with the RATE_LIMITED error code. Unlike quota exhaustion, per-minute limits reset automatically after 60 seconds — no action needed.

Plan	Requests per minute
Free	30
Hobby	60
Starter	120
Pro	120
Business	300
Enterprise	Unlimited

Rate limit headers

Every response (not just 429s) includes standard IETF draft-7 rate limit headers, so you can track your per-minute budget without parsing the response body:

Header	Description
`RateLimit-Policy`	The limit and window, e.g. `120;w=60`
`RateLimit-Limit`	Requests allowed in the current window
`RateLimit-Remaining`	Requests left in the current window
`RateLimit-Reset`	Seconds until the window resets

When a request is rejected with 429 RATE_LIMITED, the response also includes a Retry-After header (seconds to wait before retrying) alongside the meta.retry_after field in the body.

All API keys on your account share one quota pool. Every call made by any of your keys counts toward the same monthly total.

Tracking usage

Every API response includes a meta object. You do not need a separate request to check your usage. For richer analytics like daily call volume, top endpoints, and status code breakdown, use the dedicated GET /account/usage endpoint.

{
  "success": true,
  "data": { },
  "meta": {
    "plan": "starter",
    "calls_used": 4821,
    "calls_remaining": 95179,
    "reset_at": "2026-06-15T23:57:00.000Z"
  }
}

Field	Type	Description
`plan`	string	Your current plan: `free`, `hobby`, `starter`, `pro`, `business`, or `enterprise`
`calls_used`	integer	Total calls made this month across all your keys
`calls_remaining`	integer	Calls left before your quota is exhausted
`reset_at`	string	ISO 8601 UTC timestamp of your next quota reset

Read meta.calls_remaining in your application and alert yourself before you hit zero so you are not caught off guard.

When you exceed your quota

When calls_used reaches your monthly limit, all further requests return HTTP 429 with the QUOTA_EXCEEDED error code. This is distinct from RATE_LIMITED, which is returned when you exceed the per-minute burst cap:

{
  "success": false,
  "error": {
    "code": "QUOTA_EXCEEDED",
    "message": "Monthly call limit of 100,000 reached. Resets on 2026-05-01T00:00:00.000Z."
  },
  "meta": {
    "plan": "starter",
    "calls_used": 100000,
    "calls_remaining": 0,
    "reset_at": "2026-06-15T23:57:00.000Z"
  }
}

Once you receive QUOTA_EXCEEDED, every request will be rejected until your quota resets or you upgrade.

What to do when you hit your limit

Wait for the reset. Check meta.reset_at to see the exact UTC time your quota resets on your next billing date.
Upgrade your plan. Log in to your developer dashboard and select a higher plan. Upgrades take effect immediately. See Plans for pricing and call limits.

Reducing unnecessary usage

Cache responses where possible

Some endpoints return data that changes infrequently, like the company list (/companies) or available dates (/market/available-dates). Cache these in your application and refresh on a schedule rather than fetching on every request.

Avoid polling in tight loops

NGX equity prices refresh roughly every 20 minutes. Polling every few seconds burns through your quota for no benefit, since the data behind those extra calls hasn’t changed.If you’re polling specifically to catch changes as soon as they happen, the WebSocket API is a better fit than any polling interval: it pushes a message only when the data actually changes, and it doesn’t count against this quota at all.

Use one key per integration

Multiple keys do not give you more calls since all keys share one quota pool. Keep your key count to what you actually need.

Get Started

For AI Agents

Plans & Limits

Core Concepts

Monthly call quotas

Per-minute burst limits

Rate limit headers

Tracking usage

When you exceed your quota

What to do when you hit your limit

Reducing unnecessary usage

​Monthly call quotas

​Per-minute burst limits

​Rate limit headers

​Tracking usage

​When you exceed your quota

​What to do when you hit your limit

​Reducing unnecessary usage

Monthly call quotas

Per-minute burst limits

Rate limit headers

Tracking usage

When you exceed your quota

What to do when you hit your limit

Reducing unnecessary usage