Documentation Index
Fetch the complete documentation index at: https://dev.puppetvendors.com/llms.txt
Use this file to discover all available pages before exploring further.
V2 Preview — This authentication flow is part of the V2 API preview. Breaking changes may occur.
Overview
All V2 Vendor API endpoints require a JWT token passed via thex-access-token header. There are two ways to get a token:
| Method | Best For | Endpoint |
|---|---|---|
| API Key | Integrations, scripts, AI agents | POST /authenticate |
| Portal Login | Custom vendor portals, mobile apps | POST /portal/auth/login |
Method 1: API Key Authentication (Recommended)
Use this for programmatic access. Your vendor API key starts withvk_.
200
scopeis always"vendor"for vendor tokens — it’s the token typepermissionslists the specific scopes granted to your API key (e.g.,orders:read,products:write)
Getting a Vendor API Key
You can create API keys in the vendor portal under Settings > API Keys, or your merchant can provide one. See API Keys & Scopes for details on key permissions.Method 2: Portal Login
Use this if you’re building a custom login experience for vendors.Portal login is rate limited to 5 attempts per 15 minutes per IP address.
Using the Token
Include the token in all subsequent requests via thex-access-token header:
Token Expiry & Refresh
Tokens expire after 24 hours (86400 seconds). UsePOST /refresh-token with a valid (non-expired) token to get a new one without re-authenticating:
Scope Behaviour
Vendor-scoped tokens automatically filter all data to your vendor account. For example, callingGET /orders will only return orders containing your line items. Attempting to access another vendor’s data returns HTTP 403.