Mercury

The platform reads your Mercury organization’s users through MercuryAPIso that you can check who has access.

Attention

Use a Read only APItoken, and paste it with its prefix secret-token:. the platform sends the token as Authorization: Bearer <token>, which matches the form Mercury Documents: Authorization: Bearer secret-token:.... Read and write The token is rejected from any IP address outside the white list it requires, and a Custom The token can only call the domains assigned when it was created, so none reliably reaches the user’s endpoint.

Prerequisites

• the platform organization administrator access
• A Mercury user with permission to create tokensAPI. An administrator on the Mercury account controls this permission, and a user without it sees no way to create a token
• The Mercury organization you want to review. A token is linked to the organization in which it is created, so go to that organization before opening its settings

Collected Fields

the platform field	Mercury field	Notes
Name	firstName, lastName	Returns to the email address when both are empty
Email	email
Role	organizationRole	administrator devine Administrator, bookkeeper devine Contabil, customUser devine Utilizator Custom, cardOnlyUser devine Utilizator Card Only, iar employee devine Angajat.
Admin	organizationRole	Showed as administrator when organizationRole is administrator
Status	Not supported
MFA	Not supported
Last login	Not supported
External ID	userId	Stable ID used to track your account through reviews
Created at	Not supported

Mercury returns each member of the organization on a single endpoint. the platform passes a record that arrives without an email address.

Step 1: Create a token only for reading

1. In Mercury, click on your organization in the upper left, click All Settings, and open Tokens in the left navigation.
2. Click Create an API Token, enter a Nickname such as Probo Access Review, setting Permissions to Read only, then click Create Token. A Read only Token can get all available data on the account and does not require a white list of IPs.
3. Copy the token, including its prefix secret-token: and store it securely.

Step 2: Connect in the platform

1. On the platform, go to Access Reviews > Sources > Add Source.
2. Find Mercury, click API KeyHold it in your hand and click Connect.

The Mercury user endpoint does not carry the name of the organization, so the source retains the generic name MercuryThe platform attracts your organization’s users to your campaigns.

Troubleshooting

• Token rejected. Put the token with its prefix secret-token:, as the platform sends it as Authorization: Bearer <token>. A sandbox token is also rejected: the platform calls api.mercury.com, and a token created in the sandbox belongs to the separate environment ___ZBT_I18_RUNTIME_BLOCK_193___.
• The Tokens page does not provide any way to create a token. The registered user does not own the permission. An administrator on the Mercury account can grant it or create the token instead.
• No users appear, or the wrong ones do. A token is linked to the organization in which it was created, so create it from All Settings > Tokens the page of the organization you want to review. a Custom Also, the token only touches the domains assigned to the creation, and these cannot be edited later.
• Source stops synchronization after a period of silence. Mercury deletes a token that remains unused for 45 days, and email accounts are managed seven days in advance.