[type or paste code here](https://api.web3auth.io/signer-service/api/feature-access?client_id=BJJM_EvyF1oRv4dy99K4oGXywP7uG51o0n3fZPBP5-vIKPd0mFJjt9OT_kfE1yL8x4ipfVtAVWtft6gblC7AmuE&network=sapphire_mainnet&is_wallet_service=true&enable_gating=true&is_whitelabel=true)
API endpoint still returning this issue. Upgraded my account to Growth plan. Web3auth purely being used for auth only. All settings in project reverted to default.
You’re still seeing a 403 Forbidden error from the feature-access API endpoint even after upgrading to Growth Plan.
Growth Plan features (wallet services/auth) are not being reflected in the modal.
Next Steps & Troubleshooting
Dashboard Check:
Double-check that your project in the Web3Auth Developer Dashboard is actually associated with the Growth Plan subscription.
Sometimes, if you have multiple projects, the upgrade may not have applied to the correct project/client ID.
Client ID Verification:
Ensure the clientId used in your code matches the one shown for your upgraded project in the dashboard.
Feature Activation Delay:
There can sometimes be a short delay (up to a few minutes) after upgrading before features are enabled. If you just upgraded, try logging out and back into the dashboard, and restarting your app.
Modal Configuration:
If you are using custom authentication or wallet services, make sure you have configured the necessary connections in the Authentication tab of your project dashboard, as described in the Custom Authentication docs.
Browser Console:
If possible, provide a screenshot of your browser console when the error occurs. This can help the support team trace the issue further.
If you’ve checked all of the above and the issue persists, please let us know:
If you are using any custom authentication providers (Google, JWT, etc.), which ones and how they are configured.
If you see any other errors in the browser console or network tab.
Thank you for your patience! The support team will review your details and help resolve this as soon as possible.
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours