VynnAI

Canadian grocery data in the tools you already use.

The REST API is built for server-side requests. The MCP server connects compatible clients using your private API key.

Start free
REST APIYour server
GET /v1/products/lookup?upc=0060383682057&province=ON
Result fieldExample
canonical_product.display_nameSample 2% Milk 4L
offers[0].provinceON
offers[0].current_price5.79

Field names match the lookup response. Values are illustrative and do not state current product availability.

4 read-only endpoints. Clear request rules.

Start with the question you need to answer. Each endpoint uses server-side bearer authentication and returns structured JSON errors.

Look up a barcode

Resolve a UPC, EAN, or GTIN and return the observed offers available for one Canadian province.

Read the contract

Search by product or brand

Find catalogue entries when you have a name or brand instead of a barcode.

Read the contract

Retrieve price history

Use a retailer-scoped SKU, province, and period to request dated observations.

Read the contract

Check the reference-store panel

Review the store panel behind Vynn observations before making a coverage statement.

Read the contract

The context helps explain the price.

Lookup responses keep product, retailer, store, and province together. Price history returns dated observations.

See the data fields
Product identityProduct name, brand, size, and barcode fields where available.
Retailer identityBanner and retailer-scoped SKU, kept separate from cross-retailer identity.
GeographyCanadian province and reference-store context for the request.
History datePrice history returns dated observations. Lookup freshness appears only when the record provides it.
ProvenanceSource and matching context needed to interpret the record.

API delivery in one workspace.
Connect compatible MCP clients.

Standard self-serve delivery uses the REST API. The workspace contains the API reference and key controls. Use your own server-side key to connect through REST or MCP.

Public docs

REST API

4 documented GET endpoints with server-side bearer authentication and stable JSON errors.

Read API reference
Account setup

Key management

The dashboard includes controls for creating, rotating, and revoking a server-side key when access is enabled.

Open key management
Available

MCP server

Connect a compatible client to the published read-only endpoint.

Open MCP setup
Downloads and exportsREST API responses use JSON. Account-specific CSV exports, sample reports, and generated files appear in Dashboard Downloads when available. Eligible plans may include scheduled bulk-feed delivery.Open downloads

Read the contract first.

Check the request parameters, error codes, and server-side key rules before you integrate.

Read API reference