Authentication

Public endpoints (no auth)

Anything under a /public/ path is open and unauthenticated — built for storefronts, catalogs, and AI agents that read a merchant’s published inventory.

curl https://apiv3.droplinked.com/shops/v2/public/name/{shopName}
curl "https://apiv3.droplinked.com/product-v2/public/shop/{shopName}?page=1&limit=24"

Use these to discover shops and products without any credentials.

Merchant / customer JWT (Bearer)

Authenticated actions (managing a shop, products, carts, orders) use a Bearer JWT.

# 1. Obtain a token
curl -X POST https://apiv3.droplinked.com/merchant/login \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com","password":"••••••"}'
# → { "data": { "accessToken": "<JWT>" } }

# 2. Call an authenticated endpoint
curl https://apiv3.droplinked.com/shops/v2 \
  -H "Authorization: Bearer <JWT>"

Send the token as Authorization: Bearer <JWT>. The scheme in the OpenAPI spec is bearer (HTTP, JWT).

Integration key (server-to-server)

Partner/integration services authenticate to the Integration Services layer with an integration-api-key header (a 3RPD_… key issued to your integration). This is for backend-to-backend calls, not browser or agent clients.

curl https://service.droplinked.com/locations/countries \
  -H "integration-api-key: 3RPD_…"

Next: environments

Base URLs for production and development.

Get Started

Core Concepts

Deploy & Operate

Trust Fabric Guides

Order Lifecycle

Payment Integrations

Fulfillment Integrations

Library

Platform & Architecture

Public endpoints (no auth)

Merchant / customer JWT (Bearer)

Integration key (server-to-server)

Next: environments

​Public endpoints (no auth)

​Merchant / customer JWT (Bearer)

​Integration key (server-to-server)

Next: environments

Public endpoints (no auth)

Merchant / customer JWT (Bearer)

Integration key (server-to-server)