Paypal Catalog Products
Browse all Paypal APIs51
AI ReadinessFoundational (C-)51/100
Official vendor OpenAPI document · agent-readyE CommerceStorefrontoauth24 EndpointsREST
For Agents
Programmatically create product, list products. Covers 4 operations with oauth2 authentication.
Use for: I need to product, I want to products, Search for show product details, Find all product
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Merchants can use the Catalog Products API to create products, which are goods and services. The API exposes 4 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Catalog Products to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Catalog Products, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com%2Fcatalog-products" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaypal.com%2Fcatalog-products" | 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 Catalog Products API.
Create product
List products
Show product details
Update product
Use Cases
Patterns agents use Catalog Products API for, with concrete tasks.
★ E-Commerce Operations
Use the Catalog Products to perform e commerce operations programmatically. The API provides 4 endpoints covering core functionality including create product, list products, show product details.
Call POST /v1/catalogs/products to create product
Automated products Management
Automate products operations by combining multiple Catalog Products endpoints. Agents can list products and then show product details in a single workflow.
Call GET /v1/catalogs/products to list products, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Catalog Products endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'create product', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — merchants can use the catalog products api to create products, which are goods and services.
METHOD
PATH
DESCRIPTION
POST
/v1/catalogs/products
Create product
GET
/v1/catalogs/products
List products
GET
/v1/catalogs/products/{product_id}
Show product details
PATCH
/v1/catalogs/products/{product_id}
Update product
POST
/v1/catalogs/products
Create product
GET
/v1/catalogs/products
List products
GET
/v1/catalogs/products/{product_id}
Show product details
PATCH
/v1/catalogs/products/{product_id}
Update product
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Catalog Products
- Foundational (C-)51/100
66
Foundational Compliance75
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability85
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
66
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
75
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
100%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
85
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
85%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PayPal Catalog Products by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can create or update products. Through Jentic you install once, import Catalog Products from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Catalog Products puts the product id in the URL path (/v1/catalogs/products/{product_id}), so a rule can pin your agent to reading one product. You choose the operations it may call, so creating a product or patching its details is not included unless you add them.
Credential isolation
Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a product' or 'list catalog products', and Jentic returns the matching Catalog Products operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using Catalog Products API through Jentic.
What authentication does the Catalog Products use?
The Catalog Products uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create product with the Catalog Products?
Yes. Use the POST /v1/catalogs/products endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Catalog Products?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create product through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create product'. Jentic returns the matching Catalog Products operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Catalog Products have?
The Catalog Products exposes 4 endpoints covering products operations.
Can I limit what my agent is allowed to do with the PayPal Catalog Products API?
Yes. Because you self-host Jentic One, your own rules decide which of the four Catalog Products operations the agent may call, so you can allow it to list products and show product details while withholding the create (POST /v1/catalogs/products) and update (PATCH /v1/catalogs/products/{product_id}) operations. Since the product id sits in the URL path, you can pin the agent to reading a single product rather than the whole catalog. The stored PayPal OAuth client credentials are injected only for the operations you permit, so the agent never sees the raw secrets or reaches endpoints you have not granted.
GET STARTED