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

# Expo Push Push Integration with WorldVisa

> Connect Expo Push to WorldVisa to send push notifications to Expo-managed iOS and Android apps through workflows using Expo push tokens and access credentials.

This guide explains the process of configuring and using Expo Push with WorldVisa, from getting your credentials to sending your first notification.

## How to configure Expo with WorldVisa

Before you can send notifications, you must connect your Expo project to WorldVisa by generating an access token and adding it to your integration settings.

### Step 1: Generate your access token from Expo Push

Generate an access token from your dashboard. This token authorizes WorldVisa to send notifications on behalf of your project.

**1. Log in to Expo**

Sign in at the [Expo console](https://expo.dev/).

**2. Open Access Token**

Navigate to the **Credentials** section in the project settings sidebar.
Click [**Access Token**](https://expo.dev/settings/access-tokens).

![Create Expo token](https://mintcdn.com/wv-enterprise/l3bkwl1N_3mOn9aW/images/developers/channels-and-providers/push/expo-push/create-token.png?fit=max\&auto=format\&n=l3bkwl1N_3mOn9aW\&q=85\&s=47daf348331051fc5e7dabae03f1351c)

**3. Create a token**

A menu appears.

**4. Generate the token**

Give it a descriptive name, and then click **Generate New Token**.

![Generate Expo token](https://mintcdn.com/wv-enterprise/l3bkwl1N_3mOn9aW/images/developers/channels-and-providers/push/expo-push/generate-token.png?fit=max\&auto=format\&n=l3bkwl1N_3mOn9aW\&q=85\&s=f2e57722ff937d243f5020606a000cbe)

**5. Copy the token**

Copy and save the generated access token. You need it in the next step.

![Copy Expo token](https://mintcdn.com/wv-enterprise/l3bkwl1N_3mOn9aW/images/developers/channels-and-providers/push/expo-push/copy-token.png?fit=max\&auto=format\&n=l3bkwl1N_3mOn9aW\&q=85\&s=bb2665bf6c7569570b4fdbfdc97c9905)

### Step 2: Connect Expo Push to WorldVisa

Next, add the access token to your Expo integration in the WorldVisa dashboard.

**1. Log in to the WorldVisa dashboard**

Open the WorldVisa Dashboard.

**2. Open Integration Store**

On the WorldVisa dashboard, navigate to the **Integration Store**.

**3. Connect a provider**

In the **Integration Store**, click **Connect provider** to begin setup.

**4. Select Expo Push**

In the **Push** tab, choose **Expo Push** from the provider list.

**5. Paste the access token**

In the Expo integration form, paste the access token that you copied from Expo into the **Access Token** field.

![Expo Integration in WorldVisa](https://mintcdn.com/wv-enterprise/l3bkwl1N_3mOn9aW/images/developers/channels-and-providers/push/expo-push/expo-integration.png?fit=max\&auto=format\&n=l3bkwl1N_3mOn9aW\&q=85\&s=9e7d43cb899f786e574149a4786c38d7)

**6. Create the integration**

Review your credentials, then click **Create Integration** to save.

## Using Expo Push with WorldVisa

Once your integration is configured, you can start sending push notifications by registering your subscribers' device tokens and triggering a workflow.

### Step 1: Add subscriber device token

Before WorldVisa can send a push notification to a subscriber (user), you must associate their device's unique push token with their WorldVisa subscriber profile.

You can do this by making an API call to update the subscriber's credentials.

```bash theme={null}
curl -L -X PUT "${WV_API_URL}/v1/subscribers/<SUBSCRIBER_ID>/credentials" \
-H 'Content-Type: application/json' \
-H "Authorization: ApiKey ${WV_API_KEY}" \
-d '{
  "providerId": "expo",
  "credentials": {
    "deviceTokens": [
      "token1",
      "token2"
    ]
  },
  "integrationIdentifier": "string"
}'
```

> [!NOTE]
>
> WorldVisa automatically removes invalid device tokens from a subscribers' profile and then sends the failure details to the `MESSAGE_FAILED` webhook.

### Step 2: Send a notification

Now you're ready to send a push notification.

```bash theme={null}
curl --location "${WV_API_URL}/v1/events/trigger" \
--header 'Content-Type: application/json' \
--header "Authorization: ApiKey ${WV_API_KEY}" \
-d '{
    "name": "workflowId",
    "to": [
        "SUBSCRIBER_ID"
    ],
    "payload": {}
}'
```

## Configure Expo overrides

Save an Expo override on the Push step when you need Expo Push fields beyond the step subject and body — for example `data`, `sound`, `priority`, or `ttl`. The override is stored on the step, so it is versioned and promoted with the workflow, and every trigger sends it without changing your trigger call.

> [!NOTE]
>
> Provider content overrides in the workflow editor are rolling out gradually and may not be available on your Push step yet. Overrides passed at trigger time work regardless. See [provider content overrides](https://docs.worldvisagroup.com/developers/integrations/push#provider-content-overrides).

Expo overrides are validated against the [Expo Push message](https://docs.expo.dev/push-notifications/sending-notifications) request format. The editor autocompletes supported field names, validates the JSON, and flags unsupported fields.

* **`to` is managed by WorldVisa.** WorldVisa fills device tokens from the subscriber's credentials — do not set `to` in the override.
* **`body` falls back from the step.** If your override omits `body`, WorldVisa uses the rendered Push step body.
* **`title` is not seeded.** Set `title` in the override when you want one; WorldVisa does not copy the step subject automatically.

See the [Expo Push message format](https://docs.expo.dev/push-notifications/sending-notifications) for the full field list.

## Using overrides to customize notifications

```bash theme={null}
curl --location "${WV_API_URL}/v1/events/trigger" \
--header 'Content-Type: application/json' \
--header "Authorization: ApiKey ${WV_API_KEY}" \
-d '{
    "name": "workflowId",
    "to": [
        "subscriber-id-123"
    ],
    "payload": {
        "orderId": "12345"
    },
    "overrides": {
        "providers": {
            "expo": {
                "title": "Order Update",
                "body": "Your order #12345 has been shipped!",
                "data": {
                    "deepLink": "myapp://orders/12345",
                    "orderId": "12345"
                },
                "sound": "default",
                "priority": "high",
                "ttl": 3600
            }
        }
    }
}'
```

## Activity tracking

Expo supports [push activity tracking](https://docs.worldvisagroup.com/developers/integrations/push/push-activity-tracking.md). Enable the **Push Activity Tracking** toggle on the Expo integration. Your app reads the WorldVisa message id from the notification and forwards it as `eventId`.

WorldVisa sets Expo `data` to the trigger payload and adds `__nvMessageId`. A `data` override is merged into that object. Leave `__nvMessageId` in place.

```javascript theme={null}
import * as Notifications from "expo-notifications";

Notifications.addNotificationResponseReceivedListener(async (response) => {
  await fetch("https://your-api.com/api/notifications/events", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      eventType: "clicked",
      eventId: response.notification.request.content.data?.__nvMessageId,
    }),
  });
});
```

Forward `delivered`, `opened`, `dismissed`, or `failed` the same way when your app observes those events. Your backend then calls [WorldVisa's activity endpoint](https://docs.worldvisagroup.com/developers/integrations/push/push-activity-tracking.md#step-3-forward-events-to-WorldVisa-from-your-backend).


## Related topics

- [Activity Tracking](https://docs.worldvisagroup.com/developers/integrations/push/push-activity-tracking.md)
- [Push Webhook Push Integration with WorldVisa](https://docs.worldvisagroup.com/developers/integrations/push/push-webhook.md)
- [Pushpad Push Integration with WorldVisa](https://docs.worldvisagroup.com/developers/integrations/push/pushpad.md)
- [APNS Push Integration with WorldVisa](https://docs.worldvisagroup.com/developers/integrations/push/apns.md)


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