Repository navigation
docs(spec): document the account-linking flow agents actually need - #231
Merged
Sebastian Hölscher (HoelShare) merged 1 commit intoOct 5, 2026
Merged
Conversation
The published quote spec told agents to obtain a token through identity linking but never named the entry point that works. The advertised authorization_endpoint only issues a code for a signed-in storefront customer, so an agent calling it gets identity_required. That is the error a partner hit while building a spec-conformant buyer. Document the pushed-request flow (POST /ucp/quote-agent/authorization-requests, consent on authorization_url, code exchange), the scope rule (request only what scopes_supported lists), and the query-sorting rule for signed GETs. Add both failures to the error table. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sebastian Hölscher (HoelShare)
deleted the
claude/avinash-problem-clarify-c70e61
branch
October 5, 2026 08:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A partner building a spec-conformant UCP buyer called the advertised
authorization_endpointand got400 identity_required. That endpoint, from Agentic Commerce, only issues a code when a signed-in storefront customer is attached. An agent-signed call never has one. The flow that works is this plugin'sPOST /ucp/quote-agent/authorization-requests, but the publishedquote.htmlandquote.openapi.jsonnever mentioned it.Reproduced on 2026-10-05 against a strict-signature test shop (AC 1.3.0). The direct authorize call failed with
identity_required. The consent flow returned a token, andGET /ucp/quoteswith that token answered 200.What changes
quote.spec.html, Authorization:redirect_urirules, the TTL, single use,access_deniedand refresh tokensauthorization_endpointdirectly from an agentscopes_supported. The old text said to requestcom.shopware.quote:manage, which AC 1.3.0 refuses at consent.identity_required)quote.openapi.json: thebearerAuthdescription points at the flow and the scope rule.No code changes.
QuoteContractControllerTestpasses.Follow-ups (not in this PR)
authorization_endpointa real browser consent flow, as the UCP spec describes. Once it does, this plugin's route can be deprecated.com.shopware.quote:managethroughAbstractUcpOAuthScopeProviderso the scope appears inscopes_supported.🤖 Generated with Claude Code