Skip to content

Move enable native API callout as step #2679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Oct 8, 2025
+18 −11
Merged

Move enable native API callout as step #2679

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2170205
Move enable native API callout as step
SarahSoutoul Oct 7, 2025
02d320b
Changes post feedback
SarahSoutoul Oct 8, 2025
845e9ec
Merge branch 'main' into ss/DOCS-11023
SarahSoutoul Oct 8, 2025
57bd0c5
Merge branch 'main' into ss/DOCS-11023
SarahSoutoul Oct 8, 2025
33a9fc9
Fix linting
SarahSoutoul Oct 8, 2025
83df521
Merge branch 'main' into ss/DOCS-11023
SarahSoutoul Oct 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/_partials/native-api-callout.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
> [!IMPORTANT]
> Ensure that the Native API is enabled to integrate Clerk in your native application. In the Clerk Dashboard, navigate to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page.
## Enable Native API
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you think about keeping the heading out incase we want to reuse the text in places that don't have a heading or require a different heading level

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that sound good! Will make the change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change made here: Changes post feedback


In the Clerk Dashboard, navigate to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page and ensure that the Native API is enabled. This is required to integrate Clerk in your native application.
4 changes: 2 additions & 2 deletions docs/getting-started/quickstart.android.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ sdk: android
]}
/>

<Include src="_partials/native-api-callout" />

<Steps>
<Include src="_partials/native-api-callout" />

## Create an Android Project

1. Create a new Android project in Android Studio using the **Empty Activity** template. This tutorial uses `MyClerkApp` as the app name. If you choose a different name, be sure to update any code examples accordingly to match your app's name.
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/quickstart.chrome-extension.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ sdk: chrome-extension
]}
/>

<Include src="_partials/native-api-callout" />

<Steps>
<Include src="_partials/native-api-callout" />

## Configure your authentication options

When creating your Clerk application in the Clerk Dashboard, your authentication options will depend on how you configure your Chrome Extension. Chrome Extensions can be used as a popup, a side panel, or in conjunction with a web app. Popups and side panels have limited authentication options. [Learn more about what options are available.](/docs/reference/chrome-extension/overview#authentication-options)
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/quickstart.expo.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,9 @@ sdk: expo
]}
/>

<Include src="_partials/native-api-callout" />

<Steps>
<Include src="_partials/native-api-callout" />

## Install `@clerk/clerk-expo`

The [Clerk Expo SDK](/docs/reference/expo/overview) gives you access to prebuilt components, hooks, and helpers to make user authentication easier.
Expand Down
6 changes: 3 additions & 3 deletions docs/getting-started/quickstart.ios.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ icon: "clerk",
]}
/>

<Include src="_partials/native-api-callout" />

<Steps>
<Include src="_partials/native-api-callout" />

## Create an iOS Project

To get started using Clerk with iOS, create a new project in Xcode. Select SwiftUI as your interface and Swift as your language.
Expand All @@ -29,7 +29,7 @@ icon: "clerk",

## Add your Native Application

Add your iOS application to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page in the Clerk dashboard. You will need your iOS app's **App ID Prefix** and **Bundle ID**.
Add your iOS application to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page in the Clerk Dashboard. You will need your iOS app's **App ID Prefix** and **Bundle ID**.

## Add associated domain capability

Expand Down