Connect Seal Subscriptions with an API token so SyncRange can export subscriptions, items, billing attempts, and subscription rules to Google Sheets, BigQuery, or Excel.
Seal Subscriptions authenticates with a Merchant API token (sent as the X-Seal-Token header). SyncRange does not use OAuth for Seal. You copy the token from your Seal app settings, paste it into SyncRange, and we store it encrypted for use when exports run.
Watch how to find your Seal API token and connect Seal Subscriptions in SyncRange.
seal_token_). You do not need the API secret, that is only for webhook HMAC verification, which SyncRange does not use.
Seal Subscriptions → Settings → General Settings → API
Keep the token private. Do not share it in chat, tickets, or screenshots that leave your team. If it is exposed, generate or rotate a new token in Seal and update the connection in SyncRange.
SyncRange stores the shop label you entered and the API token encrypted at rest. The token is used only to call Seal’s Merchant API when an export runs. SyncRange does not store card numbers from Seal, only the limited payment metadata Seal returns (for example card brand and last digits) if you choose those columns in an export.