Full REST API with OpenAPI documentation, asynchronous batch processing, webhook-driven status updates, and push-based inventory sync. Used in production by some of the world's largest preloved operators to list 1,000+ items per day per user, with sub-5-second cross-channel sync. Available on Scale and Enterprise plans.
Thriftify's API gives you full control to customise your workflow. REST endpoints with OpenAPI documentation, OAuth and API key authentication, asynchronous batch processing for high-throughput ingestion, webhook delivery for sale and inventory events, push-based status updates from authorised partners, and full error handling with retry-able status codes. Ready for integration into existing WMS, ERP, PIM, and BI systems.
The architecture supports significantly higher peak throughput; sustained production is constrained by channel API rate limits downstream, not by Thriftify.
~10,714
Listings per minute (architectural peak)
100,000+
Listings per day in production
Live, sustained operations
<5 sec
Webhook-driven sync latency
Sale event to cross-channel de-list, measured end-to-end
96%
Listings published without manual editing
Enterprise in production, monthly
The API surface is the same one that powers Thriftify's dashboard, which means anything the UI can do is automatable. Four common integration patterns.
Push product data and image URLs from your custom photography suite or solution on intake. Thriftify enriches with AI-generated titles, descriptions, and item specifics, then publishes to your target sales channels. The operator team handles photography and exceptions; the pipeline handles everything else.
Bidirectional sync with your existing PIM. Read product data in, write enriched metadata, listing IDs, and channel status back. SKU-driven inventory truth across systems. Push-based status updates from authorised partner systems eliminate polling.
Export listing performance, sell-through rates, and channel revenue into your existing BI stack. Pull via API, push to your data warehouse, or stream via webhooks. Thriftify doesn't replace your reporting, it feeds it.
Some enterprise customers build their own internal tools on top of Thriftify's API, custom merchandising dashboards, photographer workflow UIs, or cross-channel performance reports, while using Thriftify's API for listing creation, cross-listing, and inventory sync. The API is fully sufficient for headless integration.
Most resale platforms can't tell you their throughput because they haven't measured it. Here are Thriftify's production numbers, verified by live customers in deployment.
| Capability | Limit |
|---|---|
| Listings per minute (architectural peak) | ~10,714 |
| Listings per hour (sustained) | ~642,857 |
| Listings per day (theoretical max) | ~2,100,000 |
| Batch size per API call | Up to 1,000 listings |
| Authentication | OAuth 2.0 and API key |
| Async processing | Yes, job queue with status callbacks |
| Push-based status updates | Yes, authorised partners can update without polling |
| Webhook delivery latency (typical) | 1–2 seconds |
| End-to-end cross-channel sync on sale | <5 seconds in production |
| Bulk operations endpoint | Yes |
| Idempotency keys supported | Yes |
| Error retry policy | Exponential backoff, retryable status codes documented |
Sustained throughput in your deployment may be constrained by downstream marketplace rate limits (eBay's published API limits apply per seller account).
Three things that matter to the developer who has to integrate this.
Full OpenAPI 3.0 spec with interactive Swagger UI. Test endpoints against a sandbox environment from the docs page. Sample requests in cURL, Python, JavaScript, and PHP. Generated client libraries available on request.
Open the API docsEvery error response includes an actionable message, an error code, and a documented remediation step. Retryable errors are clearly distinguished from terminal failures. Idempotency keys on write endpoints mean safe retries on network failures.
Sale events, inventory changes, and listing status updates delivered via webhook. Retry on delivery failure with exponential backoff. Webhook payloads include signed signatures for verification. Dead-letter queue for permanently failed deliveries, visible in the dashboard.
Standard enterprise authentication and security posture. Documentation available during procurement.
OAuth 2.0 for user-context operations. API key authentication for server-to-server integration. Scoped permissions per API key, read-only, write, admin. Token rotation supported.
GDPR-compliant data handling for UK and EU operations. Full Data Processing Agreement available during procurement. Data isolation between tenants. Audit log of every API operation for the duration of the contract.
Security questionnaire, penetration testing reports, business continuity plan, and vendor risk assessment available on request. Standard enterprise procurement documentation provided as part of contract negotiation.
Most enterprise deployments follow a recognisable pattern.
Your WMS or PIM pushes product data and image URLs to Thriftify's API on item intake. SKU is your reference; Thriftify uses it as the linking key across systems. Async batch processing means your system doesn't wait for AI enrichment.
Thriftify generates the AI listing, applies multi-region configuration, and publishes to eBay (multi-region) and Shopify. Listing IDs returned to your system via webhook for record-keeping.
When an item sells on any marketplace, webhooks fire to Thriftify within 1–2 seconds. Thriftify de-lists from the other channels in another 2–3 seconds. Sale notifications flow to your WMS for fulfilment and to your BI for reporting.
Honest scope statements. If your integration depends on something on the right, raise it during the technical scoping call, some items are on the roadmap, others are explicit non-goals.
If your integration needs a capability not listed on the left, raise it in the technical scoping call. Some items are on the near-term roadmap; others are explicit non-goals where the dashboard UI is the supported surface.
If you're evaluating Thriftify's API for an enterprise integration, the right entry point is a technical scoping call. We'll walk through your volume, your existing stack, and your integration requirements, and tell you honestly whether Thriftify is the right fit.