42 OAuth Integration
Connect 42 to your application without building and maintaining the OAuth flow.
42 is a global network of coding schools. Each user connects their own 42 account through your OAuth app. Pathfix manages the authorization flow, stores and refreshes their tokens, and authenticates the requests your application makes to the 42 API. What your integration does with that access is up to your code.
How Pathfix helps
- 01
OAuth authorization
Pathfix runs the authorization flow with your 42 OAuth app, so users approve access on 42’s own consent screen.
- 02
Token management
Each user’s access and refresh tokens are stored by Pathfix rather than in your application.
- 03
Token refresh
Where 42 issues refresh tokens, Pathfix refreshes them as they expire, so connections keep working after the first authorization.
- 04
Authenticated API passthrough
Your application sends 42 API requests through Pathfix, which adds the connected user’s credentials before passing them on to 42.
You own the 42 OAuth application and its credentials, and your code implements the API logic.
POST https://labs.pathfix.com/oauth/method/42org/callHow to get started
- 1
Register your app with 42
Create an app in 42’s developer settings to get a Client ID and Client Secret. When asked for a redirect URI, enter
https://labs.pathfix.com/integrate/command. - 2
Add the credentials in Pathfix
In your Pathfix account, add an application, select 42 from the providers and enter the Client ID and Client Secret.
- 3
Choose your scopes
Add only the scopes your integration needs. 42’s developer documentation lists what each scope allows.
- 4
Test the connection
Use Test Connection to connect an account in the API Playground and run a sample call.
- 5
Let your users authorize
Add the connect step to your app. Each user signs in to 42 and approves the scopes you requested.
- 6
Call the 42 API
Send requests through the Pathfix passthrough API using the provider reference
42org.
