Developer Documentation

Build with theShipToVerified REST API

Create verification sessions, embed our widget on your checkout, and listen for signed webhooks. Everything you need to ship a verified order.

Get API KeysOpen OpenAPI Reference

Base URL https://api.shiptoverified.com

Developer-First Design

Everything you need to integrate identity verification in hours, not weeks.

RESTful Design

Clean, predictable URLs and standard HTTP methods. JSON in, JSON out.

Signed Webhooks

Real-time notifications with HMAC-SHA256 signatures and automatic retries with exponential backoff.

Embedded Widget

Ship a single JavaScript snippet and let your customers complete ID capture without leaving checkout.

Sandbox-Ready

Test integrations end-to-end before going live. Reach out for sandbox credentials.

Authentication

Every request to the public API requires two headers issued from your dashboard.

Required headers

  • X-API-Key — your merchant API key (e.g. vfy_live_xxxxx).
  • X-API-Secret — the paired secret. Treat like a password; never expose it client-side.
curl https://api.shiptoverified.com/api/v1/merchants/me \
  -H "X-API-Key: vfy_live_xxxxxxxxxxxxx" \
  -H "X-API-Secret: sk_xxxxxxxxxxxxxxxxxxxx"

Rotate compromised credentials with POST /api/v1/merchants/me/rotate-keys. The previous pair is invalidated immediately.

Verification Endpoints

The core of the integration: create a verification, then drive it to completion.

POST/api/v1/verifications

Create a verification session for a customer order. The response includes a short-lived widget_token you can hand to the embedded widget on your storefront.

// Request body
{
  "transaction_id": "ORD-12345",
  "customer_email": "customer@example.com",
  "target_name": "Jane Q. Buyer",
  "target_address": {
    "line1": "123 Main St",
    "city": "Los Angeles",
    "state": "CA",
    "postal_code": "90001",
    "country": "US"
  }
}

// 201 Created
{
  "id": "ver_abc123",
  "transaction_id": "ORD-12345",
  "status": "pending",
  "widget_token": "eyJhbGci...",
  "created_at": "2025-01-15T18:04:11Z"
}
GET/api/v1/verifications/{id}

Retrieve the current state of a verification. Prefer webhooks over polling for completion notifications.

// 200 OK
{
  "id": "ver_abc123",
  "status": "verified",
  "name_match":    { "is_match": true,  "score": 0.95, "method": "llm" },
  "address_match": { "is_match": true,  "score": 0.92, "method": "llm" },
  "verified_name": "Jane Q. Buyer",
  "verified_at": "2025-01-15T18:07:42Z"
}
POST/api/v1/verifications/{id}/process

Submit the front of the customer’s ID document for OCR and matching. Supply either image_base64 or image_url.

// Request body
{
  "image_base64": "data:image/jpeg;base64,/9j/4AAQ..."
}
POST/api/v1/verifications/{id}/secondary-proof

Submit a secondary proof of address (utility bill, lease, bank statement). Only valid when requires_secondary_proof is true.

POST/api/v1/verifications/{id}/use-id-name

Resolve a name mismatch by accepting the name extracted from the ID document.

POST/api/v1/verifications/{id}/use-id-address

Resolve an address mismatch by accepting the address extracted from the ID document.

POST/api/v1/verifications/{id}/acknowledge

Finalize a verification once name and address are resolved. Fires the verification.completed webhook and marks the verification verified.

DELETE/api/v1/verifications/{id}

Cancel a pending verification. Invalidates the widget token and fires the verification.cancelled webhook.

Merchant Endpoints

Manage your account, settings, and API credentials programmatically.

GET/api/v1/merchants/me

Return the merchant account that owns the API credentials in this request.

GET/api/v1/merchants/me/settings

Read non-sensitive merchant settings (branding, verification rules, notifications).

PATCH/api/v1/merchants/me/settings

Update merchant settings. Only fields included in the body are changed.

POST/api/v1/merchants/me/rotate-keys

Rotate API key and secret. The previous credentials are revoked immediately; the new secret is shown only once.

Verification Status Lifecycle

Every verification moves through a deterministic set of states.

pending

Verification created, awaiting an ID submission from the customer.

processing

An ID has been submitted and is being analyzed.

awaiting_action

A name/address mismatch needs to be resolved (use ID data, request secondary proof, etc.).

verified

Verification complete and acknowledged.

failed

Document could not be processed or verification could not be completed.

cancelled

Verification was cancelled by the merchant.

Webhooks

Configure a webhook URL in your dashboard and we'll POST signed events to it as verifications progress.

Events

  • verification.createdEmitted right after a verification is created via POST /verifications.
  • verification.completedEmitted when the verification transitions to verified after acknowledgment.
  • verification.cancelledEmitted when a verification is cancelled via DELETE /verifications/{id}.

Headers we send

  • X-VerifyID-Event — event name (e.g. verification.completed).
  • X-VerifyID-Signature — t=<ts>,v1=<hmac_sha256(ts.payload, secret)>.
  • User-Agent — VerifyID-Webhook/1.0.

Example payload

{
  "event": "verification.completed",
  "timestamp": "2025-01-15T18:07:42Z",
  "verification_id": "ver_abc123",
  "transaction_id": "ORD-12345",
  "customer_id": "cus_4f12",
  "status": "verified",
  "verified_name": "Jane Q. Buyer",
  "verified_at": "2025-01-15T18:07:42Z",
  "method": "primary_id"
}

Delivery & retries

We retry non-2xx responses with backoff at 1 min, 5 min, 15 min, 1 hr, and 2 hr. Respond with any 2xx status within 30 seconds to acknowledge delivery. Always verify the signature before trusting payload contents.

Errors

Errors are returned as JSON with a detail field. Conventional HTTP status codes indicate the error class.

400

Verification is in a state that does not accept the requested action (e.g. processing an already-verified session).

401

Missing or invalid X-API-Key / X-API-Secret headers.

402

Your subscription is inactive. Reactivate billing before creating verifications.

404

Verification not found for this merchant.

422

Request body failed validation. Check detail for field-level errors.

500

Unexpected server error. Safe to retry with exponential backoff.

Quick Start

Create your first verification in three steps.

1. Get your API credentials

Sign up for a free dashboard account; your API key + secret appear under Settings → API.

2. Create a verification

curl -X POST https://api.shiptoverified.com/api/v1/verifications \
  -H "X-API-Key: vfy_live_xxxxxxxxxxxxx" \
  -H "X-API-Secret: sk_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "transaction_id": "ORD-12345",
    "customer_email": "customer@example.com",
    "target_name": "Jane Q. Buyer",
    "target_address": {
      "line1": "123 Main St",
      "city": "Los Angeles",
      "state": "CA",
      "postal_code": "90001",
      "country": "US"
    }
  }'

3. Embed the widget

On your order-confirmation page, expose the widget_token from step 2 via window.stvOrderData, then load the widget script. The widget walks the customer through ID capture, and you receive the final result via the verification.completed webhook.

<!-- On your order-confirmation page -->
<script>
  window.stvOrderData = {
    widgetToken: "WIDGET_TOKEN_FROM_STEP_2",
    orderId: "ORD-12345",
  };
</script>
<script src="https://api.shiptoverified.com/widget.js?api_key=vfy_live_xxxxxxxxxxxxx"></script>

BigCommerce and WooCommerce merchants don't need to embed the script manually — install the ShipToVerified app from the marketplace and the widget is injected for you.

Get Started FreeFull API Reference

Ready to Integrate?

Get your API keys and start verifying customers in minutes. Our team is here to help with integration support.

Get API KeysContact Sales