Venminder

Record your Venminder connection as vendor procurement evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Venminder:

   1. Ask your Venminder Relationship Manager or Account Executive to enable the Venminder API feature for your account (it is not part of the standard solution and needs configuration by the Venminder Software team).
   2. Make sure the user creating the key is an Admin with the API Key Manager role: click the silhouette icon in the top right corner and select Admin Panel, open the User Roles tab, choose Edit from the Actions menu for the user (or +Add User for a new one), check API Key Manager, and click Submit.
   3. Select Admin Panel from the user in the header, then click System Settings.
   4. Scroll to the Manage API User section and click Add API User.
   5. In the pop-up, enter the API User Name, Description, Expiration Date and API Permissions, then click Submit.
   6. Record the Client Secret (and the Client ID) shown in the pop-up. The Client Secret cannot be displayed again after the pop-up is closed.
   7. Exchange the Client ID and Client Secret for an access token at Venminder's authentication server (OAuth 2.0 Client Credentials grant): Venminder documents an HTTP POST to https://login.venminder.com/connect/token with grant_type=client_credentials and scope=venminderApi, using the API key and client secret as the Basic credentials. The resulting bearer token is the API token. Venminder's Postman collection uses a POST Venminder Token call for this, with the API key and secret as the Username and Password values.

   Where to find the other values:

   • Base URL (optional): Venminder's API (Venminder OpenApi v1) is documented in Swagger at https://rsd.venminder.com/swagger, with endpoints under /api/v1/.

   Venminder shows the secret only once, so copy it before you leave the page.

   Venminder's public documentation does not cover every step.

   Venminder's API is an add-on that Venminder must enable before the API Key Manager role and Manage API User section can be used. Each API key consists of a Client ID, Client Secret and Expiration Date, and a customer may have several Client IDs. A user with only the API Key Manager role sees just the Manage API Keys section of the Admin Panel. Access tokens expire after a timeout period and must be requested again with the Client ID and Client Secret. Partial because the names of the API Permissions options appear only in screenshots, so no specific read-only permission is named,. The developer portal (developers.venminder.com) renders client-side; its text was read from the page data the portal itself loads (Getting Started: About the API Key, API Key Manager Role, Adding an API Key, Connecting to the API; and The Venminder API). Verification 2026-10-07: removed the unsupported advice to choose read-only permissions (the docs do not name the API Permissions options); added the token endpoint (https://login.venminder.com/connect/token, scope venminderApi) from the portal's Token page. The docs also mention an optional Create Access Token check box for a long-running token, which Venminder recommends against.

   Source: developers.venminder.com, rsd.venminder.com, rsd.venminder.com, checked 2026-10-07.

2. On Compliance › Connectors, open Venminder, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Venminder yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Vendor Procurement connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks