Send crypto-asset activity

Send the crypto-asset activity CARF and DAC8 reporting draws on, and find what Taxbit produces from it.

Part of CARF & DAC8 Reporting. Once an account owner has a valid self-certification on file, send their crypto-asset activity. Taxbit reports from those transactions.

Before you begin

1. Tag stablecoins when you configure assets

Tag a stablecoin or Specified Electronic Money Product (SEMP) with is_stablecoin_or_semp when you create the asset with POST /v1/assets. The tag can only be set on creation, only on a CRYPTO asset, and a later PATCH can't change it. Configure your assets shows the request and what a tagged asset returns.

2. Send the activity

Send each account owner's activity with POST /v1/transactions/external-id, which creates a transaction or updates one you sent before. Send transactions and read gains shows the shapes for buys, sells, trades, and transfers, and the Transaction Data Model has every field. Transaction data can also arrive as CSV files through the Ingest page in the Taxbit Dashboard, which offers each template; see the transaction CSV template guides.

3. Find what Taxbit produces

When Taxbit generates a CARF or CRS document for an account, it appears in GET /v1/accounts/{id}/tax-documents with that type. Retrieve US tax forms shows how that endpoint works, including its expiring download URLs.

If the request fails

  • 401. The bearer token is missing, invalid, or expired. Request a new one and retry.
  • 429. Too many requests. Slow down and retry.

The Errors and rate limits page has every error shape, the rate limits, and which calls are safe to retry.

Where to go next