Skip to main content

How to Retrieve a User's API Access Key (CRM)

This guide explains how to locate a user's unique API Access Key within Dazos CRM. These keys are required to authenticate secure connections between the CRM and external integrations or custom API requests.

Updated over 2 months ago

Overview

Before You Begin

  • Admin Access: You must have Administrative permissions to access the User Management section.

  • Security Warning: Each user has only one unique Access Key. Treat this key with the same level of security as a password; never share it in public forums or unencrypted emails.


Steps

  1. Access Settings: Log in to your Dazos CRM instance and click the Settings (gear icon) on the left-hand navigation bar.

  2. Navigate to User Management: Within the Settings menu, locate the User & Access Management section and click on Manage Users.

  3. Select the User: Find the specific user whose key you need to retrieve from the list. Click on their User Name to open their full profile.

  1. Locate the Access Key: Find the field labeled Access Key. This contains the unique alphanumeric string assigned to that user.

  1. Copy the Key: Highlight the string and copy it to your clipboard for use in your integration or API request.


Verification / Expected Result

A successful retrieval is confirmed when you can see a long alphanumeric string in the Access Key field. This key is immediately active and ready for use in external configurations.

Troubleshooting / Common Errors

  • Access Key is Blank: In rare cases, if a key has not been generated, clicking "Edit" and then "Save" on the user profile will usually trigger the system to generate a new unique key.

  • Permission Denied: If you cannot see the "User Advanced Options" section, you do not have sufficient administrative privileges. Contact your System Administrator to update your role permissions.

  • Invalid Key Error: If an integration rejects the key, ensure there are no accidental spaces at the beginning or end of the string when you copied it.

Did this answer your question?