Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Cloud Services Catalog Terraform Connector API Key Credentials form reference

The Cloud Services Catalog Terraform Connector uses API key credentials to authenticate the requests sent to the Terraform Enterprise and Terraform Cloud and the version control systems provisioned in them.

To learn more about API key permissions and tokens, see https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens.

Parent Topic:Cloud Services Catalog Terraform Connector reference

sndocs is an independent community mirror and is not affiliated with or endorsed by ServiceNow.

ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc., in the United States and/or other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

© 2026 ServiceNow, Inc. All rights reserved.

Documentation content is redistributed under the Apache License 2.0 from the ServiceNowDocs repository.

FieldDescription
NameUnique and descriptive name of the credential.
ActiveOption for enabling this credential for discovery. Select this check box to enable discovery.
API Key

API key that can be used to access the account.- Terraform Enterprise or Terraform Cloud API key: Bearer token for accessing Terraform Enterprise or Terraform Cloud.

Ensure that the API key adheres to the following syntax:



</code></pre>
<p>Bearer <API key>

    ```</p>
<ul>
<li>GitHub API key: API token for accessing the GitHub enterprise or community account.</li>
</ul>
<p>Ensure that the token adheres to the following syntax:</p>
<pre><code>

Token ```

  • GitLab API key: Bearer token for accessing the GitLab enterprise or community account.

Ensure that the token adheres to the following syntax:



</code></pre>
<p>Bearer <API key>

    ```</p>
<ul>
<li>Microsoft Azure DevOps API key: base-64 encoded token for accessing the Azure DevOps enterprise or community account.</li>
</ul>
<p><strong>Important:</strong> Prefix the API token with a colon (:), and then encode the entire string to base-64.</p>
<p>Ensure that the token adheres to the following syntax:</p>
<pre><code>

Basic ```

Applies toMID Server to which you apply the credentials. Select All MID servers
OrderOrder in which the platform runs this credential as it attempts to log in to devices. A smaller number indicates that the credential appears higher in the list. Establish the 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. The default value is 100.
Credential aliasCredential alias that can resolve the credential.