Vori · Authentication Profile
Vori Authentication
Authentication
Every Vori REST API request carries a bearer JWT in the Authorization header. There is no Vori-issued API key or OAuth flow: integrations exchange a Vori user's email/password at Google Identity Toolkit (Firebase identitytoolkit/v3/relyingparty/verifyPassword) for an idToken, then refresh hourly by exchanging the returned refreshToken at securetoken.googleapis.com/v1/token (refresh tokens may rotate on each exchange). Vori recommends creating a banner-level Read-only role user for read-only integrations to limit blast radius.
Vori secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.
CompanyApplicationGroceryPoint-of-SaleRetailInventoryPaymentsCommerce
Methods: http
Schemes: 1
OAuth flows:
API key in:
Security Schemes
bearer http
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.