What you build with it.
The endpoints do distinct jobs. Pick yours.
Retrieve finished tax documents for each of your customers by API, and show them in your own product.

For customers running cost basis on Taxbit, the endpoints return live tax lots, inventory, and realized and unrealized gains. Your front end shows the data, and the engine keeps them accurate.
The same endpoints feed your internal tools, so a support agent sees the customer's forms and tax data without leaving your system.

Building on Taxbit, answered.
The Customer Experience APIs are GET endpoints. They return finished tax documents, tax lots, basis, and realized and unrealized gains, so your app shows them with no redirect. Filing with the IRS and other authorities runs through Information Reporting.
By keeping the schema out of your codebase. Taxbit generates the XML for each jurisdiction and handles updates to the schema, the validation rules, and the bilateral agreements on its own side, so a jurisdiction changing its filing format late in the year does not become work for your engineers. You integrate once against the data model rather than once per regime.
Yes. The endpoints are ordinary HTTP APIs that return structured data, so an agent calls the same interfaces a developer builds against, with no dashboard to log into. The tax data returns into your own product rather than redirecting users away.
