Skip to content

Commit 72639b6

Browse files
fix(realtimekit): changed realtimekit api reference
1 parent c4df2ca commit 72639b6

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/content/docs/realtime/realtimekit/getting-started.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ You can also view and manage your apps directly in the [Cloudflare RealtimeKit d
7171
### Create RealtimeKit App
7272

7373
Once you have your API token ready, the next step is to create a RealtimeKit app.
74-
You can use our [API reference](/api/resources/realtimekit) for details on creating an app, or use the following sample cURL command:
74+
You can use our [API reference](/api/resources/realtime/realtimekit/) for details on creating an app, or use the following sample cURL command:
7575

7676
```bash
7777
curl --location 'https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/realtimekit/kit/apps' \
@@ -84,7 +84,7 @@ curl --location 'https://api.cloudflare.com/client/v4/accounts/<account_id>/real
8484

8585
For more about apps and their role, see the [RealtimeKit Concepts guide](/realtime/realtimekit/concepts).
8686

87-
#### Sandbox vs Production App
87+
### Sandbox vs Production App
8888

8989
It’s best practice to create separate apps for your production and staging environments. This helps you test changes safely without impacting your live environment.
9090

@@ -94,7 +94,7 @@ You are free to choose any app name that fits your workflow.
9494
### Create Meeting
9595

9696
After creating an app, you can create a new meeting.
97-
Refer to the [API reference](/api/resources/realtimekit) for endpoint details.
97+
Refer to the [API reference](/api/resources/realtime/realtimekit/) for endpoint details.
9898

9999
```bash
100100
curl --location 'https://api.cloudflare.com/client/v4/accounts/<account_id>/realtime/realtimekit/kit/<app_id>/meetings' \
@@ -127,7 +127,7 @@ curl --location 'https://api.cloudflare.com/client/v4/accounts/<account_id>/real
127127
--header 'Authorization: Bearer <api_token>'
128128
```
129129

130-
You can create new presets using the [API reference](/api/resources/realtimekit) or via the [RealtimeKit dashboard](https://dash.cloudflare.com/?to=/:account/realtime/realtimekit/kit).
130+
You can create new presets using the [API reference](/api/resources/realtime/realtimekit/) or via the [RealtimeKit dashboard](https://dash.cloudflare.com/?to=/:account/realtime/realtimekit/kit).
131131

132132
Keep the preset name handy for the next step.
133133

@@ -159,7 +159,7 @@ curl --location 'https://api.cloudflare.com/client/v4/accounts/<account_id>/real
159159
- `custom_participant_id`: A unique identifier for the participant within this meeting. If you call the Add Participant API again with the same `custom_participant_id` for the same meeting, RealtimeKit will not create a duplicate participant but will instead return the existing participant's token. This can be any unique string, such as a UUID. **Do not use email addresses or personally identifiable information (PII)** here to proactively avoid sharing sensitive details. This UUID will be available in SDK for you to use later on.
160160

161161
The response will include an auth token, which is required for the participant to join the meeting.
162-
See the [API reference](/api/resources/realtimekit) for more details on participant management.
162+
See the [API reference](/api/resources/realtime/realtimekit/) for more details on participant management.
163163

164164
### Try the RealtimeKit Sample UI with Participant Auth Token
165165

0 commit comments

Comments
 (0)