API Keys

šŸ“˜

The API key is a unique identifier used to integrate with Reteno and authorize requests. It provides access to your Reteno account data, so it must be kept secure. The Reteno API supports Basic HTTP Access Authentication method with the API key used as the password.

To authorize:

  1. In the Username field, enter any value.
  2. In the Password field, enter your API key.

Example of API key authorization in the Postman application:

Postman Authorization tab with Basic Auth type showing the Username and Password fields highlighted

Creating a Key

To generate an API key:

  1. Go to your profile → Settings → API.

  2. Click New key.

Account menu open with Settings highlighted, showing the API Keys page and New key button highlighted behind it
  1. In Description, enter the name of an application or a site, where you want to use the key to access your Reteno account.

  2. Open the dropdown menu and select the access rights for the API key.

Add a key panel with a description entered and the access rights list highlighted below the access rights dropdown
ā—ļø

The access rules apply to all method versions (/v1, / v2, etc.) unless otherwise specified.

  1. To set up several integrations, create a key for each. You can create several keys with different access rights for the same account.

You can find all the API keys in the API tab. Each key shows the following information:

A. Key number
B. Key description
C. Key status (enabled/disabled)
D. Accesses rights
E. Creation date and time
F. Who created

API Keys list showing a key row labeled A key number, B description, C status toggle, D access rights, E creation date, F creator

Access Rights

Access to Reteno resources through an API key is set up at the key creation stage.

You can give full access to all Reteno API resources and methods by choosing Full access to API. Or you can limit access rights by choosing:

  • Access to events
  • Access to events and contacts
  • Access to events and contacts (adding/updating)
  • Access to messages
Access rights dropdown expanded showing Full access to API, Access to events, Access to events and contacts, and Access to messages options

Copying a Key

To copy your key:

  • Point to your key number to display the Copy icon.
  • Click Copy.
API Keys page with the copy icon next to a key number highlighted in red

Enabling or Disabling a Key

When you create your key, it becomes enabled by default.

To disable your key:

  1. Click the toggle switch on the right side of your key.
API Keys page with the enable/disable toggle switch highlighted in red
  1. Click yes on the pop-up window.
Confirmation dialog asking Do you really want to disable key, with the yes button highlighted

Your key becomes disabled. The system blocks access to the API for this key.

ā—ļø

If you don’t use a key for 90 days, it is disabled automatically.

Editing a Key

To edit your key:

  1. Click the Options menu (...) on the right.
  2. Select Edit from the list.
Options menu open on a key row with Edit highlighted and Delete listed below
  1. Edit your description and/or access rights and click Save.

Your key settings update.

Edit a key panel showing description and access rights fields with the Save button highlighted

Deleting a Key

If a key is compromised, you can permanently delete it and create a new one for that application or site.

To delete a key:

  1. Click the Options menu (...) on the right.
  2. Select Delete from the list.
Options menu open on a key row with Delete highlighted and Edit listed above
  1. Click yes to confirm.
Confirmation dialog asking Do you really want to delete key, with the yes button highlighted

The deleted key is removed from the list of API keys.

API Key Security

The API keys provide access to all the data of your Reteno account. Follow the rules below when working with API keys:

ā—ļø

Important

Do's:

  • Keep your API keys secure, like passwords.
  • Periodically check you account for suspicious activity.

Don'ts:

  • Do not show your API key in screenshots or videos. Remove it completely.
  • Do not email your API key; it could fall into the wrong hands.
  • Do not wait if your key is misused. Disable it and create a new one.