Send activation emails in bulk for users with a provisioned status by configuring a Postman collection and executing an API call with a comma-separated values file. 

NOTE: Postman is a third-party tool. Okta is not responsible for any changes to the application, and Support cannot troubleshoot issues with it. Test the Runner with a small batch of users before running the call for all users.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• User Administration
• Postman
• API

What are the prerequisites for sending bulk activation emails?

Prepare the environment for bulk reactivation emails by configuring Postman, importing the Okta API collections, and creating a comma-separated values file.

• Postman configured for the org environment as described in Configuring Postman for Okta API Access
• An Okta org
• Okta API collections imported into Postman
• A CSV file with the rules that require modification

How are activation emails sent in bulk using Postman?

Generate a CSV file of provisioned users, configure a POST request in a new Postman collection, and execute the collection runner to send the activation emails in bulk.

Follow the video or steps below to perform a bulk send of activation emails via Postman.

1. Create a CSV file containing the logins of the users that require reactivation.
   • The CSV file can be generated by running the Okta Password Health Report from the Admin Console by navigating to Reports > Reports > Okta Password Health Report and selecting the target users.
   • NOTE: This operation only functions for users with a PROVISIONED status.
2. Create the following call inside Postman:
   

   POST /api/v1/users/{{userId}}/lifecycle/reactivate?sendEmail=true

3. Create a new collection in Postman and add only the required call inside it.
4. Format the CSV file to include a Login column containing the user identifiers.
   • NOTE: Other columns may remain in the CSV file. Ensure the Login column is present, as the API call is configured to use the Login variable in step 2.
     
     
   • 
5. Open Postman Runner and configure it with the new collection, environment, iterations, and CSV file, then execute the run.
   • Add a delay between calls if there are many requests to avoid hitting the API Rate Limit.

6. Confirm the API call execution returns a 200 OK success response.

Related References

• Test the Okta REST APIs using Postman
• Why You Should Migrate to OAuth 2.0 From Static API Tokens
• Implement OAuth for Okta
• Okta Public API Collections
• OAuth 2.0 Scopes
• Implement the Authorization Code with PKCE flow
• Okta API Error Codes and Descriptions
• Using CSV and JSON Data Files in the Postman Collection Runner
• Core Okta API