Repository navigation
Authentication overview and OAuth for apps guide - #1712
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
capy-ai
Bot
changed the title
Only a refresh token revokes the whole connection; an access token sent to /revoke ends that access token alone. A refresh token used twice revokes the connection outright, including the tokens the first refresh returned. Both match the grant RPCs that back REST connections. Co-Authored-By: Claude <noreply@anthropic.com>
capy-ai
Bot
changed the title
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents every way to authenticate with Firecrawl, and adds the full guide for apps that let users connect their own Firecrawl account to the REST API.
Authentication (new page,
authentication.mdx). A "Which should I use?" table compares the four options, with a short section on each:Bearer fc-...on the REST API./v2/mcpwith the key as a header./v2/mcp-oauth, browser sign-in, used automatically by the ChatGPT and Claude connectors. Each connection gets its own key, and the tokens only work on MCP.resource=https://api.firecrawl.dev/,fco_tokens on the REST API, its own key per connection, revocable under Connected apps, refresh rotation, and reuse revokes the connection.It sits in a new API Reference group, "Authentication", next to the OAuth guide (which replaces the old "OAuth" group).
OAuth for apps (
oauth.mdx). Covers discovery, client registration (Dynamic Client Registration or a Client ID Metadata Document), the authorize request with PKCE, code exchange, calling the API with anfco_token, refresh token rotation, revocation and errors. It describes production as it works today:Cross-links. The API introductions (v2 and the current one), MCP "For Humans" and the MCP "Add an API key" section now point to the Authentication page. The MCP page's "MCP settings" link now reads "Connected apps in Settings", matching the dashboard heading.
English pages only; translations come from the localization pipeline.
mint broken-linksreports no broken links in the changed pages; the only hit in them is the pre-existing/llms.txtlink in the v2 introduction.