Application directory

The application directory queries published Applications visible to the current customer organization, allowing you to display them in your own product.

Querying the directory does not purchase products, create subscriptions, or grant access.

1. Prepare the current user identity

Complete user authentication to obtain a user Access Token for the current environment, and select an Organization where the user is a member. This shared endpoint checks the current user and Organization relationship; it does not require a separate commerce API product. A service identity cannot replace the customer user.

curl --request GET \
  --url "${GOODVISION_API_BASE}/open-platform/v1/application-listings" \
  --header "Authorization: Bearer ${GOODVISION_USER_ACCESS_TOKEN}" \
  --header "X-GV-Organization-ID: ${GOODVISION_CUSTOMER_ORGANIZATION_ID}"

2. Read visible applications

GET /open-platform/v1/application-listings returns {"items": [...]}. The array is empty when no applications are visible.

Each item includes current publication data: id, application_id, environment, resource_version and OpenAPI-defined display fields. The platform filters public and organization-specific publications for the current customer.

sales_offer_refs contains available offer references. Query purchase eligibility, amounts and product activation separately.

Display the current response. Clear previous data and read again after an Organization or environment change; do not use a long-lived cache to decide whether access remains valid.

3. Errors and retries

Status	Action
401	Sign in again
403	Check organization membership; do not change the organization header to bypass restrictions
503	Show temporary unavailability with a retry action, without displaying a previous scope's directory

This endpoint is read-only and does not require Idempotency-Key.

Next: Third-party SaaS billing · API products

Directory entry and login configuration

The directory entry opens your product; the login callback receives an authorization code. Configure them separately. One product uses one Application, with distinct user and service identities. Resolve customer scope through Users and customer spaces.

Embed in Console

Applications redirect by default and also support isolated iframe and trusted qiankun mounting. All adaptation lives in your own application repository. Follow PC web applications, then develop and configure, test, and review and publish.