Does anyone know if it is possible to setup a new account for a mobile app but not send out an email to them until later? basically I want to setup the account and then ensure that everything is working before I send out an email. This is for the CEO of a company and I want to ensure that everything is working beforehand. is this possible?
Hey @neilbalthaser ,
When you invite users to join your organization, they typically receive an email to create their accounts. However, you can create user accounts without sending email invitations by using the Retool API. Once you set up the account through the API, you can test everything before deciding to send an email to the user.
To handle this scenario properly, make sure you check the relevant APIs and documentation regarding user management to ensure your implementation aligns with best practices. Remember to handle any security considerations when managing user accounts and access.
@WidleStudioLLP thank you very much. I have reviewed the api docs but there are some questions I still have. can you share more with me about the best practices you refer to as it relates to the api? also I assume that 'create new user invite' end point: user_invites (post) actually sends the invite out correct?
- Security: Ensure that you authenticate API requests properly and limit API key access to trusted environments. Protect sensitive information and follow OAuth best practices if applicable.
- Rate Limits: Be aware of any rate limits imposed by the Retool API to avoid hitting those limits during high usage.
- Error Handling: Implement error handling in your API calls to manage failed requests gracefully. This includes handling scenarios such as invalid inputs and authentication failures.
- Test Thoroughly: Before deploying any automation or user onboarding processes using the API, conduct thorough testing to ensure everything operates as expected.
- Audit Logs: Utilize Retool's audit logs to track actions performed via the API for accountability and troubleshooting purposes.
Regarding the endpoint for creating a new user invite, the Create a New User Invite API call (POST /user_invites
) indeed sends out an invitation email to the specified email address. If you want to avoid sending an email immediately but still create a user account, you'll need to use a different approach without invoking this endpoint until you are ready.
For detailed implementation, refer to the API documentation to ensure accurate payload structure and response handling.
is it possible to: create the user account and then instruct the user to download the mobile app and will they be able to log into the app using their new account or is there an activation step that needs to occur before they can use their account?
Yes, it is possible to create a user account through the Retool API, and then instruct the user to download the mobile app. Once their account is created, they will be able to log into the mobile app using their new account credentials.
However, please note that if you used the POST /user_invites
endpoint to create the account, the user will need to complete the activation process via the email invitation sent to them. If you bypass the email invitation process and create the account directly, ensure that you allow the user to set their password or confirm their account in any required way.
If the mobile app requires email verification or any activation step, that step must be completed before they can fully access the app. Be sure to check the relevant documentation or your organization's configuration settings to understand any specific requirements related to account activation or password settings.
and can all subscription tiers access all the endpoints? I cannot see in the documentation if there are any limitations for example I do not see user scope for my api key.
Access to certain API endpoints and features in Retool may vary depending on your subscription tier. The documentation may not explicitly state limitations for each endpoint, but generally, higher tiers provide more granular controls and features.
If you do not see a user scope for your API key, it could be due to the subscription level or the specific settings of your Retool organization. You should check with your organization admin or consult the Retool support team for clarification on the specific capabilities your current subscription grants regarding API access.
For detailed information about the capabilities and limitations per subscription tier, visit the Retool pricing page or refer to any official communications received during your subscription setup.
I wish Retool were a bit more transparent/clear on things like this. There is scant documentation anywhere that I can find easily that clearly delineates what api end points are available to what subscription levels. I end up wasting a lot of time digging trying to figure out how to work around something that would normally be pretty straightforward on any other platform.