> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sherweb

> Connect Sherweb to Triggr with a Sherweb API application (client ID, client secret and subscription key).

Triggr works with your Sherweb customers, catalogue, orders, subscriptions and platforms. One configuration covers all your customers.

## Set up Sherweb

**1. Create an API application**

In the [Sherweb partner portal](https://cumulus.sherweb.com), go to **Security > APIs** and create an application named `Triggr`. The Account Administrator role has access.

**2. Copy the keys**

Copy the Client ID, Client Secret and Subscription Key. Sherweb shows the client secret only in this dialog.

See Sherweb's [API prerequisites](https://github.com/sherweb/Public-Apis#prerequisite-for-using-the-apis) and [Developer Platform](https://developers.sherweb.com/docs/get-started).

## Connect it in Triggr

**1. Open the configuration**

Go to **Integrations > Sherweb** and click **Configure** on the Base Configuration card.

![The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**2. Enter the keys**

Enter the ClientID, ClientSecret and SubscriptionKey (the key from Security > APIs, not a product subscription ID), then click Save Configuration.

![The Sherweb configuration window with ClientID, ClientSecret and SubscriptionKey fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/sherweb/configure.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=3bcf3f02417246ef4127a893b502e8b0)

Actions for one customer take its Sherweb customer ID, which Get Customers returns.

## Use it in Triggr Core

Core can buy a licence seat at Sherweb when a new starter has none free. Set **Default distributor** to Sherweb in Core's Settings > General, then link each client to its Sherweb customer (saved as the client's `sherwebId` variable) and map its licences. See [Licences and distributors](https://kb.mspprocess.com/core/manage/licences-and-distributors.md#buy-seats-automatically).

## Troubleshooting

> [accordion] 401 errors
>
> Check all three values were pasted in full and come from the same application, and that it still exists under Security > APIs.

> [accordion] SubscriptionKey is missing from sherweb configuration
>
> Core found no complete Sherweb connection. Save the Base Configuration with all three fields, then run the onboarding again.

> [accordion] Client not linked to Sherweb — won't auto-buy
>
> In Core, open the client, click Map next to Sherweb under Integrations, pick its Sherweb customer and click Save mapping.

> [accordion] Calls are refused although the keys are correct
>
> Ask Sherweb to confirm Service Provider API access is enabled for your partner account.

> [accordion] Lost the client secret
>
> Create a new API application, then click Edit on the Base Configuration card and enter all three of its values.

> [accordion] Rate limits
>
> Sherweb allows 3 concurrent requests, 100 a minute and 10,000 a day. Run large workflows in smaller batches. See Sherweb's [Limits](https://developers.sherweb.com/docs/limits).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.