---
sourceDocument: Yokohama Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-security

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# API key credentials

# API key credentials {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

An API key is a unique code that is passed in to an API to identify the calling
application or user.

## API key credentials {#API-key-credential-form__section_qjx_dd3_l2b}

{#API-key-credential-form__table_APIKeyCredentialsForm__entry__2}

| Field | Input value |
|-|-|
| Name | Enter a unique and descriptive name for this credential. |
| Active | Enable or disable these credentials for use. |
| API Key | Enter the API key. |
| Credential alias | Allow flow and workflow creators to assign individual credentials to any activity in a flow or workflow or assign different credentials to each occurrence of the same activity type in a flow or workflow. |
| Applies to | Select whether to apply these credentials to All MID servers in your network, or to one or more Specific MID servers. Specify the MID Servers that should use these credentials in the MID servers field. |
| Order | Order (sequence) in which Discovery tries this credential as it attempts to log on to devices. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), the instance tries the credentials in a random order. |
[Table 1. API key credentials form fields]

{#API-key-credential-form__table_APIKeyCredentialsForm}