Authenticate as a Sharefox shop user vs. an admin user for different API scopes
domain: api.mysharefox.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Sharefox API's auth tag at https://api.mysharefox.com/docs#tag/auth to see the available login flows.
For customer-facing/storefront actions, POST to /login to authenticate as a shop user (a registered customer of the shop); this returns a short-lived JWT bearer token.
For privileged operations spanning all users of a shop, POST to /admin/login instead; this returns a long-lived opaque token, not a JWT.
Send whichever token you obtained as a Bearer token in the Authorization header on subsequent requests — both token types are used the same way despite their different formats.
Contact Sharefox support to confirm your subscription includes API access and is approved for production use before going live.
Known gotchas
The two login endpoints return structurally different tokens (short-lived JWT from /login vs. long-lived opaque token from /admin/login) — don't assume you can decode an admin token as a JWT.
Admin-prefixed endpoints (paths starting with /admin) require the admin token; using a shop-user token against them will fail authorization even though both are sent as 'Bearer' tokens.
The Sharefox API is described by Sharefox as beta, and available only to approved partners/customers — endpoints can change without notice.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?