API & Integrations
The IVQA Extension API lets your own tools and the IVQA add-ons for Google Workspace and Microsoft Office create verifications, fetch QR codes and read verification status. This section documents authentication, scopes, endpoints and error handling as they exist today.
Overview
API OverviewWhat the IVQA Extension API is, who uses it, the base URL and response format, and what it can and cannot do.Authentication and API TokensCreate API tokens in Settings, send them as a bearer token, understand scopes and rate limits, and learn how the add-ons sign in instead.Verification APICreate a verification for an external editor document, fetch its QR code, read its status and scan counters, and keep editor metadata in sync.Documents and Directory APIRead-only endpoints — identity and settings, dashboard KPIs and statistics, activity, the documents list, the student and employee directories and search.Issuing Documents through the APIIssue student documents and employee documents from IVQA templates through the API — request fields, host targets, the always-new rule and the response contract.API Errors and Rate LimitsThe error envelope of the IVQA Extension API, every error code and its meaning, and the per-token rate limit.Add-ons and IntegrationsThe IVQA add-ons for Google Workspace and Microsoft Office, what the Integrations page offers, how a verification created from an editor is managed afterwards.WebhooksIVQA does not provide webhooks today. Here is how to follow verification events with the existing API instead.