BrandKwikID Documentation
API SuiteDocument Processing (ML)

Signature Detection

Detect signature regions in a document image. Server-side multipart POST with Bearer auth.

API reference

Try itLoading playground…
Loading…
AuthorizationBearer <token>

JWT Bearer token authentication. Obtain a token from the KwikID dashboard.

In: header

filestring
unique_id?string

Response Body

curl -X POST "https://__mock__/signature_detection/signature_detection" \  -F file="string"
{
  "confidence": 0,
  "type": "string"
}
{
  "detail": {
    "<location>": {
      "<field_name>": [
        "string"
      ]
    }
  },
  "message": "string"
}
{
  "detail": {},
  "message": "string"
}

Overview

Call POST /signature_detection/signature_detection with Authorization: Bearer <token> and multipart/form-data file. Optional unique_id. Use the response to crop or score signatures before human review or policy checks.

Key features

  • Document workflows: Finds signature blocks on scans and photos.
  • Server-side processing keeps raw documents off untrusted clients where possible.

Implementation

Step 1: Call from your backend

Attach file as document image per OpenAPI.

Error handling

HTTP statusWhen
400Bad image input.
401Invalid token.

Benefits

  • Speeds up loan and agreement checks that need signature presence.

Next steps