We’re RateRunners, a shipping-cost reconciliation platform with multiple mutual customers on ShipHero. We currently onboard customers using the Third-Party Developer token flow, which requires the customer to create a dev user, then copy/paste the bearer and refresh tokens into our app. It works, but it’s error-prone and intimidating for non-technical users.
The new OAuth 2.0 + PKCE flow on the Scopes page is exactly the model we want — a customer clicks “Connect ShipHero,” signs in, approves scopes (view:billing, view:shipments, no PII), and we hold the tokens. The blocker is that the published client is restricted to http://localhost:3000/callback, which a hosted web app can’t use.
Request: a way for integration partners to register their own OAuth client (own client_id, allowlisted https:// redirect URI), similar to how MCP agents can be registered via CIMD. A confidential client with a secret would be ideal, but PKCE with a custom redirect would also work.
Two questions if this is possible: (1) are OAuth tokens scoped to the authorizing user’s account only, or can a 3PL user authorize across customer accounts? (2) Is there a recommended way to handle the case where the authorizing user is later deactivated?
Happy to pilot this with our existing ShipHero customers.
Thanks, and appreciate it getting to the dev team.
On the mix: our ShipHero connections span both brands on the WMS and 3PLs on the 3PL platform, and the 3PL side is a fast-growing piece for us since we reconcile fulfillment invoices against carrier bills. I’d rather not post counts publicly, but happy to share specifics with your partner or dev team directly — Rick S. has our thread.
Two things that might help the dev team’s review:
The MCP server already supports registered third-party OAuth clients via CIMD, so this is the same mechanism pointed at a hosted web app — a registered client ID with an allowlisted https redirect — rather than a new auth system.
Password-based “connect” flows break the moment a customer turns on SSO or MFA. The PKCE flow on the Scopes page is the only path that survives that, which is why we want to build on it rather than on /auth/token.
We’re ready to pilot on a staging redirect URI whenever they are.