AWS Marketplace Catalog Service
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentE CommerceStorefronthmac12 EndpointsREST
For Agents
List, describe, and update AWS Marketplace product entities and offers programmatically through change sets and resource policies.
Use for: I need to update the price of a SaaS product offer in Marketplace, List all my SaaS offerings in the AWS Marketplace catalog, Submit a change set that adds a new dimension to a metering plan, Get the status of an in-progress change set
Not supported: Does not handle metering, billing, customer subscriptions, or buyer-side actions — use for AWS Marketplace seller-side product and offer catalog management only.
Jentic publishes the only available OpenAPI specification for AWS Marketplace Catalog Service, keeping it validated and agent-ready. The Catalog API lets AWS Marketplace sellers automate product and offer management — listing entities, describing change sets, submitting changes, and applying resource policies for shared editing. It is the programmatic counterpart to the Marketplace Management Portal and supports product types such as SaaS, AMI, container, and AI/ML offerings. Change sets are the unit of edit, asynchronously applied with describe and cancel operations for status tracking.
Install Jentic One Beta
Connect the AWS Marketplace Catalog Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Marketplace Catalog Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS Marketplace Catalog Service API.
List Marketplace entities such as products, offers, and resale authorizations by type
Describe a single entity to retrieve its current detail document
Submit a change set with one or more change types to create or update entities
Cancel a pending change set before AWS applies the requested changes
Track change set status, applied changes, and per-change error details
Attach or remove IAM resource policies that control who can edit a Marketplace entity
Tag Marketplace entities and change sets for cost allocation and access control
Use Cases
Patterns agents use AWS Marketplace Catalog Service API for, with concrete tasks.
★ Programmatic Product Catalog Management
Independent software vendors automate Marketplace listings instead of using the Management Portal — pushing pricing updates, version changes, and metering dimensions through StartChangeSet. Each change is tracked as a change set with describe and cancel operations, giving the seller a full audit log of catalog edits and the ability to roll back unapplied changes.
Submit a StartChangeSet for the SaaSProduct catalog with a single change of ChangeType=UpdatePricingTerms and the new dimension price, then poll DescribeChangeSet until Status is SUCCEEDED
Multi-Account Catalog Editing
Sellers operating across linked AWS accounts use PutResourcePolicy to grant edit rights on a Marketplace entity to teammates without sharing root credentials. The IAM policy is attached directly to the entity, and DeleteResourcePolicy revokes access. This pattern supports separation of duties between product, finance, and partnerships teams within one ISV.
Call PutResourcePolicy on EntityArn arn:aws:aws-marketplace:::Product/abc123 with a policy granting marketplace-catalog:StartChangeSet to a partner account principal
Continuous Listing Validation
Operations teams run scheduled jobs that ListEntities for each product type and DescribeEntity for any entry in CHANGES_PENDING — surfacing pricing or visibility issues before customers see them. This monitoring pattern catches stuck change sets, flagged entities, and unintended visibility changes early, before they affect Marketplace transactions.
Call ListEntities with EntityType=SaaSProduct, then DescribeEntity for each result with EntityIdFilter to find any whose Visibility is Restricted
AI Agent Marketplace Automation
ISVs run AI agents through Jentic to automate routine Marketplace tasks: pushing release notes via change sets, rolling pricing updates across regions, and reporting on catalog health. Jentic isolates the AWS access keys in the vault and surfaces the catalog operations as discoverable tools so the agent can answer 'update pricing for product X' without seeing raw long-lived keys.
Search Jentic for 'submit a marketplace change set', load the StartChangeSet operation, and execute it with Catalog=AWSMarketplace and a single UpdateInformation change for the target SaaS product
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for aws marketplace catalog service, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/ListEntities
List Marketplace entities by type
GET
/DescribeEntity#catalog&entityId
Describe a single entity in detail
POST
/StartChangeSet
Submit a new change set
GET
/DescribeChangeSet#catalog&changeSetId
Describe an existing change set
POST
/CancelChangeSet#catalog&changeSetId
Cancel an in-progress change set
POST
/PutResourcePolicy
Attach a resource policy to an entity
POST
/ListChangeSets
List recent change sets in the catalog
POST
/ListEntities
List Marketplace entities by type
GET
/DescribeEntity#catalog&entityId
Describe a single entity in detail
POST
/StartChangeSet
Submit a new change set
GET
/DescribeChangeSet#catalog&changeSetId
Describe an existing change set
POST
/CancelChangeSet#catalog&changeSetId
Cancel an in-progress change set
POST
/PutResourcePolicy
Attach a resource policy to an entity
POST
/ListChangeSets
List recent change sets in the catalog
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS keys are stored encrypted in the Jentic vault. Catalog calls are signed with Signature Version 4 server-side, so the agent never sees raw keys and IAM scoping limits which entities and change types it can touch.
Intent-based discovery
Agents search by intent (e.g. 'submit a marketplace change set') and Jentic returns matching Marketplace Catalog operations such as StartChangeSet and ListEntities with their input schemas, including the asynchronous ChangeSetId polling pattern.
Time to first call
Direct integration: 1-2 days for IAM, async change-set polling, and SDK error handling. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Marketplace Catalog Service API through Jentic.
Why is there no official OpenAPI spec for AWS Marketplace Catalog Service?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Marketplace Catalog Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AWS Marketplace Catalog API use?
The API uses AWS Signature Version 4 (HMAC) with an access key ID and secret access key scoped via IAM policies under the aws-marketplace and marketplace-catalog action namespaces. Through Jentic, those keys live in the encrypted vault and Jentic signs each request server-side.
Can I update product pricing with the AWS Marketplace Catalog API?
Yes. Submit a change set via POST /StartChangeSet with ChangeType=UpdatePricingTerms or UpdateOfferTerms, providing the EntityIdentifier and the new pricing details. The change set runs asynchronously — poll DescribeChangeSet with the returned ChangeSetId until Status is SUCCEEDED.
What are the rate limits for the AWS Marketplace Catalog API?
AWS does not publish hard request-per-second limits for Marketplace Catalog operations in this spec. Concurrent change sets per entity are restricted — only one open change set can target a given entity at a time, and StartChangeSet returns ResourceInUseException if you violate that constraint.
How do I list my Marketplace entities through Jentic?
Search Jentic for 'list marketplace products' to find POST /ListEntities. Load its schema with the Jentic SDK (pip install jentic), then execute it with Catalog=AWSMarketplace and EntityType set to SaaSProduct, AmiProduct, or ContainerProduct as needed. Pagination is via the NextToken field in responses.
Is the AWS Marketplace Catalog Service free?
Yes — the Catalog API itself has no usage charge. Sellers pay AWS Marketplace listing and transaction fees on the underlying products and offers. Standard data transfer charges may apply for very high-volume API use, but typical seller workflows incur no API cost.
GET STARTED