# Push Providers & Multi Bundle

## Push Provider

A push provider is a configuration of a push API with one of four different types: APN, Firebase, Huawei and Xiaomi at the moment.

Multiple providers can be added to the same Stream application to support, for example:

- Multi-tenancy: there can be different builds of the same application such as prod vs staging, regular vs admin, etc.

- Multi-platform: there can be specific customizations for different target platforms such as starting React Native and adapting native Android/iOS SDKs along the way.

<admonition type="info">

Following endpoints, management of push providers only works if your app is upgraded to v2 or v3. Otherwise, the update app settings endpoint must be used for a single provider config per type (APN, Firebase, Huawei, Xiaomi).

</admonition>

### Upsert a Push Provider

In the same endpoint, a new config can be created or updated.

<admonition type="warning">

Up to 25 push providers can be added to a single application.

</admonition>

<admonition type="info">

If the authentication information is updated, linked devices might be invalidated in the next push message sent retry.

</admonition>

<codetabs>

<codetabs-item value="javascript" label="JavaScript">

```js
const pushProviderConfig = {
  name: "my-custom-name",
  type: "firebase",
  firebase_credentials: "my-service-account-information",
};

client.upsertPushProvider(pushProviderConfig);
```

</codetabs-item>

<codetabs-item value="ruby" label="Ruby">

```ruby
# require 'stream-chat'

push_provider_config = {
 name: 'my-custom-name',
 type: 'firebase',
 firebase_credentials: 'my-service-account-information',
}

client.upsert_push_provider(push_provider_config);
```

</codetabs-item>

<codetabs-item value="go" label="Go">

```go
pushProviderConfig = &PushProvider{
 Name: "my-custom-name",
 Type: "firebase",
 FirebaseCredentials: "my-service-account-information",
}

client.UpsertPushProvider(ctx, pushProviderConfig)
```

</codetabs-item>

</codetabs>

### List Push Providers

<codetabs>

<codetabs-item value="javascript" label="JavaScript">

```js
client.listPushProviders();
```

</codetabs-item>

<codetabs-item value="ruby" label="Ruby">

```ruby
client.list_push_providers()
```

</codetabs-item>

<codetabs-item value="go" label="Go">

```go
client.ListPushProviders(ctx);
```

</codetabs-item>

</codetabs>

### Delete a Push Provider

<codetabs>

<codetabs-item value="javascript" label="JavaScript">

```js
const pushProviderID = {
  type: "apn or firebase or huawei or xiaomi",
  name: "your given custom name while creating",
};

client.deletePushProvider(pushProviderID);
```

</codetabs-item>

<codetabs-item value="ruby" label="Ruby">

```ruby
provider_type = 'apn or firebase or huawei or xiaomi'
provider_name = 'your given custom name while creating'

client.delete_push_provider(provider_type, provider_name)
```

</codetabs-item>

<codetabs-item value="go" label="Go">

```go
pushProviderType := "apn or firebase or huawei or xiaomi"
pushProviderName := "your given custom name while creating"

client.DeletePushProvider(ctx, pushProviderType, pushProviderName)
```

</codetabs-item>

</codetabs>

### Push Providers & Devices

By default, adding a device doesn't require a push provider linking due to backward compatibility where old configurations don't have a `name` , so their names are empty.

- If the configuration name is not provided when adding a device, devices will be matched with configurations according to only their types.

- If the configuration name is provided, but invalid, the request will fail with a bad request error.

When devices are added, they can be linked to a provider to inherit their configuration.

<codetabs>

<codetabs-item value="javascript" label="JavaScript">

```js
const pushToken = "your client side generated device token to receive pushes";
const pushProviderType = "apn or firebase or huawei or xiaomi";
const userId = "your user id for server side calls";
const pushProviderName =
  "the name of the provider you created while configuring your app";

client.addDevice(pushToken, pushProviderType, userId, pushProviderName);
```

</codetabs-item>

<codetabs-item value="go" label="Go">

```go
device := &Device{
 ID: "your client side generated device token to receive pushes",
 UserID: "your user id for server side calls",
 PushProvider: "apn or firebase or huawei or xiaomi",
 PushProviderName: "the name of the provider you created while configuring your app"
}

client.AddDevice(ctx, device);
```

</codetabs-item>

</codetabs>

## Updating non-multi bundle configs (nameless)

If you're not interested in multi-bundle support, you can leverage `updateAppSettings` endpoint to add push configuration for a single APN, Firebase, Huawei or Xiaomi provider.

<codetabs>

<codetabs-item value="javascript" label="JavaScript">

```js
// this configuration is same with upsert push provider
// except type is inherent and naming is missing so it's set to empty string
const firebase_config = {
  credentials_json: "my-service-account-information"
};

client.updateAppSettings({ firebase_config });
```

</codetabs-item>

<codetabs-item value="go" label="Go">

```go
// this configuration is same with upsert push provider
// except type is inherent and naming is missing so it's set to empty string

settings := &AppSettings{
 FirebaseConfig: &FirebaseConfigRequest{
  CredentialsJSON: "my-service-account-information",
 },
}

client.UpdateAppSettings(ctx, &settings)
```

</codetabs-item>

</codetabs>

---

This page was last updated at 2025-08-15T14:14:33.384Z.

For the most recent version of this documentation, visit [https://getstream.io/chat/docs/go-golang/push_providers_and_multi_bundle/](https://getstream.io/chat/docs/go-golang/push_providers_and_multi_bundle/).