Skip to content

Commit 3bf031a

Browse files
omer9564zeevmoney
andauthored
Remove outdated note about adjustable rate limits in API documentation (#604)
* Remove outdated note about adjustable rate limits in API documentation * fix build --------- Co-authored-by: Zeev Manilovich <zeevmanilovich@gmail.com>
1 parent 1ba1454 commit 3bf031a

File tree

2 files changed

+5
-6
lines changed

2 files changed

+5
-6
lines changed

docs/api/api-with-cli.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ For fact requests (`/v2/facts/*`), the limit is 3,000 requests per minute.
2525
For schema requests (`/v2/schema/*`), the limit is 1,000 requests per minute.
2626
For bulk requests, the limit is 100 requests per 10 minutes.
2727

28-
The rate limit is adjustable per customer, reach out to us if you need to adjust the rate limit.
2928
## API Endpoints and Regions
3029
All the examples in this documentation are using the `api.permit.io` endpoint.
3130

docs/how-to/manage-data/loading-data.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ import addingAttributes from "/static/ui-videos/how-to/loading-data/attributes-t
77

88
There are three ways you can load data into Permit / your PDPs:
99
1. Loading to Permit as a database - storing attributes per object in the [UI](#via-a-user-in-the-ui) or [API](#via-the-api)
10-
2. Loading data as part of the [input for authorization queries](#via-the-permitcheck-function).
11-
3. Loading data asynchronously in the background from data sources [via OPAL](#via-opal)
10+
2. Loading data as part of the [input for authorization queries](#via-the-permitcheck-function).
11+
3. Loading data asynchronously in the background from data sources [via OPAL](#via-opal)
1212

1313
## Via a user in the UI
1414

@@ -19,7 +19,7 @@ As you perform a `permit.check()` for any individual user to check his access, t
1919
function and the enforcement is evaluated based on the policy and the user attributes.
2020

2121
<video controls autoPlay loop playsInline>
22-
<source src={addingAttributes} />
22+
<source src={addingAttributes}/>
2323
</video>
2424

2525
## Via the `permit.check()` function
@@ -34,7 +34,7 @@ These attributes are evaluated on each enforcement check. This also gives you th
3434
:::info
3535
Both a resource and a user can have multiple attributes attached to them.
3636
There are no practical limits on number of objects or object sizes.
37-
There are limits on the overall data volume that can be loaded to a single PDP, which can be bypassed via [PDP Sharding](/how-to/manage-data/pdp-sharding/).
37+
There are limits on the overall data volume that can be loaded to a single PDP, which can be bypassed via [PDP Sharding](/concepts/pdp/overview#sharded-edge-pdps).
3838
:::
3939

4040
Here is an example of the code:
@@ -81,7 +81,7 @@ To make changes to the OPAL Scope, use the
8181
[OPAL Scope API](https://api.permit.io/v2/redoc#tag/Scope-Configurations). Simply include the
8282
project and environment IDs in the API endpoint URL - don't worry, our guide can show you where to find them.
8383

84-
Out of the box, Permit automatically pulls in details about users, roles, and more from its cloud database to the PDP's policy engine,
84+
Out of the box, Permit automatically pulls in details about users, roles, and more from its cloud database to the PDP's policy engine,
8585
setting a solid foundation for your policy.<br />
8686

8787
To view the data structure loaded into PDPs used by default check out the API reference and the example [here](https://api.permit.io/v2/redoc#tag/OPAL-Data-(-EAP-)).

0 commit comments

Comments
 (0)