How access works
Access is given to a project, not to a person: a project has an owner (an iBus account), groups of operations, keys, optional IP addresses and limits.
1. Application
Sign in to iBus and describe the project: what you are building, which data you need, the expected load, how you call the API and from which addresses. The e-mail of your account becomes the confirmed contact.
One open application at a time; the draft is kept while you write.
2. Review
The iBus team reads every application and may ask a question. You answer on the application's page, which also shows the status: draft, sent, in review, details needed, approved or declined.
There is no key before approval, and no review time is promised.
3. Project and keys
- After approval the project appears in your developer cabinet with its groups and limits.
- Create a key there. It is shown once; iBus keeps only a hash and a short prefix such as
ibk_live_k_7mq2xw4hzt. - Up to 5 working keys per project, for
testand forlive. When you rotate a key, the old one keeps working for up to 24 hours. - A key that leaked can be revoked in one click: it stops working within seconds.
4. IP addresses
With an IP list, a request needs both the right key and an allowed address. With the restriction on and an empty list, every request is refused. Private and very wide networks are refused; a wide network needs an explicit confirmation.
If iBus set the restriction, changes go through a request on the project page.
5. Limits
| Who | Per minute (burst) | Per day, UTC | Per month, UTC | At once | Heavy: per minute / day |
|---|---|---|---|---|---|
| Project, «trial» | 30 (10) | 1,000 | 20,000 | 2 | — |
| Project, «standard» | 120 (30) | 20,000 | 400,000 | 4 | — |
| Project, individual (example) | 120 (30) | 20,000 | 400,000 | 4 | 6 / 300 |
| Without a key: older addresses only, per address (transition) | 60 (30) | 20,000 | 400,000 | 6 | 20 / 600 |
Day and month budgets reset at 00:00 UTC (02:00 or 03:00 in Israel, depending on the season). A refusal says which limit was reached and when to retry (Retry-After). Individual limits are set by iBus on request.
6. Pause and block
iBus can pause a project (its keys stay) or block it (all keys are revoked), always with a reason shown on the project page, where you can reply. Repeated violations, such as many wrong keys, lead to a short automatic pause; a long block is only a person's decision.
7. What is kept
- For each request: the time, project, key prefix, operation, status, duration and the network part of the address. Details are kept for 7 days, then only counts.
- Full addresses with query strings and coordinates from your requests are not stored.
- Keys never appear in logs, reports or messages.
Every refusal code and what to do: access errors.