n3rgy · Rate Limits

N3Rgy Rate Limits

n3rgy does not publish a global requests-per-second rate limit. What it DOES publish, in the Customer Service API V2 developer guide, are three concrete quota ceilings enforced with HTTP 429 — a per-request item cap and a daily processed-entries threshold on Read Inventory, and a per-customer daily request counter on Update Now. There is no documented Retry-After or X-RateLimit-* response header; the quota state is only surfaced in the 429 message body. The changelog entry "AMI updates and API usage plan tuning" (2.39.1) confirms AWS API Gateway usage plans sit behind the key, but the per-key throughput values are not published.

N3Rgy Rate Limits is the machine-readable rate-limit profile for n3rgy on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring items, entries, and requests.

The profile also includes response codes documented for throttled.

Tagged areas include Rate Limiting, Smart Metering, and Energy Data.

4 Limits Throttle: 429
Rate LimitingSmart MeteringEnergy Data

Limits

Read Inventory items per element per request request
items
200
Applies independently to each of the mpxns, uprns and deviceIds arrays in the request body.
Read Inventory processed entries per day customer
entries · day
1000000
The daily threshold is the sum of all entries across all elements (mpxns, uprns and/or deviceIds) in all requests that day.
Update Now requests per utility/reading-type combination per day customer
requests · day
The counter is "the configured number of requests" — configured per customer and NOT published as a number in the developer guide.
Export profile creation (V1 solution) customer
requests
The OpenAPI declares a 429 response for this operation; the developer guide does not document the threshold.

Sources