// 1. After the OS grants permission and gives you a token, register it.
await client.registerPush({
  token,               // APNs (hex), FCM or HMS token
  platform: 'ios',     // 'ios' | 'android' | 'web'
  provider: 'apns',    // optional: 'apns' | 'fcm' | 'hms' | 'web_push'
  // hmsConfig: { appId } is required for HMS tokens
});

// 2. Separately, when the person agrees to push messages:
await client.setChannelConsent({ push: true });

// 3. Register again whenever the OS refreshes the token.

import { useCF } from '@contentflow/sdk/react';

// Web Push. Your app owns the service worker and the VAPID key pair.
// Web tokens can be registered, but there's no web-push sender yet (see Current limits).
function EnablePush() {
  const cf = useCF();

  // 1. After the browser grants permission and gives you a subscription, register it.
  const enable = async () => {
    if ((await Notification.requestPermission()) !== 'granted') return;
    const registration = await navigator.serviceWorker.ready;
    const subscription = await registration.pushManager.subscribe({
      userVisibleOnly: true,
      applicationServerKey: VAPID_PUBLIC_KEY,
    });
    await cf.registerPush({
      token: JSON.stringify(subscription),
      platform: 'web',             // provider defaults to 'web_push' for 'web'
    });
  };

  // 2. Separately, when the person agrees to push messages:
  const agree = () => cf.setChannelConsent({ push: true });

  // 3. Register again whenever the browser replaces the subscription.
  return <><button onClick={enable}>Turn on notifications</button><button onClick={agree}>Send me offers</button></>;
}

import * as Notifications from 'expo-notifications';
import { registerExpoPush } from '@contentflow/sdk/expo';

// 1. Asks for permission, reads the device token and registers it.
const result = await registerExpoPush(client, Notifications, { requestPermission: true });
if (result.status !== 'registered') {
  // 'permission_denied', 'permission_not_requested' or 'unsupported_token': nothing was registered.
}

// 2. Separately, when the person agrees to push messages:
await client.setChannelConsent({ push: true });

// 3. Call registerExpoPush again whenever the OS refreshes the token.

// 1. In application(_:didRegisterForRemoteNotificationsWithDeviceToken:):
try await client.registerPushToken(deviceToken)   // APNs by default; platform: .fcm for Firebase

// 2. Separately, when the person agrees to push messages:
try await client.setChannelConsent(.granted, for: .push)

// 3. Register again whenever the OS refreshes the token.

// 1. In FirebaseMessagingService.onNewToken(token), from a coroutine:
client.registerPushToken(token, PushPlatform.Fcm)   // (HMS is not usable yet: no app id parameter)

// 2. Separately, when the person agrees to push messages:
client.setChannelConsent(ConsentChannel.Push, ConsentStatus.Granted)

// 3. onNewToken runs again when the token is refreshed: register there.

final cf = ContentFlow.instance;

// 1. After the OS grants permission and gives you a token (e.g. from firebase_messaging):
await cf.registerPush(CFPushConfig(
  token: token,
  platform: CFPushPlatform.android,   // ios | android | web
  provider: CFPushProvider.fcm,       // apns | fcm | hms
));

// 2. Separately, when the person agrees to push messages (after identify):
//    every channel is sent, and a flag you leave out is sent as false.
await cf.setChannelConsent(userId, const CFChannelConsent(push: true));

// 3. Register again whenever the OS refreshes the token.

# 1. Register the token for this device.
curl -X POST https://api.contentflow.click/sdk/v1/register-push \
  -H "X-CF-Key: $CF_SDK_KEY" -H "X-CF-Device: $CF_DEVICE" -H 'Content-Type: application/json' \
  -d '{"token":"'"$DEVICE_TOKEN"'","platform":"ios","provider":"apns"}'

# 2. Separately, when the person agrees to push messages:
curl -X POST https://api.contentflow.click/sdk/v1/consent \
  -H "X-CF-Key: $CF_SDK_KEY" -H "X-CF-Device: $CF_DEVICE" -H 'Content-Type: application/json' \
  -d "{\"deviceId\":\"$CF_DEVICE\",\"channels\":{\"push\":true}}"

# 3. Register again whenever the OS refreshes the token.