RegisterLogin
DocsPricing
RegisterLogin
  • Getting Started
  • Introduction
  • Quick Start
  • SDKs
  • React
  • TypeScript
  • Next.js
  • Express
  • NestJS
  • Python
  • API Reference
  • Support and Resources
  • FAQ
  • Contact Support

AuthSafe

Product

HighlightFeatureIntegrationPricingFAQ

Company

AboutBlogContactSitemap

Developer

DashboardDocumentation

Legal

Terms & ConditionsPrivacyComplianceShippingCancellation

© 2026 AuthSafe. All rights reserved.

We value your privacy

This website uses cookies for anonymous analytics to help us improve your experience. No personal information is stored or shared. You can allow or reject analytics tracking at any time. See our Privacy Policy.

We use cookies for anonymous analytics. No personal info is stored. See our Privacy Policy.

APIs Overview

AuthSafe provides a complete OAuth 2.0 and OpenID Connect (OIDC) implementation for secure authentication and authorization. Our APIs are designed to be standards-compliant, developer-friendly, and production-ready.
OAuth 2.0
OpenID Connect
REST API
Standards Compliant

Base URL

All API endpoints are hosted at:
https://identities.authsafe.in

Core APIs

Authentication

OAuth 2.0 and OpenID Connect flows for user authentication. Learn about authorization codes, tokens, and secure authentication.

Learn More

API Endpoints

Complete API reference for all authentication endpoints including authorization, token exchange, user info, and more.

View Reference

Authorization

Fine-grained access control using OAuth 2.0 scopes, role-based access control (RBAC), and custom permissions.

Learn More


Authentication Flow

AuthSafe implements the OAuth 2.0 authorization code flow with PKCE (Proof Key for Code Exchange) for maximum security.
1. User initiates login in your application
2. Application redirects to AuthSafe authorization endpoint
3. User authenticates and grants consent
4. AuthSafe redirects back with authorization code
5. Application exchanges code for tokens
6. Application uses access token to access protected resources
7. Application refreshes tokens when needed
PKCE Required
All authorization code flows must use PKCE with the S256 method. This prevents authorization code interception attacks and is mandatory for all applications.

Token Types

AuthSafe issues different types of tokens for different purposes:
Access Token

JWT-based token used to access protected resources. Contains claims about the user and their permissions. Expires after 1 hour by default.

JWT Format
RS256 Signed
1 hour expiry
ID Token

JWT containing user identity information. Issued by OpenID Connect and contains claims like sub, name, email, and profile picture.

OIDC Standard
User Info
JWT Format
Refresh Token

Long-lived opaque token used to obtain new access tokens without re-authenticating. Stored securely server-side and can be revoked at any time.

Opaque Format
Long-lived
Revocable

Standards Compliance

AuthSafe implements the following specifications:
OAuth 2.0 (RFC 6749)

Authorization framework for delegated access

OpenID Connect Core 1.0

Identity layer built on OAuth 2.0

PKCE (RFC 7636)

Proof Key for Code Exchange

Token Introspection (RFC 7662)

Token validation and inspection

Token Revocation (RFC 7009)

Token lifecycle management

JWT (RFC 7519)

JSON Web Tokens


Security Features

PKCE Required

All authorization code flows require PKCE with S256 method to prevent authorization code interception attacks.

RS256 Token Signing

All tokens are signed with RSA-256 using organization-specific keys. Verify signatures using our JWKS endpoint.

HTTPS Only

All API endpoints require HTTPS. HTTP requests are rejected to ensure secure communication.

Token Revocation

Refresh tokens can be revoked at any time through the revocation endpoint for enhanced security.


Rate Limiting

API endpoints have rate limits to ensure platform stability:
Rate Limit Headers
All responses include rate limit headers:
  • X-RateLimit-Limit: Maximum requests allowed
  • X-RateLimit-Remaining: Remaining requests
  • X-RateLimit-Reset: Unix timestamp when limit resets
If you exceed the rate limit, you'll receive a 429 Too Many Requests response.

Next Steps

Quick Start

Get started with AuthSafe in minutes using our step-by-step integration guide.

View Quick Start →

Authentication Guide

Learn about OAuth 2.0, OpenID Connect, and how AuthSafe handles authentication.

Learn About Authentication →

React SDK

Use our official React SDK for seamless integration with your React applications.

View React SDK →