Allegro Pl Allegro REST API
60
AI ReadinessFoundational (C+)60/100
Official vendor OpenAPI document · agent-readyE CommerceStorefrontoauth2270 EndpointsREST
For Agents
Create and manage Allegro marketplace offers, read and fulfill buyer orders, and handle shipping, ratings, and disputes for a seller account.
Use for: List all of my active Allegro offers, Create a new offer from an Allegro product, Get the details of a specific order, Set the fulfillment status on an order
Not supported: Does not run buyer-side checkout, capture payments directly, or sell on non-Allegro marketplaces. Use for managing a seller's Allegro listings, orders, and after-sales operations only.
The Allegro REST API lets sellers run their presence on Poland's largest online marketplace, creating and editing product offers, publishing them in bulk, and managing prices, stock, and promotions. It exposes buyer orders through checkout forms so sellers can read order details, set fulfillment status, attach shipments, and issue invoices. Supporting operations cover category trees and their required parameters, shipping rates, delivery settings, seller ratings, and post-purchase disputes.
Install Jentic One Beta
Connect the Allegro REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Allegro REST API, 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%2Fallegro.pl%2Fallegro" | 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%2Fallegro.pl%2Fallegro" | 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 Allegro REST API.
List and inspect a seller's Allegro offers and their processing status
Create and edit marketplace offers from Allegro product definitions
Read buyer orders and set the seller fulfillment status on each
Manage shipping rates, delivery settings, and points of service for a seller account
Handle post-purchase disputes and claims, including messages and attachments
Browse Allegro category trees and the parameters each category requires
Use Cases
Patterns agents use Allegro REST API for, with concrete tasks.
★ AI agent managing an Allegro storefront
A seller's agent needs to keep listings and orders current without a human in the console. Through Jentic the agent searches for listing a seller's Allegro offers, the matching operation is loaded with the OAuth token already injected, and it reads offers, edits prices, and publishes new offers using Allegro product definitions. The agent works directly against the live marketplace surface.
Call GET /sale/offers to list active offers, then POST /sale/product-offers to create a new offer from a product
Order fulfillment automation
After a sale, an agent reads new orders, marks them as being processed, and records a tracking number so the buyer is updated. Allegro surfaces orders as checkout forms, lets the seller set a fulfillment status, and accepts parcel tracking numbers against the order. This keeps the order status accurate without manual clicks in the seller panel.
Call GET /order/checkout-forms for new orders, then PUT /order/checkout-forms/{id}/fulfillment to set the status
Bulk price and stock updates
A seller running thousands of listings needs to adjust prices and quantities together and track whether the change applied. Allegro accepts batch modification commands and returns a command summary plus a detailed per-offer report so an agent can confirm the result. This replaces editing offers one by one when repricing against competitors.
Call POST /sale/offer-bulk-modification-commands and poll GET /sale/offer-bulk-modification-commands/{commandId} until the batch completes
Dispute and claim response
When a buyer opens a post-purchase issue, an agent reads the dispute thread, posts a reply, and changes the claim status. Allegro exposes issues with their chat history, message posting, attachments, and status changes so the whole exchange can be handled through the API. This lets a support agent keep response times low across many open disputes.
Call GET /sale/issues to list open disputes, then POST /sale/issues/{issueId}/message to reply to one
Key Endpoints
270 endpoints — the allegro rest api lets sellers run their presence on poland's largest online marketplace, creating and editing product offers, publishing them in bulk, and managing prices, stock, and promotions.
METHOD
PATH
DESCRIPTION
GET
/sale/offers
List a seller's offers
POST
/sale/product-offers
Create an offer based on a product
GET
/order/checkout-forms
List the seller's buyer orders
GET
/order/checkout-forms/{id}
Get a single order's details
PUT
/order/checkout-forms/{id}/fulfillment
Set the seller fulfillment status on an order
GET
/sale/categories
Get the IDs of Allegro categories
GET
/me
Get basic information about the authenticated user
GET
/sale/offers
List a seller's offers
POST
/sale/product-offers
Create an offer based on a product
GET
/order/checkout-forms
List the seller's buyer orders
GET
/order/checkout-forms/{id}
Get a single order's details
PUT
/order/checkout-forms/{id}/fulfillment
Set the seller fulfillment status on an order
GET
/sale/categories
Get the IDs of Allegro categories
GET
/me
Get basic information about the authenticated user
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.
A
Allegro REST API
- Foundational (C+)60/100
73
Foundational Compliance71
Developer Experience & Jentic Compatibility54
AI-Readiness & Agent Experience43
Agent Usability88
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
71
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
35%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
51%
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.
54
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
57%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
94%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
67%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
88
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
88%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
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 the Allegro REST API by hand means registering an application, running its OAuth 2.0 authorization code or device flow, requesting the right scopes, and refreshing tokens before every offer or order call. Through Jentic you install once, import Allegro from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Allegro authorizes calls with OAuth scopes such as reading offers or writing orders. You choose the operations your agent may call through Jentic, so you can allow order reads and offer reads while leaving write operations like deleting an offer out of the allowed set unless you add them.
Credential isolation
Your Allegro client credentials are stored once, encrypted, by your own Jentic One instance, which runs the token exchange at execution time. They never enter the agent's prompt, logs, or context, nor does the resulting access token.
Intent-based discovery
Agents search Jentic by intent such as 'list my Allegro offers' or 'set an order fulfillment status', and Jentic returns the matching Allegro 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.
FAQs
Specific to using Allegro REST API through Jentic.
What authentication does the Allegro REST API use?
The Allegro REST API uses OAuth 2.0, per its OpenAPI spec. Seller operations run under a user access token obtained through the authorization code or device code flow with scopes such as allegro:api:sale:offers:write and allegro:api:orders:read, while some public catalogue reads also accept an application token from the client credentials flow. Through Jentic the client credentials and token refresh are handled for you, so the agent receives only a scoped token.
Can I read and fulfill buyer orders with the Allegro REST API?
Yes. Call GET /order/checkout-forms to list a seller's orders and GET /order/checkout-forms/{id} for one order's details, then PUT /order/checkout-forms/{id}/fulfillment to set its status and POST /order/checkout-forms/{id}/shipments to add a tracking number. Each of these requires the allegro:api:orders scope.
What are the rate limits for the Allegro REST API?
The OpenAPI spec does not state numeric rate limits. Allegro applies per-application throttling that varies by resource, and heavy write operations such as offer modifications are designed to run as batch commands rather than many single calls. Check the Allegro developer documentation for the current limits on your application before scheduling large syncs.
Is there an Allegro API MCP server?
You don't need an MCP server to give your agent the Allegro REST API. Jentic connects it directly from the API Directory: import the API, store your OAuth credentials once, and your agent calls operations such as GET /sale/offers on demand without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Allegro REST API?
Yes. Write a rule that allows only the order read and offer read operations, so the agent can report on sales and listings but cannot edit prices, publish offers, or delete anything, and every call it makes is logged. You add write operations to the allowed set only when you want the agent to make changes.
How do I list my Allegro offers through Jentic?
Search Jentic for 'list my Allegro offers', load the GET /sale/offers operation, and run it after your OAuth credentials are stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED