Skip to main content

​
API Reference

TexasVerified implements Next.js route handlers under apps/web/src/app/api. Most are same-origin application routes authenticated by the Auth0 session cookie. Authentication for native mobile routes uses Auth0 Bearer tokens. The web Worker verifies the JWT’s RS256 signature, issuer, audience, and lifetime before resolving the database-backed principal. Set APP_ORIGIN to the origin of the deployment you are testing. No production app origin is asserted by this documentation.

​
Selected route surface

​
Public certificate lookup

The public lookup trims the certificate number, rejects empty or over-64-character values, and returns 404 when no public member record exists.

​
Upload a Drive file

The upload handler expects multipart fields named locationId, section, and file. The section must be one of notice, form, coa, invoice, receipt, compliance_image, certificate, permit, agreement, or other. The request requires a valid Auth0 session.
The handler rejects empty files, unsupported MIME types, files above 50 MB, exceeded storage quotas, and locations the caller does not manage. A successful write returns HTTP 201 with the OCR-queued state.

​
Auditor routes

Auditor routes are served from app/(audit) and use Auth0 Bearer token or session authentication:
  • GET /audit/locations — auditor’s requested locations ledger
  • GET /audit/locations/[grantId] — single-location compliance review
  • GET /audit/tasks — auditor task list
  • GET /audit/tasks/[taskId] — auditor single-task detail

​
Worker surface

Supporting workers handle internal processing that is not part of the public integration surface. These include inbound document intake, background OCR and notification processing, scheduled authority-data sync, and realtime change signaling. They are reached through private service-to-service paths. The one exception is inbound intake: external providers deliver to the intake endpoints listed on the Webhooks page, which are public receivers rather than integration APIs. This is deliberately not an exhaustive route catalog. Administrative review, webhook, evidence, and internal reevaluation handlers exist but are not documented here as external integration surfaces.