Glossary
Definitions of key terms and concepts used throughout LoomAPI documentation.
Tenant
A customer account in LoomAPI. Each tenant has their own API key, isolated rate limits, quotas, and billing. Tenants are completely isolated from each other.
API Key
A unique authentication token for a tenant. Included in the x-tenant-api-key header for all tenant API requests. Keep this secure—it authenticates all API calls for your tenant.
Verification
A single age verification session. Starts with /verify/start, completes with /verify/complete, and results in either approval (with a JWT token) or rejection.
Verification ID
A unique identifier returned when starting a verification. Used to complete the verification and track its status throughout the verification lifecycle.
Token
A JWT (JSON Web Token) issued when a verification is approved. Contains verification metadata without PII. Used to validate access on subsequent requests. Default expiration is 24 hours.
JWT
JSON Web Token—a standard format for securely transmitting information. LoomAPI tokens are JWTs signed with HS256 algorithm and contain verification claims.
Evidence
The verification data submitted to complete a verification. In production, this comes from identity providers like Veriff. In test mode, this can be mock data.
Rate Limit
The maximum number of API requests allowed per time window (default: 60 requests per minute per tenant). Exceeding the limit returns a 429 status with retryAfterSeconds.
Quota
The monthly limit on the number of verifications a tenant can perform. Exceeding the quota returns a 429 status. Quotas reset at the start of each billing cycle.
Hard Limit
An absolute maximum limit on verifications, regardless of quota. Used as a safety mechanism. Exceeding the hard limit requires contacting support.
Request ID
A UUID v4 identifier included in all API responses (especially errors). Use this when contacting support for faster issue resolution.
Mock Provider
A built-in test verification provider that simulates the verification flow without real identity checks. Used for development and testing only.
Veriff
A third-party identity verification provider integrated with LoomAPI. Used in production to perform real age and identity verification.
Stripe
The payment processor used for LoomAPI metered billing. Billing is automatically calculated based on verification usage and charged monthly.
Redis
The caching and rate limiting service used by LoomAPI. Stores rate limit counters, token validation cache, and other temporary data.
Need More Help?
If you encounter a term that's not defined here, check the documentation overview or contact support@loomapi.com.