RunSignUp supports OAuth2 authentication for secure API access. OAuth2 allows your application to access user data without requiring users to share their credentials with your application.
RunSignUp implements the OAuth2 Authorization Code flow with PKCE (Proof Key for Code Exchange) support for enhanced security:
| Scope | Description |
|---|---|
rsu_api_read |
Read access to RunSignUp API resources. |
rsu_api_write |
Write access to RunSignUp API resources. |
Once you obtain an access token, include it in the Authorization header of your API requests:
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9...For complete implementation details including all endpoints, parameters, request/response formats, and error handling, see the OAuth2 OpenAPI Specification.
Ready to implement OAuth2 authentication? Start with the OAuth2 Developer Guide for step-by-step instructions, or view the OpenAPI specification for detailed technical documentation.
RunSignUp supports PKCE (Proof Key for Code Exchange) for enhanced security, particularly recommended for public clients such as mobile applications and single-page applications that cannot securely store client secrets.
| Token Type | Lifetime | Usage |
|---|---|---|
| Access Token | 1 month (2,592,000 seconds) | Include in API request Authorization headers. |
| Refresh Token | 20 years | Use to obtain new access tokens. |
| Authorization Code | 5 minutes | Exchange for tokens immediately after receiving. |
