What you can expect
- Bearer API keys with scopes
- Signed outbound webhooks for key events
- Designed to respect the same safety rails as the UI
- Available on every plan (600 requests per hour per key — not scaled by plan)
Integrations
API & webhooks and PayBlah
PayBlah API and signed webhooks for teams that need the chase to talk to the rest of their stack — scoped keys, same safety rails.
API & webhooks
Keep the chase list honest
Some teams need buttons. Others need events. PayBlah exposes a REST API with bearer keys and scopes, plus signed outbound webhooks so your other systems can react when something changes.
The same safety philosophy applies: the API is not a back door to skip stop-on-payment or blast every contact without the controls the product is built around.
Rate limits do not scale by plan. Each API key is limited to 600 requests per hour on every plan. Public docs are still stabilising.
What this is not
- Not an invitation to spam — Acceptable use still applies
- Not a promise of every internal endpoint forever; public surface is documented deliberately
- Not a books connector — Xero, QuickBooks Online and Sage OAuth are not launched
Next steps
Start a trial, then create API keys in Settings (API & webhooks). There is no vendor Connect button. Use first-run review before any reminder sends. Questions: hello@payblah.com (the PayBlah team).
Create API keys on a free trial
Nothing firm sends without you. You stay the creditor.