Tier limit exceeded
TIER_LIMIT_EXCEEDED means your current subscription does not allow the action you just attempted. The most common cases are trying to register one device too many, or trying to create an API key on the Free plan. The HTTP status returned is 403 Forbidden.
Understand why this happens
Your request was rejected because your organization has reached a limit of its current plan. The error response tells you exactly which limit was hit, your current count, and the plan name:
HTTP/1.1 403 Forbidden
Content-Type: application/json
{
"error": {
"code": "TIER_LIMIT_EXCEEDED",
"message": "Device limit reached. Your free plan allows a maximum of 2 devices (current: 2). Upgrade your plan to add more devices."
}
}
See which limits trigger it
| Plan | Devices | API key creation |
|---|---|---|
| Free | up to 2 | not allowed |
| Pro | up to 10 | allowed |
| Enterprise | unlimited | allowed |
Two actions are gated by the plan:
- Registering a new device — blocked once your organization already has the maximum number of devices for the plan.
- Creating an API key — blocked entirely on the Free plan, regardless of how many devices you have.
Check your current plan and devices
Confirm which plan your organization is on and how many devices are registered:
curl https://api.e-bon.ro/api/v1/org \
-H "Authorization: Bearer <token>"
curl https://api.e-bon.ro/api/v1/devices \
-H "Authorization: Bearer <token>"
Resolve the error
Remove a device you no longer use
If one of the listed devices is no longer in service — for example an AMEF you replaced or a location you closed — delete it to free a slot:
curl -X DELETE https://api.e-bon.ro/api/v1/devices/{deviceId} \
-H "Authorization: Bearer <token>"
Then retry the registration of your new device.
Upgrade your plan
Sign in to the portal as owner or admin and open the Billing page. Pick the plan that fits your fleet, complete checkout, and the new limits apply immediately.
You do not need to rotate any token — your existing session keeps working.
Retry the original request
Re-send the request that failed. The plan change is visible to the very next call, so the action that was just blocked will now succeed.
To create API keys, upgrade to Pro or Enterprise
API keys (the long-lived ebon_live_… tokens used for server-to-server integrations) are available starting with the Pro plan. There is no per-organization exception on Free — upgrading is the only way to enable API key creation.
Get help if you are still blocked after upgrading
If you completed checkout but still receive TIER_LIMIT_EXCEEDED, contact support at support@e-bon.ro or via e-bon.ro/contact. Include:
- Your organization slug
- The
orgIdfrom your token - A recent failed request ID
For background on this and other HTTP error codes, see the Errors reference.
HMAC signature mismatch
Why `X-EBon-Signature` verification fails on your endpoint — clock skew, wrong secret after rotation, and body re-serialization gotchas.
Integration walkthrough
End-to-end story for connecting your first fiscal device with e-bon — from creating an account to your first X report.