Incarts authenticates API requests with an API key issued for your integration.Documentation Index
Fetch the complete documentation index at: https://incarts.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
API key header
| Header | Required | Description |
|---|---|---|
X-Incarts-API-Key | Yes, except unauthenticated endpoints | Authenticates the caller and limits access to allowed projects. |
Idempotency-Key | Recommended for writes | Lets clients safely retry create requests without creating duplicates. |
X-Correlation-ID | Optional | Client-supplied request ID echoed in responses for tracing. |
Where credentials come from
Incarts issues API keys during onboarding. Each key is tied to a project and a set of scopes:| Value | Purpose |
|---|---|
projectId | Identifies which Incarts project owns created links and QR codes. |
| API key | Authenticates your server and grants access to a specific project. |
X-Incarts-API-Key and the projectId in request bodies that create project-owned resources.
If the key does not have access to that project, the API returns 403.
Get API access
See the current onboarding flow for project IDs, API keys, and scopes.
API scopes
API keys are project-scoped and need operation-specific scopes such aslinks:write, links:read, and qr-codes:write. Retailer-specific writes also need the matching retailer scope.
Request the smallest useful scope set for what you’re building. A Walmart-only link creator usually needs:
retailers:custom for custom URL links, retailers:instacart for Instacart links, and
links:read only when you need to retrieve links after creation.
Idempotent writes
Use a stableIdempotency-Key when creating links or QR codes. If a network retry happens, reuse the same key for the same logical operation.
Correlation IDs
PassX-Correlation-ID when you want to align client logs with API logs.
