Report what a DIRECT_REQUEST POST /registrations for a jurisdiction would do, without creating anything. Send an Organization-Id, Connection-Id or Entity-Id header to say which organization it is for
result is OK when a new registration would be opened, ABSORBED when an existing sales-tax registration would cover the jurisdiction instead (returned as registration), PLAN_UPGRADE_REQUIRED when the organization's plan does not include the registration, or SALES_TAX_REGISTRATION_REQUIRED when a retail delivery fee registration needs an active sales-tax registration in the jurisdiction first
It assumes the jurisdiction has a nexus, like the register dialog, which only previews jurisdictions the organization is exposed in. A jurisdiction with no nexus reports OK
This is read-only: it stores nothing and never creates a registration.
Release date, as YYYY-MM-DD. Defaults to 2026-07-21.
Target organization id (Organization-Id selector).
Target connection id; resolves to its organization.
Platform entity id; resolves to a connection's organization.
Optional source to disambiguate an Entity-Id.
ISO 3166-1 alpha-2 country to check.
State or province code within countryCode. Omit it for a country-level check.
Which taxes the prospective registration would cover.
SALES_TAXUSE_TAXSALES_AND_USE_TAXRETAIL_DELIVERY_FEEOK to open a new registration, ABSORBED when a sales-tax registration would cover it, PLAN_UPGRADE_REQUIRED when the plan does not include it, or SALES_TAX_REGISTRATION_REQUIRED when the retail delivery fee needs an active sales-tax registration first.
OKABSORBEDPLAN_UPGRADE_REQUIREDSALES_TAX_REGISTRATION_REQUIREDThe existing sales-tax registration that would absorb this one. Present only when result is ABSORBED, null otherwise.
Successful Response
The request was invalid.
Authentication failed or was missing.
The credential is not permitted for this request.
The requested resource was not found.
The request conflicts with existing state.
The request failed validation.