You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en-us/cloud/guides/data-store-api-handling.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Before sending requests to Open Cloud APIs for [standard data stores](../../refe
7
7
8
8
## Authorization
9
9
10
-
Like all Open Cloud APIs, data store endpoints require all requests to include the `x-api-key` header, which contains an API key with enough permissions for the request. This requires you to apply the key to the experience and the data store, and the endpoint operation is permitted. If the key is invalid, `403 Unauthorized` is returned. For more information on API keys, see [Manage API keys](api-keys.md).
10
+
Like all Open Cloud APIs, data store endpoints require all requests to include the `x-api-key` header, which contains an API key with enough permissions for the request. This requires you to apply the key to the experience and the data store, and the endpoint operation is permitted. If the key is invalid, `403 Unauthorized` is returned. For more information on API keys, see [Manage API keys](../auth/api-keys.md).
Copy file name to clipboardExpand all lines: content/en-us/cloud/guides/usage-data-stores.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Although Open Cloud APIs are similar to `Class.DataStoreService`, there are a fe
35
35
36
36
Data stores often store sensitive information, such as user profiles and virtual currency. To maintain security, each Open Cloud API has corresponding required permissions that you must add to your API key, such as the `List Keys` permission for the listing API. If you don't add the required permissions, your API call returns an error. For the specific permissions that are required for each operation, see the API reference of [standard](../../reference/cloud/datastores-api/v1.json) and [ordered data stores](../../reference/cloud/datastores-api/ordered-v1.json).
37
37
38
-
When [configuring your API keys](./api-keys.md#create-an-api-key), you can set granular permissions, such as read, write, and list entry, for each data store within a specific experience, or you can give a key to read or write all data stores within an experience. You can also limit access to a subset of data stores needed for your tool instead of exposing all data stores. This mitigates the impact in case your key gets leaked.
38
+
When [configuring your API keys](../auth/api-keys.md#create-an-api-key), you can set granular permissions, such as read, write, and list entry, for each data store within a specific experience, or you can give a key to read or write all data stores within an experience. You can also limit access to a subset of data stores needed for your tool instead of exposing all data stores. This mitigates the impact in case your key gets leaked.
39
39
40
40
## Build tools
41
41
@@ -57,7 +57,7 @@ From a high level, you can build your Python app by adding API key permissions a
57
57
58
58
#### Add API key permissions for data stores
59
59
60
-
When [creating an API Key](./api-keys.md) for this example, make sure you perform the following settings:
60
+
When [creating an API Key](../auth/api-keys.md) for this example, make sure you perform the following settings:
61
61
62
62
1. From the **Select API System** menu in the **Access Permissions** section, select **universe-datastores**.
63
63
@@ -74,7 +74,7 @@ When [creating an API Key](./api-keys.md) for this example, make sure you perfor
74
74
You don't need the `create entries` API key permission since the app doesn't create new user inventories.
75
75
</Alert>
76
76
77
-
1. In the **Security** section, explicitly set IP access to the key using [CIDR notation](./api-keys.md#cidr-format), and set an explicit expiration date so your key automatically stops working after that date. For this example, if you plan to do local testing first, you can remove the IP restriction by setting it to **0.0.0.0/0** and let it expire in **30 days**.
77
+
1. In the **Security** section, explicitly set IP access to the key using [CIDR notation](../auth/api-keys.md#cidr-format), and set an explicit expiration date so your key automatically stops working after that date. For this example, if you plan to do local testing first, you can remove the IP restriction by setting it to **0.0.0.0/0** and let it expire in **30 days**.
78
78
79
79
#### Add scripts for the user inventory support portal
80
80
@@ -300,7 +300,7 @@ The example app requires four methods to achieve its functionalities: [`List`](.
300
300
-**Read** for the `list` method.
301
301
-**Write** for `Create`, `Update`, and `Increment` methods.
302
302
303
-
When [creating an API Key](./api-keys.md) for this example, make sure you perform the following operations:
303
+
When [creating an API Key](../auth/api-keys.md) for this example, make sure you perform the following operations:
304
304
305
305
1. From the **Select API System** menu in the **Access Permissions** section, select **Ordered Data Stores**.
306
306
@@ -309,7 +309,7 @@ When [creating an API Key](./api-keys.md) for this example, make sure you perfor
309
309
1. Click the **Select Experience to Add** dropdown and select the target experience.
310
310
2. In the **Experience Operations**, expand the dropdown to select **Read** and **Write** operations.
311
311
312
-
1. In the **Security** section, explicitly set IP access to the key using [CIDR notation](./api-keys.md#cidr-format), and set an explicit expiration date so your key automatically stops working after that date. For this example, if you plan to do local testing first, you can remove the IP restriction by setting it to **0.0.0.0/0** and let it expire in **30 days**.
312
+
1. In the **Security** section, explicitly set IP access to the key using [CIDR notation](../auth/api-keys.md#cidr-format), and set an explicit expiration date so your key automatically stops working after that date. For this example, if you plan to do local testing first, you can remove the IP restriction by setting it to **0.0.0.0/0** and let it expire in **30 days**.
0 commit comments