This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:what_is_my_api_key [2024/11/28 09:46] – [What is my API-Key?] bk | en:what_is_my_api_key [2025/02/27 09:53] (current) – bk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== What is my API-Key? ====== | + | ====== What is my API key? ====== | 
| - | API key is needed to authenticate your requests via REST. Navigate to //Settings > API//. | + | An API key is needed to authenticate your requests via REST. Navigate to //Settings > API//. | 
| ===== REST ===== | ===== REST ===== | ||
| Line 8: | Line 8: | ||
| In clients that are enabled for omnichannel and use REST, existing keys are listed in the " | In clients that are enabled for omnichannel and use REST, existing keys are listed in the " | ||
| - | ==== Create REST API-Key ==== | + | ==== Create REST API key ==== | 
| It is recommended to create a separate key for each application that uses REST. | It is recommended to create a separate key for each application that uses REST. | ||
| Line 14: | Line 14: | ||
| To do so, follow the steps here: | To do so, follow the steps here: | ||
|   - Click on the " |   - Click on the " | ||
| - |   - Choose action " | + |   - Choose  | 
| * Step 1: Assign a name for the application that will use the new key. | * Step 1: Assign a name for the application that will use the new key. | ||
|     * Step 2: Specify which IP addresses are allowed to use the new key. To do this, enter one or more IP addresses and click " |     * Step 2: Specify which IP addresses are allowed to use the new key. To do this, enter one or more IP addresses and click " | ||
| - |     * Finalize action by clicking the " | + |     * Finalize  | 
| - | - The created key is now listed with assigned name. | + | - The created key is now listed with the assigned name. | 
| ===== SOAP ===== | ===== SOAP ===== | ||