> ## 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.

# TD SYNNEX StreamOne Stellr

> Connect TD SYNNEX StreamOne Stellr to Triggr with a client ID and secret from the TD SYNNEX Developer Portal.

Triggr works with your Stellr customers, catalogue and pricing, vendor accounts, subscriptions, customers' Microsoft 365 and Google Workspace tenants, and billing. In Triggr it's called TD Synnex Stellr; it works with StreamOne Stellr, not StreamOne Ion.

## Set up TD SYNNEX

You need a PartnerFirst user with the Admin role.

**1. Open the Developer Portal**

Sign in to the [TD SYNNEX Developer Portal](https://developer.tdsynnex.com) with your PartnerFirst credentials and click **Get API Access**.

**2. Check the application**

Under **My Account → Applications**, use your region's Default Application, or a Custom Application with access to the StreamOne Stellr API.

**3. Copy the credentials**

In **My Account → Client Credentials**, copy the Production client ID and client secret. Sandbox credentials don't work against production.

See TD SYNNEX's [Authentication](https://developer.tdsynnex.com/api-center/reseller/getting-started?resourceKey=authentication) and [Applications](https://developer.tdsynnex.com/api-center/reseller/getting-started?resourceKey=application) guides.

## Connect it in Triggr

**1. Open the configuration**

Go to **Integrations > TD Synnex Stellr** 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 credentials and hosts**

Enter the Client ID and Client Secret, your region's [API Hostname](#regional-hosts), and `sso.us.tdsynnex.com` as SSO Hostname unless TD SYNNEX's Authentication guide gives a different token host for your region. Enter both hostnames without `https://`, then click Save Configuration.

![The TD Synnex Stellr configuration window with Client ID, Client Secret, API Hostname and SSO Hostname fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/rFRD51HB_88hTzdJ/images/td-synnex-stellr/configure.png?fit=max\&auto=format\&n=rFRD51HB_88hTzdJ\&q=85\&s=4d9ed04f56ad4c4553e531179d784153)

### Regional hosts

| Region | API Hostname (production) | API Hostname (sandbox) |
| - | - | - |
| United States | `api.us.tdsynnex.com` | `api-uat.us.tdsynnex.com` |
| Canada | `api.ca.tdsynnex.com` | `api-uat.ca.tdsynnex.com` |
| Brazil | `api-br.lac.tdsynnex.com` | `api-br-uat.lac.tdsynnex.com` |
| Mexico | `api-mx.lac.tdsynnex.com` | `api-mx-uat.lac.tdsynnex.com` |

TD SYNNEX lists these on its [Servers](https://developer.tdsynnex.com/api-center/reseller/getting-started?resourceKey=server) page.

## Use it in workflows

There's no per-client setup. Actions for one end customer take its customer number (`customerNo`) from List Customers; list actions number pages from `1`. Subscription changes return an `operationId` to pass to Get Operation Result.

## Use it in Triggr Core

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

## Troubleshooting

> [accordion] Triggr can't get an access token
>
> Check you pasted the full Production client ID and secret with no spaces, and SSO Hostname is the token host only, such as `sso.us.tdsynnex.com`. New credentials can take a few minutes to become active.

> [accordion] Authentication errors (401)
>
> API Hostname must be the host only, for the region and environment your credentials were created for.

> [accordion] TD Synnex configuration is incomplete (need ClientID, ClientSecret, hostname, ssoHostname)
>
> Core found a saved connection with a blank field. Click Edit on the Base Configuration card and fill in all four.

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

> [accordion] Lost the client secret
>
> Create a new secret under My Account → Client Credentials, then click Edit on the Base Configuration card and paste the new Client ID and Client Secret.

> [accordion] Some calls are refused although authentication works
>
> Give your Custom Application access to the StreamOne Stellr API, or use your region's Default Application. Otherwise ask StreamOne support to confirm API access is enabled for your account.

> [accordion] Rate limits (429)
>
> TD SYNNEX allows 50 requests a second per API client and per source IP address, and blocks calls over the limit for at least 60 seconds. Run bulk workflows in smaller batches. See [Rate Limits](https://developer.tdsynnex.com/api-center/reseller/getting-started?resourceKey=ratelimit).


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