Sume SDK 0.2.0 exported constants: webhook headers and wait defaults

@sume-com/sdk 0.2.0 exports the webhook header names, the 300 s tolerance and the wait defaults as constants. List them so your code does not repeat strings.

4 min readSume
All posts

The 0.2.0 build of @sume-com/sdk exports the strings and defaults that webhook and wait code needs, so you can import them instead of typing them. Printing them from the installed package gives the values below.

The constants

I read these by installing the package and printing the exports on 2026-10-07. They match the webhook verification page and the runs page.

Exports in @sume-com/sdk 0.2.0 (read 2026-10-07)
ExportValue
SUME_WEBHOOK_SIGNATURE_HEADERx-sume-webhook-signature
SUME_WEBHOOK_TIMESTAMP_HEADERx-sume-webhook-timestamp
SUME_WEBHOOK_SIGNATURE_VERSIONsume-v1
DEFAULT_SUME_WEBHOOK_TOLERANCE_SECONDS300
DEFAULT_WAIT_FOR_RUN_POLL_INTERVAL_MS2000
DEFAULT_WAIT_FOR_RUN_TIMEOUT_MS600000 (10 minutes)
DEFAULT_SUBSCRIBE_FORMAT_RUN_TIMEOUT_MS1200000 (20 minutes)
SUME_RUN_FAMILIESaction, format, agent

Where to use them

Use the header constants when you read a request in your receiver, so a rename on Sume's side shows up as a type or value change on upgrade and not a silent mismatch. Use the tolerance constant if you write a verifier of your own and want to match the SDK.

What is not there

The package also exports verifyWebhook, waitForRun, subscribeFormatRun and uploadFile. It does not export waitForJob in 0.2.0, although the repository and the docs describe it, so a job poll needs your own loop on top of getApiJobStatus.

Upgrades

Pin the exact version, and recheck the export list after an upgrade. Generated operations do not throw on an API error; they resolve with { data, error, response }, while waitForRun and subscribeFormatRun do throw.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume