This article describes how to send Activation Emails in bulk for users with a provisioned status via Postman.

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

• User Administration
• Postman
• API

Prerequisites 

• Postman configured for the org environment as described in How to Integrate Postman with Okta 
• An Okta Org
• Okta API collections imported into Postman
• A CSV file with the rules that should be modified

If Admins have many users that need to be reactivated from the org, Admins can leverage Postman to do so. If not done so already, please follow How to Integrate Postman with Okta to set up Postman and configure API calls leveraging OAuth. 

Below are the steps that need to be performed to run a Bulk reactivation of users via Postman:

1. Create a CSV with the users' logins that Admins want to reactivate.

• • This CSV can be created by running the Okta Password Health Report from the Admin UI (Reports >  Reports >  Okta Password Health Report) and selecting the users that need to be reactivated.

1. • NOTE: This operation can only be performed on 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 call needed inside it.

4. Modify the CSV in order to look like the screenshot below.

• • NOTE: Admins may keep the other columns in the CSV. Ensure the Login column is present as the API call is configured to use Login in step #2.

5. Open Postman Runner, select the collection, environment, iterations (if there are many requests, Admins can add a delay between calls to avoid hitting the API Rate Limit), and the CSV file, and then run the call.
    

6. Success result - 200 OK:
    

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
• Import a Postman Collection
• 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