> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/guides-and-best-practices/how-to-securely-share-api-keys-and-credentials-with-claimlane.md).

# How to securely share API keys and credentials with Claimlane

Guide for sharing credentials securely with Claimlane.

When setting up an integration, Claimlane may need **credentials** such as an **API key**, **API secret**, **token**, **client ID**, **password**, or similar. Because these are sensitive, they must be shared using Claimlane’s secure **Share secrets** feature (not email or chat).

#### What to send

Send exactly the credential fields requested in the integration setup guide, for example:

* **API Key** / **API Secret**
* **Access Token** (and any required companion values, like a **token secret**)
* **Client ID** / **Client Secret**
* **Username** / **Password**
* Any required **Base URL** or **Account ID** (these are often *not* secrets, but should still be labeled clearly)

If the guide asks for multiple values, make sure you share **all** of them—partial credentials often won’t work.

#### How to share credentials securely (recommended method)

1. Open **Manage company** in Claimlane.
2. Go to **Company settings**.
3. Select **Share secrets**.
4. Add each credential you were asked to provide.
   * **Label each secret clearly**, e.g. “ShipStation API Key”, “Zendesk token”, “Magento Access Token Secret”, etc.
   * If you have multiple stores/environments (e.g. **Production** vs **Test**, multiple brands, multiple regions), **include which one each secret belongs to**.
5. After submitting, the page may appear **blank**—that’s expected. For security, **only authorized Claimlane admins can reveal submitted secrets**.
6. Let your Claimlane contact person know once you’ve added the secrets (e.g. “Credentials have been submitted via Share secrets”).

#### What not to do

To keep your credentials safe, please **do not** share secrets via:

* Email
* Slack / Teams / chat messages
* Screenshots containing keys
* Documents or tickets where many people may have access

#### Troubleshooting tips

* If the integration still fails after sharing, double-check that:
  * You shared **all required fields** (not just one of them).
  * The credentials match the correct **account/store/environment**.
  * The credentials are still valid (some platforms show secrets only once, or expire keys).