Environments

Droplinked runs two planes: production and development. Data is isolated per plane — the same shop slug is different data in each.

The development API plane is not currently serving. apiv3dev, servicedev, authdev and web3dev return 503 from the load balancer, as does the production web3 host. Build and test against production with a test shop until the development plane is restored — and see Sandbox access below before you plan a certification run.

API & service base URLs

Service	Production	Development	State
Core API (backend)	`https://apiv3.droplinked.com`	`https://apiv3dev.droplinked.com`	prod serving · dev `503`
Integration Services (3rdp)	`https://service.droplinked.com`	`https://servicedev.droplinked.com`	prod serving · dev `503`
Auth / OAuth	`https://auth.droplinked.com`	`https://authdev.droplinked.com`	prod serving · dev `503`
Web3 Integration	`https://web3.droplinked.com`	`https://web3dev.droplinked.com`	both `503`
Public MCP server	`https://mcp.droplinked.com`	—	serving

Everything a partner integration needs today is on apiv3.droplinked.com. The Web3 Integration host is not reachable on either plane — do not build against it.

Front-end surfaces

Surface	Production	Development
Storefront	`https://droplinked.io` (+ custom domains)	`https://dev.droplinked.io`
Shop Builder (designer)	`https://droplinked.com`	`https://dev.droplinked.com`
Checkout	`https://checkout.droplinked.io`	`https://devcheckout.droplinked.io`

API specification & Swagger UI

Both are served from production:

What	URL
Raw OpenAPI 3.0 JSON	`https://apiv3.droplinked.com/swagger/json`
Interactive Swagger UI	`https://apiv3.droplinked.com/swagger/dev-docs`

/api-doc and /api-doc-json are not valid paths on any plane — both return 404. Earlier revisions of these docs pointed at them; use the two URLs above.

Health

curl https://apiv3.droplinked.com/health

{
  "status": "ok",
  "timestamp": "2026-09-20T23:26:37.274Z",
  "commit": "01647d491",
  "builtAt": "2026-09-20T21:37:59.000Z"
}

commit and builtAt identify the exact running build — useful when you need to confirm a fix has actually shipped before re-testing. Per-integration health lives on the Integration Services host:

curl https://service.droplinked.com/health/stripe

{ "statusCode": 200, "status": "success", "data": { "provider": "STRIPE", "status": "healthy", "latencyMs": 150 } }

Sandbox access

There is no self-serve sandbox today: no public test credentials, no seeded test merchant, and no test-card matrix published here. If you are a payment or technology partner who needs to run an end-to-end transaction for certification, contact your Droplinked counterpart to have a test shop provisioned — that is currently a human-in-the-loop step, and we would rather tell you that up front than have you discover it mid-integration.

Next: authentication

Public endpoints, merchant JWTs, shop API keys, and integration keys.

Get Started

Core Concepts

Deploy & Operate

Trust Fabric Guides

Order Lifecycle

Payments

Payment Integrations

Fulfillment Integrations

Library

Platform & Architecture

API & service base URLs

Front-end surfaces

API specification & Swagger UI

Health

Sandbox access

Next: authentication

​API & service base URLs

​Front-end surfaces

​API specification & Swagger UI

​Health

​Sandbox access

Next: authentication

API & service base URLs

Front-end surfaces

API specification & Swagger UI

Health

Sandbox access