Waymark / Routes / photoshelter.com Authenticate a user against the PhotoShelter API using token-based auth for a non-browser app
domain: photoshelter.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Obtain a PhotoShelter API key by registering as a developer POST email, password, and mode=token to /psapi/v3/mem/authenticate over HTTPS with the X-PS-Api-Key header set Store the returned authentication token (not a cookie) since it stays constant for the session Attach the token to subsequent requests via the X-PS-Auth-Token header (preferred) or an auth_token query parameter Call /psapi/v3/mem/authenticate/logout when finished to close the session Known gotchas All authentication calls must be made over HTTPS or they will fail Cookie-based auth returns a new cookie on every response, which is awkward outside a browser — use mode=token for server-to-server apps instead Trial accounts are limited to 14 days and reduced storage, which can mask production issues during development
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