POST
/
api
/
underwriting
/
initial-verification
/
{business_uuid}
Trigger Verification
curl --request POST \
  --url https://monitoring.safeturf.ai/api/underwriting/initial-verification/{business_uuid} \
  --header 'Authorization: Bearer <token>'
{
  "flow_run_id": "<string>",
  "status": "<string>",
  "services_included": [
    {}
  ],
  "services_count": 123,
  "business_uuid": "<string>"
}

​
Overview

Triggers the full verification pipeline for a dealer. Safeturf automatically determines which services to run based on the available data, then executes them in parallel. When to use this endpoint:
  • The dealer was imported with ?skip_verification=true and you’re ready to start verification now
  • You’ve updated the dealer’s data and want to re-run verification with the latest information
  • Verification failed or stalled and you need to re-trigger it
If verification runs automatically on import (the default), you typically don’t need to call this endpoint.

​
Authentication

Every request must include a Bearer token in the Authorization header: 
Authorization: Bearer <your_api_token>

​
Path Parameters

​
business_uuid
string
required
The Safeturf UUID for the business. Retrieve this from Look Up Business UUID after import.

​
Verification Services

Safeturf runs up to 8 services depending on what data is available for the dealer:
ServicePurpose
socureIdentity verification (EmailAuthScore)
middeskBusiness entity verification
verdataSeller/merchant search
apivoid_trustcheckDomain trust and reputation
apivoid_domainDomain age and registration check
serpapiLocation and web presence lookup
validifyBank account insights
giactBank account verification
Only services for which the dealer has the required data fields will be included in the run.

​
Example Request

curl -X POST "https://api.safeturf.com/api/underwriting/initial-verification/b3f1c2a4-91de-4e7c-a823-5f6d84c2e001" \
  -H "Authorization: Bearer <your_api_token>"

​
Response

{
  "message": "Initial verification flow triggered",
  "business_uuid": "b3f1c2a4-91de-4e7c-a823-5f6d84c2e001",
  "flow_run_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "status": "QUEUED",
  "services_included": ["socure", "middesk", "verdata", "apivoid_domain"],
  "services_count": 4,
  "note": "Use GET /api/underwriting/case/{business_uuid} to check status"
}
​
flow_run_id
string
UUID of the background flow run processing this verification.
​
status
string
Always "QUEUED" on success — the flow runs asynchronously.
​
services_included
array
List of verification service names that will run for this dealer, based on available data.
​
services_count
integer
Number of services included in this run.
​
business_uuid
string
Echo of the business_uuid path parameter.

​
Error Responses

StatusMeaning
401Missing or invalid Bearer token
400Not enough data to run any verification services
404No business found for this business_uuid
500Internal error — contact Safeturf support

​
Notes

  • The flow runs asynchronously — a 200 response means it was accepted and queued, not that it has completed.
  • Use Check UW Status to monitor progress after triggering.
  • If services_count is lower than expected, the dealer record may be missing fields (e.g. SSN for Socure, bank account for GIACT). Update the dealer data and re-trigger.