> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/administration/integrations.md).

# Integrations

Integrations in Equipme Pro: API key and tenant ID for interfaces and automation, product import and price updates from distributor catalogs, and passing parcels to a shipping service.

**Path:** "Administration" → "Integrations"

Under **"Integrations"**, you connect Equipme Pro with other systems. Which tabs you see depends on your role:

| Tab                                       | Content                                                         | Visible to                           |
| ----------------------------------------- | --------------------------------------------------------------- | ------------------------------------ |
| **"API key"**                             | API keys and tenant ID for interfaces and the automation module | "Administrator"                      |
| Distributor catalogs (one tab per vendor) | Credentials for product import and price updates                | "Administrator", "Portfolio Manager" |
| Shipping service                          | Credentials for passing parcels from fulfillment                | "Administrator"                      |

The tabs for distributor catalogs and the shipping service carry the name of the respective vendor.

{% hint style="info" %}
You don't set up single sign-on here, but together with equipme (see [Sign-in and registration](/pro/getting-started/sign-in-and-registration.md)).
{% endhint %}

## API key

With an API key, you connect other systems or the [automation module](/pro/automation.md) or the [equipme connector](/pro/automation/connectors/equipme-pro.md) with Equipme Pro. "Please note: The key is only displayed when it is created."

1. Select the **"Expiration date"**: "Unlimited", "1 month", "6 months" or "1 year".
2. Click **"Add"**.
3. **Copy the key immediately** (copy icon) **and store it securely.**

You also find the **"Tenant ID (required for API communication)"** here, with a copy icon.

The list shows "API key" (masked), "Creator" and "Expiration date"; expired keys are marked. **Deleting** invalidates the key immediately: "If you are currently using it in an integration, it will no longer have access to the API."

{% hint style="warning" %}
**An API key from Pro has full administrator rights** for your provider company and thus access to the data of all your customers. Treat it like a password, don't pass it on, and create a separate key with the shortest possible validity for each connection. If a key is lost or compromised, delete it and create a new one.
{% endhint %}

## Distributor catalogs

Use these tabs to store credentials for connected distributor or product data catalogs. This lets you import product master data directly from the catalog (see [Product import](/pro/portfolio/product-import.md)) and keep the prices of imported products up to date automatically.

What you store differs depending on the vendor:

* **Personal credentials:** For catalogs with user licenses, the stored data only applies to your own user. Every employee who wants to import then stores their own credentials. The tab names the prerequisites at the vendor (required licenses).
* **Company access:** In addition, credentials of an administrative user can be stored for automatic price synchronization ("Administrator" only).
* **Login and password:** Other vendors expect a login with password for import and price updates.

Here's how:

1. Open the vendor's tab.
2. **"Add"** or **"Edit"** and enter the credentials.
3. **"Save"**.

Saved passwords and keys are stored securely and not displayed again; you can update them at any time or remove them with **"Delete"**.

## Shipping service

By connecting a shipping service, you transfer parcels that you create in the shipping area of fulfillment directly to the service. There you create shipping documents and labels; status updates of the shipments are transferred back to Pro (see [Picking, production and shipping](/pro/fulfillment/picking-production-shipping.md)).

1. In the shipping service's portal, create an API integration and copy the keys (instructions with a link are in the tab).
2. In Pro, enter **"Public key"** and **"Secret key"** and save.

If you delete the credentials ("Delete access data"), no more parcels are transferred and no more status updates are synchronized.

## Frequently asked questions

**I don't see the "API key" tab.**

Only administrators manage API keys.

**My API key no longer works.**

Check in the list whether it has expired or been deleted. If necessary, generate a new key and enter it in the integration or under "Automation" → "Accounts".

**Can I display the API key again later?**

No. It is only displayed when it is created. If it is lost, create a new key and delete the old one.

**A colleague can't import products from the distributor catalog even though I have stored my credentials.**

For catalogs with a user license, the credentials only apply to the user who stored them. Your colleague must store their own credentials.

**Which distributors and shipping services are supported?**

You see the available vendors as tabs on this page. Further connections are possible via the [automation module](/pro/automation/connectors.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/pro/administration/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.