Answer: The flow uses PKCE: the partner backend generates a code_verifier and derives a code_challenge, redirects the admin to Devin's connect page, the admin confirms, Devin redirects a one-time code to the callback_url, and the backend exchanges the code plus code_verifier at the token endpoint to receive credentials. The one-time code has a 10-minute TTL and is single-use, and the outpost and service user are created only when the code is redeemed. Status: Confirmed Entry: tool/devin/integrations/outposts-partner-flow-overview Revision: 1 Digest: sha256:f9871536b9daf135 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:12:31Z Last changed: 2026-11-13T03:12:31Z Last verified: 2026-11-20T12:41:32Z Next check: 2026-11-21T12:41:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of code_verifier length | 43–128 characters | characters | [1] | 2026-11-20 code TTL | 10-minute TTL | | [1] | 2026-11-20 token endpoint | https://api.devin.ai/outposts/connection-token | | [1] | 2026-11-20 connect page URL | https://app.devin.ai/outposts/connect | | [1] | 2026-11-20 grant_type | authorization_code | | [1] | 2026-11-20 PKCE method | S256 | | [1] | 2026-11-20 token_type | bearer | | [1] | 2026-11-20 Sources: [1] Cognition. "Devin Outposts partner integrations". https://docs.devin.ai/cloud/outposts/partners.md Role: primary. Accessed: 2026-11-20T12:41:32Z Quote: "Generate a high-entropy, random **`code_verifier`**: 43–128 characters from the unreserved alphabet" (Supports: code_verifier length) Quote: "stores an encrypted, single-use code (10-minute TTL)" (Supports: code TTL) Quote: "curl -X POST "https://api.devin.ai/outposts/connection-token"" (Supports: token endpoint) Quote: "https://app.devin.ai/outposts/connect" (Supports: connect page URL) Quote: "--data-urlencode "grant_type=authorization_code"" (Supports: grant_type) Quote: "the unpadded base64url of the SHA-256 of the verifier (PKCE "S256")" (Supports: PKCE method) Quote: ""token_type": "bearer"" (Supports: token_type) Published: 2026-11-20T12:41:32Z Snapshot SHA-256: 8c89d2bfe4cbbb8d71c92043b5071f4653eeec19c4474760e984546ab2690267 (captured 2026-11-13T03:12:31Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:12:31Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:41:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:41:32Z Last attempt: 2026-11-20T12:41:32Z Notes and limitations: Extracted automatically from a single official source (section "Flow overview"). Related: https://latestn.com/tool/devin/integrations/outposts-partner-prerequisites What are the prerequisites for connecting Devin Outposts to a partner integration? https://latestn.com/tool/devin/integrations/pr-template-discovery-order What pull request template filenames does Devin look for, and in what order? https://latestn.com/tool/devin/integrations/register-devin-oauth-app How do I register Devin as an OAuth app in PagerDuty? https://latestn.com/tool/devin/integrations/native-integration-settings-location Where do I set up native integrations like Slack, Jira, and Linear in Devin? https://latestn.com/tool/devin/integrations/outposts-exchange-code-server-to-server How do I exchange the authorization code for Devin Outposts credentials server-to-server? https://latestn.com/tool/devin/integrations/outposts-integrations What partner integrations are available for Devin Outposts? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:12:31Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/integrations/outposts-partner-flow-overview/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/integrations/outposts-partner-flow-overview POST: https://latestn.com/dispute/tool/devin/integrations/outposts-partner-flow-overview with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/integrations/outposts-partner-flow-overview?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does the Devin Outposts partner integration authorization flow work? Revision 1, last verified 2026-11-20T12:41:32Z. https://latestn.com/tool/devin/integrations/outposts-partner-flow-overview (accessed 2026-11-21T09:59:38Z). @misc{LatestN_tool_devin_integrations_outposts_partner_flow_overview_r1, title = {How does the Devin Outposts partner integration authorization flow work?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/integrations/outposts-partner-flow-overview}}, note = {Revision 1; digest sha256:f9871536b9daf135; last verified 2026-11-20T12:41:32Z; accessed 2026-11-21T09:59:38Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/integrations/outposts-partner-flow-overview