Looking for more powerful ways to scale your processes with API? Meet our automation token! Unlike your typical user token, this one comes with a longer expiration period and higher rate limits.

https://api.multilogin.com/workspace/automation_token?expiration_period=<string>

In this article, we will show you how to use the automation token in the target workspace: both as an account owner and as a team member. 

Steps to generate

Workspace owner

1. Complete all three steps from this article, including “Using the bearer token”: they will allow you to sign in correctly
2. Go to the “Profile Access Management” folder in your Postman workspace and select “GET Workspace Automation Token”
3. In the “Params” tab, fill in the value for the expiration_period parameter: this will determine how long the token will last for (check the “Description” column for example values)
4. Click “Send” to execute the request
5. When the token expires, send another request to generate a new one

If you change the master account password, the currently active automation tokens will expire.

 

 

 

Team member

1. Sign in to your team member account using the “POST User Signin” endpoint
2. Copy the refresh_token value from the response

3. Go to the "Profile Access Management" folder in your Postman workspace and select “POST User Refresh Token”
4. Go to the “Body” tab and fill in the following values:
   1. email: Your team member email
   2. refresh_token: The value from step 2
   3. workspace_id: The ID of the target workspace
5. Go to the "Tests" section, add the following code and save the changes:

const response = pm.response.json() 
const token = response['data']['token'] 
pm.collectionVariables.set("token", token)

6. Click "Send" to execute the request
7. Repeat steps 2 to 4 of the “Workspace owner” section

If you change the master account password, the currently active automation tokens will expire.

 

 

 

Troubleshooting

After sending the request correctly, you should see response code 200, which means success.

If you encounter any issues, you might get the following error codes:

• 401 — Incorrect JWT token: This means your sign-in token has expired, or you haven't added the bearer token to your request. To fix this in Postman, sign in again using the “POST User Signin” endpoint and ensure you follow all steps, including obtaining the bearer token.
• 400 — Invalid refresh token: This indicates you've entered the wrong value for refresh_token. Double-check the description column for examples.
• 400 — Incorrect expiration period: This indicates you've entered the wrong value for expiration_period. Double-check the “Description” column for examples.

Video guide