Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.commenda.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Registration Content API provides a data-driven approach to creating tax registrations. Instead of manually specifying jurisdiction details, you use these endpoints to:
  1. Discover jurisdictions where you can register
  2. Get registration options (tax types, frequencies) for each jurisdiction
  3. Get portal requirements (credentials needed for automated filing)
This ensures that registrations are created with valid, up-to-date information that matches each jurisdiction’s actual requirements.
After gathering content information, use the Create Registration endpoint to create your registration.

​
Workflow

1

Search Available Jurisdictions

Use List Available Jurisdictions to find jurisdictions where you can register. Returns jurisdiction_id for each matching jurisdiction.
curl --request POST \
  --url 'https://transaction-tax.api.in.commenda.io/api/v1/registrations/content/available-jurisdictions' \
  --header 'Authorization: Bearer <your_token>' \
  --header 'Content-Type: application/json' \
  --data '{"filters": {"countries": ["US"], "types": ["STATE_OR_PROVINCE"]}}'
2

Get Registration Options

Use Get Registration Options to get the registration_content_id, available tax_types, and frequencies for your selected jurisdictions.
curl --request POST \
  --url 'https://transaction-tax.api.in.commenda.io/api/v1/registrations/content/registration-input-options' \
  --header 'Authorization: Bearer <your_token>' \
  --header 'Content-Type: application/json' \
  --data '{"filters": {"jurisdiction_ids": ["JUR_US_STATE_CA"]}}'
3

Get Portal Requirements

Use Get Portal Fields to get the portal credentials needed for automated filing (username, password, PIN, etc.).
curl --request POST \
  --url 'https://transaction-tax.api.in.commenda.io/api/v1/registrations/content/portal-fields' \
  --header 'Authorization: Bearer <your_token>' \
  --header 'Content-Type: application/json' \
  --data '{"filters": {"registration_content_ids": ["CCT_US_STATE_CEN_06_RST"]}}'
4

Create Registration

Use Create Registration with the registration_content_id from step 2.
curl --request POST \
  --url 'https://transaction-tax.api.in.commenda.io/api/v1/registrations' \
  --header 'Authorization: Bearer <your_token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "corporation_id": "your-corporation-id",
    "registration_content_id": "CCT_US_STATE_CEN_06_RST",
    "tax_types": ["RST", "DTT"],
    "frequency": "QUARTERLY"
  }'

​
Key Concepts

​
Jurisdiction IDs

Each tax jurisdiction has a unique jurisdiction_id like:
  • JUR_US_STATE_CA — California (state)
  • JUR_US_COUNTY_CA_LOS_ANGELES — Los Angeles County
  • JUR_US_CITY_CO_DENVER — Denver (city)

​
Registration Content IDs

Each registration type has a registration_content_id that encodes the jurisdiction and tax type:
  • CCT_US_STATE_CEN_06_RST — California Retail Sales Tax
  • CCT_US_STATE_CEN_48_RST — Texas Retail Sales Tax
  • CCT_US_STATE_CEN_36_RST — New York Retail Sales Tax

​
Jurisdiction Types

TypeDescription
TRADEBLOCTrade bloc level (e.g., European Union). Covers multiple member countries under a single registration.
COUNTRYCountry level (for non-US jurisdictions or EU member states)
STATE_OR_PROVINCEState or province level (most common for US)
CITYCity with separate filing requirements (home-rule)
COUNTYCounty with separate filing requirements
DISTRICTSpecial taxing district
LOCALOther local jurisdiction
TERRITORYUS territory

​
Tax Types

CodeName
RSTRetail Sales Tax
RUTRetailer’s Use Tax
DTTDistrict Transaction Tax
SSTSimplified Sellers Use Tax
VATValue Added Tax

​
API Endpoints

EndpointDescription
POST /registrations/content/available-jurisdictionsSearch for jurisdictions where you can register
POST /registrations/content/registration-input-optionsGet tax types and frequencies for jurisdictions
POST /registrations/content/portal-fieldsGet portal credential requirements