API Reference

Reference map for currently available `v1` endpoints and shared response contracts.

Base URL

https://www.securepointusa.com/api/v1

External API calls use an active `spusa_` API key with the required scope. Browser/admin calls use an authenticated user session with a valid organization scope.

Endpoint Map

Method	Path	Purpose
POST	/api/v1/checkin	Submit a v1 check-in request.
POST	/api/v1/prescreen	Run a prescreen decision workflow.
POST	/api/v1/ownership/check	Run an ownership-aware screening check where enabled.
POST	/api/v1/vendors/screen	Screen vendor entities against sanctions sources.
GET	/api/v1/screenings/{id}	Fetch one screening record by id.
GET	/api/v1/screenings/{id}/evidence	Fetch evidence metadata for a screening record.
GET	/api/v1/adjudication/queue	Fetch adjudication cases available to the caller.
GET	/api/v1/adjudication/{id}	Fetch one adjudication case.
POST	/api/v1/adjudication/{id}/disposition	Record an adjudication disposition.
POST	/api/v1/sessions/{id}/update	Update a session state or metadata.
GET	/api/v1/audit/export	Export audit records for authorized users.
GET	/api/v1/audit/integrity	Check audit-log integrity status for authorized users.
PUT	/api/v1/adjudication/rules	Update adjudication rules configuration.
PUT	/api/v1/workforce/sync	Sync workforce identity records.
GET	/api/v1/compliance/reports	Retrieve compliance report summaries.
GET	/api/v1/compliance/sales-matrix	Retrieve compliance capability matrix data.

Success Response Shape

{
  "success": true,
  "data": {
    "...": "resource payload"
  },
  "meta": {
    "requestId": "uuid",
    "timestamp": "2026-02-24T00:00:00.000Z"
  }
}

Error Response Shape

{
  "success": false,
  "error": {
    "code": "FORBIDDEN",
    "message": "Insufficient permissions",
    "details": {
      "...": "optional diagnostic data"
    }
  },
  "meta": {
    "requestId": "uuid",
    "timestamp": "2026-02-24T00:00:00.000Z"
  }
}

Example Request

curl -X POST "https://www.securepointusa.com/api/v1/checkin" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <spusa_api_key_or_user_session>" \
  -d '{
    "visitor": {
      "first_name": "Alex",
      "last_name": "Morgan"
    }
  }'

How to screen a name with the Screening API

A short walkthrough of /api/v1/prescreen and /api/v1/screenings/{id}, once SecurePoint has turned on the Screening API for your organization and issued your API key.

Handle Errors and Retries Next

Review rate-limit and error-handling guidance before integrating production traffic.

Open Error Handling Guide