Prerequisites

Three things exist before your first API call: access to the Taxbit Dashboard, API credentials, and a server-side environment to hold them. Most other decisions are settled in the implementation kickoff that your Taxbit implementation manager leads.

Access to the Taxbit Dashboard

Your implementation manager provisions your tenant and your Dashboard users. The Dashboard is where you find your API credentials, set up filers, and upload transaction files in bulk.

Each tenant is its own organization, with its own credentials and data, and a sandbox tenant can't be split by environment. To keep dev and stage apart, ask your implementation manager for a second sandbox tenant, or use IDs that never overlap between them.

API credentials

The Developer Settings page in the Dashboard (Settings > Developer Settings) holds your client_id, client_secret, and tenant_id, which the Dashboard shows as Organization ID. You exchange the first two for a bearer token that lasts 24 hours; Authenticate your tenant shows how. Keep tenant_id at hand as well: the token request needs it when one set of credentials covers more than one tenant, and the account-owner token the React SDK uses always needs it.

Store the secret in your secret manager, never in source control. If it ever reaches client code, rotate it in Developer Settings.

A server-side environment

Tokens are minted and used from your backend. Nothing in these guides runs in a browser. The Tax Documentation React SDK is the one piece that runs in the browser, and it receives a short-lived account-owner token from your backend, never your credentials.

Decisions from your kickoff

The kickoff settles four things that shape your integration. Have answers ready.

• Your data path. Whether you send transactions and let Taxbit compute form amounts, or send form items you compute yourself. Choose your data path explains the trade-off.
• Your transaction types. How the activity on your platform maps onto Taxbit's transaction types, such as trade, deposit, withdraw, and income. The transaction types sheet from your kickoff is the working reference, and the Transactions reference lists every type.
• Your filers. A filer is the legal entity that submits returns: its name, address, EIN or TIN, and a contact person. You need one per filing entity. A tenant can hold several filers, and one is marked as the default. Some parts of the product call a filer a payer. See the Filers reference.
• Your assets. The list of fiat and crypto assets your platform supports, so Taxbit can map them before any data arrives.

Where to go next

Authenticate your tenant turns your credentials into a bearer token, which every later step uses.