Re-check Resale Certificate
POST/api/admin/portal/applications/:application/verify-resale-certificate
Re-run the automated resale-certificate check: AI read of the uploaded certificate (when an AI provider key is configured), comparison with the application, and the issuing state's registry lookup (Texas via the Comptroller's open dataset; other states get the official manual-lookup URL). The check is queued: the response is 202 with resale_certificate_verification_status set to pending, and the result lands on the application when the job finishes. Never changes tax exemption.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.