What a bridge costs and when

Every bridge is in one of three states, and state comes back on any bridge you fetch or list.

• running - the container is up. This is the only state that sends and receives.
• paused - the container is stopped and the session is kept. Nothing is delivered while paused, and it is not billed.
• suspended - stopped by us, effectively always because payment failed. Settle the bill in the dashboard and it comes back.

A bridge that is provisioned but never paired, and sees no activity for about 6 hours, has its container stopped automatically. It is not deleted and nothing is lost - the record, the customer_ref, the webhook config all stay.

Using it wakes it. The next call touches the bridge, the container is recreated, and it carries on. So a provisioning script that creates bridges ahead of demand costs nothing while they wait, and the first real request pays a short wake-up delay.

A bridge is a $5/month seat, added to the account subscription when you create it. Bridges created during the 7-day trial are free until the trial ends, and the subscription itself only begins when the first number is connected in the dashboard, card on file.

Cancelling a bridge refunds the unused part of the month automatically - no ticket, no waiting period. Unlimited messages either way; there is no per-message fee to model.

Full terms, including what happens to a number that gets banned, are on the pricing page.

Bridges are cancelled in the dashboard, not through the API. Creating is automatable because platforms provision constantly; removing a number is deliberate, rare, and takes money off a subscription, so it stays a decision someone makes on purpose.

If your platform genuinely needs to tear bridges down programmatically, tell us what you are building - it is a reasonable thing to want and we would rather hear the use case than guess at it.