Lovisa · Authentication Profile

Lovisa Authentication

Authentication

Lovisa declares 2 security scheme(s) across its OpenAPI definitions.

CompanyRetailJewelryFashionE-CommerceAustraliaASX Listed

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

Web Bot Auth (agent identification) http-message-signatures

UCP identity linking (buyer Shop account) oauth2

Source

Authentication Profile

generated: '2026-10-21'
method: searched
source: https://www.lovisa.com/llms.txt
docs: https://shopify.dev/docs/api/storefront#identifying-bots-with-web-bot-auth
summary: Lovisa publishes no API auth reference of its own. Its llms.txt (Shopify-generated) says agent traffic
  to the UCP MCP service must identify itself, server-to-server requests using Web Bot Auth, and that buyers may
  connect a Shop account. The store's UCP profile advertises the dev.ucp.common.identity_linking capability. The
  anonymous tools/list recorded in json-schema/ on 2026-10-21 answered without credentials.
schemes:
- name: Web Bot Auth (agent identification)
  type: http-message-signatures
  evidence: '"Server-to-server requests and hosted or remote browsers must use [Web Bot Auth](https://shopify.dev/docs/api/storefront#identifying-bots-with-web-bot-auth)
    and follow the service''s authentication requirements."'
  source: https://www.lovisa.com/llms.txt
- name: UCP identity linking (buyer Shop account)
  type: oauth2
  evidence: 'UCP profile capability dev.ucp.common.identity_linking; llms.txt: "Connect their Shop account for
    personalized discovery and accelerated checkout with saved details."'
  source: https://www.lovisa.com/.well-known/ucp
  note: Flow details are defined by the UCP spec and Shopify, not documented by Lovisa; type is the UCP identity-linking
    mechanism as published by ucp.dev, not observed.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/lovisa-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.