Freedom ID is a unified account system for accessing services provided by the Freedom Group of Companies and supported third-party websites or applications. This API enables configuring a single sign-on experience for your website or mobile application.
The Freedom ID API offers the following benefits:
Unified Authorization: Users can log into your website or application using their existing Freedom ID account, removing the need for new account registrations and forms.
Data Transfer: With user consent, necessary data can be retrieved for account creation or updates.
Web Authorization: Allows login via Freedom ID widgets or buttons on your site.
Mobile Authorization: Integrates SDKs for mobile devices to facilitate seamless login if users are already signed into Freedom ID on their devices.
To work with the Freedom ID API, a partner service needs credentials (Login and Password). These can be obtained by contacting the product support team via email: support@freedompay.uz.
Subject: Request for Service Integration with Freedom ID API
Dear Freedom ID Support Team,
My name is [Your Name], representing the platform [Your Company Name]. We aim to integrate our service with the Freedom ID API for unified user authorization.
Service Name: [Your Service Name]
Platforms: [Platform List]
Contact Details:
- Name: [Responsible Person's Name]
- Position: [Position]
- Email: [Email Address]
- Phone: [Phone Number]
When a user consents to provide the requested access rights, Freedom ID redirects the user to the specified redirect_uri with an appended authorization_code parameter. This one-time code must be exchanged for an access_token and refresh_token for subsequent operations.
This method is used to refresh an expired access_token using a refresh_token. If the access_token has expired, the application can use the refresh_token to request a new set of tokens.
This method allows an application to obtain user information using a valid access_token. The response includes data that can be used for the application's user interface or other purposes.
This method retrieves personal and other analytical data about the client (user). Before making this request, the application must request the read.profile grant during the authentication link generation step. If the user consents and the grant is active, the profile data request is queued for processing.