Open OAuth tools

Commerce

eBay OAuth

Token verification can fail unless user-related scopes are granted.

Automated OAuth formProvider docs

What this workflow can do

  • Build authorization URL
  • Exchange authorization code
  • Refresh token
  • Verify access token

Before starting

  • Client ID
  • Client secret
  • RuName
  • Scopes
  • PKCE only if your app requires it
  • Callback code and state

Result handling

  • Access token returns from exchange and can be verified in the result panel.
  • Refresh token may return from exchange or refresh.
  • Callback state is only used to validate the current handshake.
  • Anonymous OAuth Hub workflows do not store client secrets, authorization codes, access tokens, or refresh tokens.

Provider warnings

  • eBay uses a RuName from your keyset, not a redirect URL.
  1. 01PrepareEnter provider credentials, scopes, callback details, and PKCE values if required.
  2. 02AuthorizeBuild the authorization URL and open provider consent.
  3. 03ExchangePaste the returned code and state, then exchange them for tokens.
  4. 04VerifyTest the access token against the provider verification endpoint.
  5. 05Next stepsCopy tokens or metadata, then store them safely outside anonymous mode.

Credentials

OAuth handshake

Provider callback returns code and state. Refresh uses refresh_token.

Troubleshooting

  • eBay scope strings are full URI values; include exact scope URIs for target APIs.
  • Sandbox and production credentials are separate; endpoint and keyset must match environment.

Provider checklist

  1. Choose sandbox or production and keep all credentials/endpoints aligned.
  2. Confirm selected eBay API scopes are enabled for your keyset.
  3. Exchange auth code and test token with a minimal identity endpoint.
  4. Persist refresh token and schedule refresh before expiry.