Endpoint reference
Every endpoint the API serves to customers, with every parameter, field and problem code, generated from the API's own OpenAPI document each time this site is built.
Shared conventions
The base is https://api.datatactical.group and every path starts /v2. Authenticate with an API key as a bearer token (authentication). Identifiers are strings: FIPS codes zero-padded (00 for the nation, 22 for a state, 22073 for a county), NAICS codes as published with range sectors under their first code, SOC codes with the hyphen, ownership as fed, state, local or private. Periods are 2015 or 2015q1, chosen with granularity (annual or quarterly) and a from and to.
Parameters are strict: an unknown query parameter is a 400 with the code unknown_parameter, a repeated one repeated_parameter, and the parameters that shape a spreadsheet export are refused on a JSON or CSV request with xlsx_only_parameter. The data endpoints and the taxonomies answer an envelope of data and meta; on the data endpoints meta carries the vintage, the provenance_boundaries and the pagination block. The vintage list and the account routes answer the shapes their own pages describe.
Large results are paged with cursor and limit (paging). Every refusal is a problem document with a code (errors), and the request ceilings and the points meter are on rate limits.
The resources
Each page below lists its endpoints with every parameter, request field, response field and the problem codes each can send. The pages are generated from the API’s OpenAPI document, the same document the API serves at /v2/openapi.json, so a change to the API changes this reference on the next build.
Industry data
Industry (QCEW) series, map and location quotient endpoints: every parameter, response field and problem code, generated from the API document.
4 endpoints
Reference →Occupation data
Occupation (OEWS) series, map and location quotient endpoints: every parameter, response field and problem code, generated from the API document.
4 endpoints
Reference →Taxonomies
The codes the data routes take: NAICS, SOC, areas, MSAs, ownership, periods. Not metered; cacheable.
9 endpoints
Reference →Vintages
The data releases this credential can read.
1 endpoint
Reference →Account
The signed-in person, their active organization, the rules the screens state, sessions, closing and reopening.
17 endpoints
Reference →Keys & usage
API keys (live and sandbox) and the month's usage.
4 endpoints
Reference →Notifications & workspace
The in-app notifications and the app's saved workspace.
6 endpoints
Reference →Organization
Organizations a person can find or join, verified domains and join requests.
16 endpoints
Reference →Members & invitations
Members, seats, roles, invitations and ownership.
17 endpoints
Reference →Clusters & counties
The organization's county set and its saved clusters of codes or counties.
17 endpoints
Reference →Billing
The self-serve subscription: plan, interval, seats, county slots, the API add-on, the card, invoices.
16 endpoints
Reference →Support
Support tickets, open to signed-out visitors.
7 endpoints
Reference →Authentication
Sign-up, sign-in, verification, password reset and the second factor (better-auth). These answer `{code, message}` JSON, not problem documents, except where noted.
40 endpoints
Reference →Service
Liveness and this document.
2 endpoints
Reference →160 endpoints, generated from taigan/openapi.yaml at catahoula77925fab712f.