Droppery REST API

Name: Droppery REST API
Brand: Droppery REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceInventoryapiKey7 EndpointsREST

For Agents

Browse the Droppery dropshipping catalog, place orders, and check inventory and shipment tracking. Useful for storefront agents that need a managed supplier feed.

Install Jentic One Beta

Connect the Droppery REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Droppery 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.

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 | sh

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 instance

Jentic 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 Droppery REST API.

List the dropshipping product catalog via GET /products

Retrieve a single product's details via GET /products/{productId}

Read live inventory counts via GET /products/{productId}/inventory

GET STARTED

Start building with Droppery REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Droppery REST API for, with concrete tasks.

★ Storefront Catalog Sync

Pull the Droppery product list into a Shopify or WooCommerce storefront and refresh inventory regularly so listings reflect supplier stock. The agent calls GET /products on a schedule and GET /products/{productId}/inventory for hot SKUs to avoid overselling on low-stock items.

Call GET /products to list the catalog, then for each productId call GET /products/{productId}/inventory and update the storefront listing with current stock

Order Forwarding to Droppery

Forward storefront orders to Droppery for fulfilment immediately after checkout. POST /orders accepts the product line items and shipping address, and the agent then polls GET /orders/{orderId} for status and GET /orders/{orderId}/tracking for carrier details to surface in the buyer's order page.

On checkout-completed, POST /orders with line items and shipping address, store the returned orderId, and poll GET /orders/{orderId}/tracking until a tracking number is available

Agent-Driven Dropshipping via Jentic

Wire Droppery into agent workflows that source, price, and fulfil products without exposing supplier credentials. Through Jentic the agent searches by intent, loads the schema for the right operation, and executes — the X-API-Key never enters the agent's prompt context.

Search Jentic for 'place a dropshipping order', load the Droppery /orders schema, and execute with line items supplied by the parent storefront agent

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for droppery rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

List products

GET

/products/{productId}

Get a product

GET

/products/{productId}/inventory

Get product inventory

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

GET

/orders/{orderId}/tracking

Get order tracking

GET

/products

List products

GET

/products/{productId}

Get a product

GET

/products/{productId}/inventory

Get product inventory

POST

/orders

Create an order

GET

/orders/{orderId}

Get an order

GET

/orders/{orderId}/tracking

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Droppery X-API-Key values are stored encrypted in the Jentic vault. Agents receive scoped access at execution, so the raw API key never enters the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (for example 'list dropshipping products' or 'place a dropshipping order') and Jentic returns the matching Droppery operation with its input schema.

Time to first call

Direct Droppery integration: half a day for auth and order plumbing. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Droppery REST API through Jentic.

Why is there no official OpenAPI spec for Droppery REST API?

Droppery does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Droppery REST API 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 Droppery REST API use?

Droppery uses an API key passed in the X-API-Key header. Through Jentic the key is stored in the encrypted vault and injected at execution, so it never enters the agent's prompt.

Can I place a dropshipping order with the Droppery REST API?

Yes. POST /orders accepts the line items and shipping details and returns an orderId. Use GET /orders/{orderId}/tracking to retrieve the carrier number once shipped.

What are the rate limits for the Droppery REST API?

The OpenAPI spec does not declare rate limits. Have your agent handle 429 responses with exponential backoff, and confirm your plan's quota with Droppery support.

How do I sync product inventory with the Droppery REST API through Jentic?

Search Jentic for 'check product inventory', load the schema for GET /products/{productId}/inventory, and execute on a schedule for the SKUs you list. Install with pip install jentic.

Does the Droppery REST API expose webhooks?

The current spec only exposes GET and POST endpoints under /products and /orders, with no webhook surface. Use polling on GET /orders/{orderId}/tracking for fulfilment updates.