Test in your sandbox
What your sandbox organization does differently for your integration, what to test in it, and the test data rules.
Every Taxbit customer gets a sandbox organization alongside their production organization. The sandbox is where you build and test your integration against the real API, without filing anything, before you point the same code at production. Sandbox vs Production Organizations in the Help Center covers the Dashboard side; this page covers what matters to your integration.
What differs for your integration
- Same API, own credentials. The sandbox answers on the same host as production, with the same endpoints and the same validation, but it has its own
client_id,client_secret, and Organization ID on its Developer Settings page, and nothing you send to it reaches production. When one set of credentials covers more than one organization,tenant_idin the token request picks the organization; see Authenticate. - Nothing is filed or mailed. Approving filing in a sandbox organization files nothing, and a mailing request mails nothing. Filings and mailings come from your production organization.
- TIN matching is skipped. Name and TIN combinations in a sandbox organization are never sent to the IRS.
- One environment per organization. A sandbox can't be split into dev and stage. To keep them apart, request a second sandbox organization with the Tenant Creation Request form on Contacting Taxbit Customer Support, or use IDs that never overlap.
- Sample forms on demand. Generate a QA Package from the Eligibility page in the Dashboard: watermarked draft forms, plus the data behind them, so you can check your forms before tax season.
What to test
Run the Go live checklist in your sandbox first, end to end, for each product in your contract: the filer, your assets if you send crypto transactions, account owners and accounts, tax documentation (the React SDK in demo mode first, then real submissions), transactions or form data, inventory and gains if they're in your contract, a QA Package for each form type, and your webhooks against a test subscription (see Webhooks). When the cycle passes, go live.
Test data
Fictional names, addresses, and TINs are fine for integration tests, since nothing is filed or matched from a sandbox. Before your first production load, most customers load a sample of their real historical account data to the sandbox first, then the full set to production; your implementation manager's checklist covers it. To clean up, work with your implementation manager on deleting account data, or request a new sandbox organization with the Tenant Creation Request form.
Where to go next
Go live: the checks before your first production filing.
Updated 15 days ago
