Marketplace acquisition handoff

Marketplace uses Bazaar acquisition intents only to preserve a visitor’s selected listing, catalog revision, and action while DotID authenticates the person or creates the account and initial account root user.

Bazaar does not accept or persist a password, root-user record, account bootstrap record, account selector, or client-supplied callback URL. The shell starts the DotID OIDC flow and returns to a fixed Marketplace route. On resume, Bazaar obtains sub and account_id exclusively from the validated DotID JWT, binds the intent once, and reruns catalog, policy, and commercial checks before creating an account-scoped effect. Anonymous intent creation never provisions, charges, grants artifact access, or issues a license.

The public contract uses product-neutral capability paths:

  • POST /software-acquisition/v1/intents

  • GET /software-acquisition/v1/intents/{intentId}

  • POST /software-acquisition/v1/intents/{intentId}/resume

The resume mutation requires Idempotency-Key. Reusing a key with the same request replays the stored outcome; changing the accepted catalog revision conflicts without producing another effect.

DotID permission documents use these independent Bazaar actions:

  • bazaar:Listing:Read — discover public catalog facts.

  • bazaar:Application:Acquire — acquire or request an application for the active account.

  • bazaar:Application:Read — read account application inventory.

  • bazaar:ApplicationAssignment:Assign — assign acquired capacity.

  • bazaar:ApplicationAssignment:Reclaim — reclaim an assignment.