Overrides
Instructions on how to override the default configuration of Reclaim Protocol's InApp SDKs
Get Started
Many configurations in the InApp SDKs can be overridden. For example, a different attestor can be used, or we can update app info that appears in the verification flow.
Reclaim Protocol InApp SDK has some overrides which are restricted and require a capability access token. This can be made available upon request. Contact our team to discuss implementation details.
The setOverrides
method allows you to customize various aspects of the Reclaim InApp SDK's behavior. This documentation covers all available override options and their usage.
Basic Usage
For example of how to use overrides, see:
Available Override Options
Provider Configuration
Configure custom provider settings:
or
- The JSON string or url must point to a valid provider configuration that follows the provider schema.
Provider Schema
The Schema of Reclaim HTTP Provider used by Reclaim Protocol's InApp SDKs
Examples of provider schema can be found as provider configurations in the https://api.reclaimprotocol.org/api/providers/${provider_id}
http api. For example, Devtool's Http Api for Github Username Provider.
Note:
- These examples have a different structure where the provider configuration is nested under a 'providers' key, rather than being the root object. Therefore, the
https://api.reclaimprotocol.org/api/providers/${provider_id}
http apis cannot be used as direct parameters for provider overrides by url in this SDK. - For use with
jsonString
, provider the value of the 'providers' key in thejsonString
parameter.
Logging Configuration
Control SDK logging behavior:
App Information
Customize the application's identity during claim creation:
Feature Options
Configure SDK behavior and features:
Setting all values to non-null values will prevent the SDK from fetching feature settings from reclaim protocol APIs server.
Session Management
Handle session-related events:
Complete Example
Here's a full example showing all available override options:
Best Practices
- Set overrides before calling
startVerification
- Consider setting overrides only once.
- Handle all session management events appropriately.
- Use appropriate timeout values for your use case
- Test thoroughly when modifying default behaviors
Notes
- All override options are optional
- Overrides persist until explicitly changed or cleared with
clearAllOverrides
- Some features may require specific override combinations to work properly
- Overriding all options will cause the app to not use any reclaim protocol APIs.