Routable API
Routable is a financial technology platform that automates mass payouts, vendor onboarding, and accounts payable for scaling businesses. An unofficial API lets you programmatically pull vendors, payables, payment methods, funding accounts, and tax forms—and push updates like new bills, mass payouts, vendor invitations, and reconciliation events back into Routable.
What is Routable?
Routable is a financial technology platform that automates mass payouts, vendor onboarding, and accounts payable processes for scaling businesses. Companies use Routable to send thousands of payments globally to 220+ countries and territories in 140+ currencies, onboard vendors and contractors with collected business, payment, and tax data, code bills with AI-powered OCR, and reconcile payments against accounting systems like NetSuite, Sage Intacct, QuickBooks Online, and Xero.
Core product areas include:
- Mass Payouts (send thousands of payments via ACH, SWIFT, or Check, plus CSV bulk uploads)
- Vendor Onboarding (24/7 collection of business, payment, and tax details via a customizable UI)
- International Payments (220+ countries and territories, 140+ currencies)
- AP Automation (AI-powered OCR and bill coding)
- Tax Management (W-9, W-8, 1099, and 1042 form handling)
- Vendor Compliance Checks and Payment Reconciliation with accounting systems
Common data entities:
- Payables (ACH, Check, External, International, PayPal, Vendor Choice)
- Companies / Vendors and Contacts
- Payment Methods (address, bank, international, paypal) and bank account validation
- Receivables, Funding Accounts, and Routable balance deposits
- Tax Forms, Compliance Reports, Team Members, and Webhook Events
The Routable Integration Challenge
Routable exposes a developer-friendly REST API, but operationalizing it across an organization's payables, vendor, and reconciliation workflows still presents hurdles:
- API token management: Access is gated behind secret API tokens that must be provisioned, rotated, and scoped per environment without leaking into client code
- Rate limits: Routable caps requests at 600 per minute by default, so high-volume mass-payout and sync jobs need careful throttling and backoff
- Payable type sprawl: ACH, Check, External, International, PayPal, and Vendor Choice payables each carry different required fields, fee estimates, and currency-conversion logic
- Vendor onboarding state: Companies move through invite, onboarding, and re-invite flows for payment and tax data, and integrations must track that lifecycle accurately
- Webhook coverage: 14 webhook events signal onboarding, payment movement, and issues, but consuming them reliably with retries and idempotency is non-trivial
- Accounting reconciliation: Keeping payables, payments, and external IDs aligned with NetSuite, Sage Intacct, QuickBooks Online, and Xero requires precise mapping
How Supergood Creates Routable APIs
Supergood reverse-engineers authenticated browser flows and Routable's REST API surface to deliver a resilient, normalized API layer for your Routable workspace—across payables, vendors, payment methods, and funding accounts.
- Handles API token and session authentication securely, with credential rotation and scoped access
- Respects the 600-requests-per-minute limit with adaptive throttling, backoff, and idempotency keys
- Normalizes responses across payable types, companies, payment methods, and tax forms so you integrate once and rely on consistent objects
- Subscribes to webhook events and reconciles external IDs against your accounting system of record
Use Routable with AI agents: Routable MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your payable types, vendor onboarding flows, and accounting integrations.
- Supergood Generates and Validates Your API
We deliver a production-ready Routable adapter tailored to your workspace, payment methods, and webhook events.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Routable evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Routable workspace using your secret API token and obtain a scoped session for downstream calls.
Vendors
/companiesList vendor and customer companies with filters for onboarding status, payment readiness, and tax form completion.
Vendors
/create_companyCreate a vendor company and optionally invite it to the onboarding flow to collect business, payment, and tax details.
Payables
/payablesRetrieve payables across ACH, Check, External, International, PayPal, and Vendor Choice types with status filters.
Payables
/create_payableCreate a payable with amount, currency, and payment method, with fee and currency-conversion estimation.
Payment Methods
/payment_methodsPull payment methods (address, bank, international, paypal) and validate bank accounts for a company.
Use Cases
Automate mass payouts to vendors and contractors
- Create ACH, SWIFT, and Check payables in bulk and dispatch payouts to 220+ countries - Estimate fees and currency conversions before sending - Stream payment movement webhook events into finance and treasury tools
Sync vendor onboarding and tax data
- Invite companies to onboarding and pull business, payment, and tax form status - Validate bank accounts and payment methods before first payout - Push W-9, W-8, 1099, and 1042 tax form data to compliance and reporting systems
Reconcile payments against accounting systems
- Match payables and payments to external IDs in NetSuite, Sage Intacct, QuickBooks Online, and Xero - Pull funding account balances and deposits for cash-position reporting - Surface failed or pending payments to AR/AP reconciliation workflows
Power AP automation and bill ingestion
- Capture bills via OCR and create payables from coded line items - Route payables through approval workflows before disbursement - Notify downstream apps via webhooks when vendors onboard or issues arise
Technical Specifications
Authentication
Secret API token, plus authenticated session handling in a managed credential vault
Connectivity
Routable's REST API surface plus authenticated browser flows where actions aren't exposed via API
Response format
Normalized JSON across Payables, Companies, Payment Methods, Funding Accounts, and Tax Forms
Rate limits
Adaptive throttling tuned to Routable's default 600 requests-per-minute limit to avoid 429s
Session management
Automatic token rotation, session refresh, and re-authentication on expiry
Data freshness
Near real-time pulls for payables, payments, and vendor status with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Consumes Routable's 14 webhook events for vendor onboarding, payment movement, and issue alerts
Latency
Sub-second reads on cached entities; multi-second writes when creating payables and dispatching payouts
Throughput
Horizontally scaled workers sized for mass-payout volume from hundreds to hundreds of thousands of payments
Reliability
Retry, backoff, and idempotency keys for payable creation and payout dispatch
Adaptation
Continuous monitoring of Routable API releases, webhook changes, and workspace configuration drift
Frequently asked questions
Yes. Supergood normalizes payables across ACH, SWIFT, Check, International, PayPal, and Vendor Choice types, so you can send payouts to 220+ countries and territories in 140+ currencies through a single API surface.
Supergood applies adaptive throttling, backoff, and request queuing tuned to Routable's default 600-per-minute limit, so high-volume mass-payout and sync jobs avoid 429 errors without manual tuning.
Yes. Supergood preserves and maps external IDs so payables, payments, and vendor records reconcile cleanly with NetSuite, Sage Intacct, QuickBooks Online, and Xero.
Yes. Company onboarding status, payment method validation, and W-9, W-8, 1099, and 1042 tax form data are all surfaced through the normalized API, alongside payables and funding accounts.
Supergood subscribes to Routable's 14 webhook events for vendor onboarding, payment movement, and issue alerts, delivering them with retries and idempotency so downstream systems stay in sync.