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: fern/products/docs/pages/api-references/autopopulate-api-key.mdx
+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
@@ -20,10 +20,10 @@ API key injection can work in two different ways depending on your company's aut
20
20
***JWT Flow:** You handle the entire auth flow and just give Fern a JWT cookie
21
21
***OAuth Flow:** You give Fern access, and Fern directly initiates the OAuth handshake process
22
22
23
-
<AccordionGroup>
23
+
<AccordionGrouptoc={true}>
24
24
<Accordiontitle="JWT"toc={true}>
25
25
26
-
### How it works
26
+
### How the JWT flow works
27
27
28
28
To enable this feature, you need to configure authentication so that Fern can securely retrieve API keys for your users. The process works as follows:
29
29
@@ -87,7 +87,7 @@ The JWT should have a structure similar to:
87
87
88
88
</CodeBlocks>
89
89
90
-
## Setting up auto-populated API keys
90
+
####Setting up auto-populated API keys
91
91
92
92
-[ ] Reach out to Fern to get your secret key
93
93
-[ ] Send Fern the URL of your authentication page. This is where users will be redirected to after clicking the "Login" button in the API Explorer.
@@ -98,7 +98,7 @@ The JWT should have a structure similar to:
98
98
</Accordion>
99
99
<Accordiontitle="OAuth"toc={true}>
100
100
101
-
### How it works
101
+
### How the OAuth flow works
102
102
103
103
To enable this feature, you need to configure OAuth authentication so that Fern can securely retrieve API keys for your users through your OAuth provider. Here's how the process works:
104
104
@@ -107,7 +107,7 @@ To enable this feature, you need to configure OAuth authentication so that Fern
107
107
1. After successful authentication, your OAuth provider redirects back to Fern with an authorization code, which Fern exchanges for an access token at your token endpoint.
108
108
1. Fern uses this token to retrieve the user's API key and automatically populates it in the API Explorer.
109
109
110
-
### Setting up auto-populated API keys
110
+
####Setting up auto-populated API keys
111
111
112
112
To enable API key injection, you'll need to:
113
113
-[ ] Set up an authenticated account for Fern so Fern can authorize users on your behalf. Provide Fern with
0 commit comments