{"article":{"id":10575849523735,"url":"https://linksquares.zendesk.com/api/v2/help_center/en-us/articles/10575849523735.json","html_url":"https://help.linksquares.com/hc/en-us/articles/10575849523735-Managing-API-Keys-and-Authenticating-to-the-LinkSquares-APIs","author_id":9550772382103,"comments_disabled":true,"draft":false,"promoted":false,"position":3,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":26436087990551,"created_at":"2022-11-29T19:53:33Z","updated_at":"2026-02-24T17:37:04Z","name":"Managing API Keys and Authenticating to the LinkSquares APIs","title":"Managing API Keys and Authenticating to the LinkSquares APIs","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2025-09-02T17:47:42Z","user_segment_id":null,"permission_group_id":1091514,"content_tag_ids":[],"label_names":["API","API Key Management","API Key","api"],"body":"

Overview 

\n

LinkSquares APIs are secured from unauthorized use by restricting calls to those that provide proper authentication credentials. The credentials are in the form of an API Key, which is a unique alphanumeric string that the system uses to identify your company’s data.

\n

These keys should be stored in a password manager or an alternative safe location since having access to them is the equivalent of access to your agreements.

\n

Note: LinkSquares API Tokens are shared across Analyze and Finalize. The same token can interact with either application. 

\n

Authentication

\n

LinkSquares APIs utilize a common API key-based authentication, which is invoked by embedding the API key in the request header. API endpoints are REST/HTTPS unless otherwise specified, with request and response data in JSON format.

\n\n

Authentication Examples

\n

Adding your API key should be quick and easy. Here is a quick cURL example from which you can build.  Swap out XXXXX for your API key.

\n
curl --location 'https://api.linksquares.com/api/analyze/v1/agreements' \\
--header 'Content-Type: application/json' \\
--header 'x-api-key: XXXXX'
\n

If you're working in Postman, this will often look like the below, again, swap out the XXXXX for your key:

\n

\n

Creating an API Key 

\n

LinkSquares Administrators can create API keys in the LinkSquares web app settings. 

\n

To begin, go to Settings from the app selector.

\n

Select API Keys.

\n

To create an API key, press the GENERATE API KEY button.

\n

\"Generate_API_Key.png\"

\n

Disabling an API Key 

\n

If you ever wish to disable the API key (e.g., it was on a laptop that was lost or stolen), you can log in to LinkSquares and disable the key. 

\n

Once you disable the compromised key, you can create another one. In other cases, your security policy may dictate that API keys are rotated every 90 or 120 days. The process is the same. Once the option to disable a key is selected, please allow up to five minutes for the change to go into effect.

\n

For the relevant API key, click the Enabled toggle. 

\n

\"Enabled_Toggle.png\"

\n

The Disable API Key modal will appear and prompt you to confirm. Click SAVE.

\n

\"Disable_Key_Pop_Up.png\"

\n

The API key is now shown as Disabled. 

\n

\"Disabled_Toggle.png\"

\n

Disabled keys can be re-enabled by clicking the same toggle.

\n

Deleting an API Key 

\n

If you no longer need an API key, it can be deleted by clicking the trash icon. 

\n

\"Delete_Icon.png\"

\n

The Delete API Key modal will appear and prompt you to confirm. Click DELETE.

\n

\"Delete_API_Key_Pop-Up.png\"

\n

There is no way to undo the deletion of a key. Once deleted, please allow up to five minutes for the change to go into effect.

\n

Using HTTPS for the API Gateway \n

\n

The API Gateway requires using HTTPS as a method of ensuring encryption and security of the public API. If HTTP is used then the user will receive a message detailing that a connection was not able to be established.

"}}