AJO decision items appear in the UI but not the API

Your team can see offers in Journey Optimizer, but its API list is empty. In an Experience League thread, Adobe staff suggested checking sandbox, container, item state and propagation. The discussion does not establish which one caused that account’s result.

Make the request reproducible

Capture the exact endpoint, query parameters, response status, sandbox header, organization and container ID. Compare them with the UI context of one named item. Adobe’s decision-item list API and Experience Platform API guide define the request surface and sandbox scoping. A successful HTTP response can still represent the wrong scope.

Check lifecycle before eligibility

Open the item’s lifecycle state and last change timestamp. Adobe’s item management guide distinguishes draft work from approved items. Record whether you are testing catalog enumeration or whether an item can be selected for a particular decision context; those are separate questions.

Retest one known item

Use a single item whose UI ID, state and container are recorded. Repeat after any expected propagation window, preserving request and response IDs for Support if the mismatch remains. Recreating all offers would destroy useful evidence and may create duplicates.

Adovo’s view

Visibility is not availability. Every decisioning integration needs a traceable path from authored item to API scope to eligible experience. When that path is explicit, an empty response becomes a bounded diagnosis.