Getting Started


TaxBit is a leading end-to-end compliance and reporting solution for the Digital Economy. Our platform serves as a unified system of record that supports tax and accounting needs for digital assets and other areas. We provide scalable, API-powered compliance processes that address the diverse needs of various businesses in an ever-changing regulatory environment. Our APIs enable enterprises and their partners to securely share data, documents, forms, and insights.

The TaxBit Enterprise APIs form the foundation of our TaxBit Enterprise Tax Suite, which comprises several products and services, including Information Reporting, Tax Documentation (Digital W9/W8), Cost Basis Interchange, Tax Center, Broker Cost Basis, and TaxBit Dashboard.

To facilitate your development activities using our advanced APIs, we have organized our documentation into the following categories:

  • Guides: This provides comprehensive guidance for specific workflows and solutions.
  • Recipes: This includes workflows for typical use cases such as creating accounts and submitting transactions to TaxBit.
  • API Reference: This contains details, query parameters, and sample responses for each public endpoint.
  • Changelog: This is a continually updated document that provides information on our latest releases.

Getting Access

Our APIs require authentication with an access token. To get the access token, you must access the /oauth/token endpoint with your client_id, client_secret, and grant_type. You can request this information from your TaxBit implementation manager. Please reference our guides for more information on access tokens.

Endpoints Configurations

TaxBit currently offers REST APIs to access our endpoints.

Our REST API Architecture
Representational State Transfer, or REST, is one of the most famous architectural methods for creating web services. TaxBit chose a RESTful method to provide users with a straightforward, standardized, user-friendly, and scalable framework. In addition, REST also offers the following advantages:

  • Under a RESTful framework, each URL represents a type of resource.
  • The representational state of each resource is transferred between the client and server.
  • The client will use four HTTP request methods, or verbs, to make RESTful calls to the server. These verbs are GET, POST, PUT, and DELETE.

Here are some examples of how you should use each verb:

  • GET: Retrieves an existing record or records from the server.
  • POST: Creates a new record or records on the server. (In some cases we allow updates through the post method.)
  • PUT: Updates an existing record or records on the server.
  • DELETE: Deletes an existing record or records on the server.

We strongly recommend using our REST APIs to perform trades; withdrawals; and collect and certify tax documentation.

Contact Us

If you have any questions about our REST APIs, please contact the Implementation Team. You can also contact our Enterprise Support Team at [email protected].

Open API Specification