Integrate in under 2 hours.
Verify gig workers in milliseconds.

🚀 Quickstart

You can have a worker verified end-to-end in your sandbox in under 20 minutes. Here's the shortest path.

// 1. Install
// npm install gigverify

const GigVerify = require('gigverify');

const client = new GigVerify({
  apiKey: 'gv_sandbox_YOUR_KEY',  // from /partners
  env:    'sandbox',             // 'production' when live
});

// 2. Verify a worker (requires their consent token)
const result = await client.verify({
  workerId:     'GID-US-288867',   // from consent widget callback
  consentToken: 'ct_abc123...',    // from widget GIGID_CLAIMED event
});

// result:
// {
//   level: 2,
//   income_signal: 'verified',
//   platforms: 3,
//   gig_score: 612,
//   kyc_status: 'pending',
//   worker_type: 'gig',
//   queried_at: '2026-03-30T12:00:00Z'
// }

if (result.level >= 2) {
  // Worker has verified active income — approve loan / policy / tenancy
  approveApplication(result);
}

🔑 Authentication

GigVerify™ uses API keys passed in the Authorization header as a Bearer token. Every request must include your key.

Authorization: Bearer gv_sandbox_YOUR_KEY_HERE
Content-Type: application/json

🧪 Environments

Sandbox returns realistic simulated data. The API contract is identical between environments — flip the key to go live. No code changes required.

Sandbox Test Workers

Use these IDs in sandbox to test different scenarios:

📦 SDKs

Official SDKs wrap the REST API with typed responses, automatic retries, and consent widget helpers.

✅ Consent Model

GigVerify™ is consumer-permissioned — not a Consumer Reporting Agency under FCRA. Every query requires the worker's active, revocable consent. This is the architecture that makes GigVerify™ legally distinct from credit bureaus.

The Consent Flow

🎯 Response Levels

GigVerify™ returns a level field (1–3) indicating how much has been verified. Higher levels = more data + higher confidence.

🔍 POST /verify

The core verification call. Returns the worker's current level, income signal, GigScore, and platform count.

{
  "success":       true,
  "workerId":      "GID-US-288867",
  "level":         2,
  "income_signal": "verified",   // verified | pending | insufficient
  "platforms":     3,
  "gig_score":     612,
  "kyc_status":    "none",        // none | pending | verified
  "worker_type":   "gig",         // gig | indie
  "queried_at":    "2026-03-30T12:00:00Z"
}

📋 GET /consent/status

Check whether a worker's consent is currently active for your integration.

📦 POST /verify/batch

Verify up to 50 workers in a single call. Each item requires its own consent token. Useful for portfolio reviews or bulk underwriting.

{
  "workers": [
    { "workerId": "GID-US-288867", "consentToken": "ct_abc..." },
    { "workerId": "IID-UK-146032", "consentToken": "ct_xyz..." }
  ]
}

🔔 Webhooks

Register an HTTPS endpoint to receive real-time events. Configure in your Verifier Dashboard.

⚠️ Error Codes

💳 Pricing

🛡️ Compliance

FCRA — We Are Not a CRA

GigVerify™ is not a Consumer Reporting Agency under the Fair Credit Reporting Act (15 U.S.C. § 1681 et seq.). Our data is:

• Consumer-initiated: The worker claims their GigID and connects their platforms voluntarily.
• Consumer-permissioned: Every query requires a consent token the worker has actively granted.
• Consumer-revocable: Workers can withdraw consent at any time from their Vault.
• Not assembled for credit purposes: GigVerify™ is income identity verification, not a credit report.

A full attorney-reviewed "Not a CRA" one-pager is available for your legal team. Email partners@gigid.ai.

GDPR

GigVerify™ is GDPR-compliant. A standard Data Processing Agreement (DPA) is available for EU-based verifiers. Workers in the EU have full rights to access, correct, and delete their data from the GigID Vault.