Getting Started
HaceVerify provides a REST API for building verification workflows into your platform. All API requests are authenticated with your organization's API key. Requests and responses use HaceVerify's normalized schema — you never interact directly with underlying provider APIs.
API Operational Status — September 2026
"Live" = provider-backed checks dispatched and results normalized. "Partial" = internal path works, no public gateway yet. "Provider-blocked" = requests accepted, stubs returned. "Not active" = not wired. "Deferred" = documented contract for future gateway deployment.
Current transport (interim): POST https://hace-verify-copy-8145c464.base44.app/functions/apiGateway
The application-layer API is fully functional with Bearer authentication. Because the Base44 function transport does not expose literal /v1/* URL paths, the logical route and HTTP method are conveyed in the request body via _path and _method. A public edge at api.haceverify.com/v1 is the GA target and is not yet available.
curl https://hace-verify-copy-8145c464.base44.app/functions/apiGateway \
-H "Authorization: Bearer hv_test_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"_path":"/v1/verifications","_method":"GET"}'Quick Integration Flow
Create API Key
Generate a scoped API key in your Business Portal → API Keys.
Submit a Verification Request
POST /v1/verifications with subject data and confirmed consent.
Poll Status
GET /v1/verifications/:id to poll request status.
List Requests
GET /v1/verifications lists your organization’s requests with pagination.
Retrieve a Report
GET /v1/reports/:id returns the report artifact when ready.
Webhooks
POST /v1/webhook-endpoints to register a webhook for async event delivery.