Platform API
You run a platform where members publish listings.
Your users prove they have a Qevik account, and you show the Qevik Member badge next to their listings.
Platform docsQevik offers two separate APIs. Each has its own declaration, identifiers and terms: access to one does not open the other.
You run a platform where members publish listings.
Your users prove they have a Qevik account, and you show the Qevik Member badge next to their listings.
Platform docsYou sell items online that can carry a Qevik identifier.
At checkout, your customer confirms their account and you receive, item by item, a QR code, their System ID as text, or both. You print, engrave or embroider them yourself.
Merchant docs| Topic | Platform API | Merchant API |
|---|---|---|
| What you receive | A signed attestation, verified on your server | A QR code, a System ID or both, per item |
| What to prepare | A domain and a verification file | A domain, a return address, public ES256 keys and a verification file |
| Client identifier | plt_… | mrc_… in production, mrc_test_… in test |
| Authentication | OAuth with PKCE, no secret and no key | private_key_jwt (ES256) server to server, no secret |
| Declaration | Declare a platform | Declare a merchant domain |
| Terms | Platform API terms(new tab) | Merchant API terms(new tab) |