Skip to content

Commit 9e3a171

Browse files
authored
rate limits and credentials update (#788)
1 parent f0a81b4 commit 9e3a171

File tree

2 files changed

+26
-11
lines changed

2 files changed

+26
-11
lines changed

modules/ROOT/pages/api/authentication.adoc

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,7 @@ The Aura API uses OAuth 2.0 for API authentication.
66

77
== Creating credentials
88

9-
label:AuraDB-Free[]
10-
label:AuraDB-Professional[]
11-
label:AuraDS-Enterprise[]
12-
label:AuraDB-Virtual-Dedicated-Cloud[]
13-
14-
AuraDB Virtual Dedicated Cloud users, and AuraDS Enterprise users have unrestricted access to creating API credentials.
15-
However, users with Free and Professional instances must have entered billing information or be a member of a marketplace project before they can create API credentials.
9+
All tiers can create Aura API credentials.
1610
API credentials are linked to the user account, inheriting its capabilities and roles.
1711
The API credentials never expire unless you delete them.
1812

modules/ROOT/pages/api/overview.adoc

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,7 @@ The following example shows how to use the base URL and versioning to make a req
3838
In the event of `5xx` server error responses, you may consider retrying the request after a delay if it is safe to do so.
3939
The response may include a `Retry-After` header with a suggestion of a suitable minimum delay before attempting to retry.
4040

41-
The global rate limit for all requests is 125 requests per minute.
42-
43-
You should consider your use of the rate limit before attempting to retry, and it is recommended that you use an exponential backoff delay with a limited number of retries before giving up.
41+
You should consider your use of the xref:api/overview.adoc#_rate_limits[rate limit] before attempting to retry, and it is recommended that you use an exponential backoff delay with a limited number of retries before giving up.
4442

4543
A request is only guaranteed to be safe to retry if it uses an idempotent HTTP method, such as `GET`.
4644
If, for example, you retry a request for creating an instance, you may end up with duplicate instances and end up being charged extra as a result.
@@ -55,4 +53,27 @@ An `X-Request-Id` response header is returned with each request and can be used
5553

5654
The value of this header contains a unique ID that can be used to track the journey of a request.
5755

58-
If you run into any issues with a particular request, you can https://support.neo4j.com/[raise a support ticket] and provide the `X-Request-Id`.
56+
If you run into any issues with a particular request, you can link:https://support.neo4j.com/[raise a support ticket] and provide the `X-Request-Id`.
57+
58+
== Rate limits
59+
60+
AuraDB Free and AuraDB Professional trial accounts without a billing method attached, get a rate limit of 25 requests per minute.
61+
62+
AuraDB Professional accounts with a billing method attached, AuraDB Business Critical, and AuraDB Virtual Dedicated Cloud get a rate limit of 125 requests per minute.
63+
64+
[cols="1,1"]
65+
|===
66+
|Tier |Rate Limit
67+
68+
|AuraDB Free & Pro (Trial, No Billing)
69+
|25 requests/minute
70+
71+
|AuraDB Pro (With Billing)
72+
|125 requests/minute
73+
74+
|AuraDB Business Critical
75+
|125 requests/minute
76+
77+
|AuraDB Virtual Dedicated Cloud
78+
|125 requests/minute
79+
|===

0 commit comments

Comments
 (0)