PRICING

Pay for requests, not seats.

Name: 1688 DataHub API
Brand: eCommDataHub
Availability: InStock

Each DataHub is priced independently. Subscribe monthly for included credits, pay-as-you-go from your wallet, or mix both on the same account.

MONTHLY PLANS

Per-service subscriptions

Every DataHub has its own Starter, Growth and Scale tiers with a monthly credit quota and rate limits. Upgrade or downgrade any time — proration is based on the credits you have left, not days remaining. Invite-only custom plans are available through sales.

PAY-AS-YOU-GO

Account-wide credit wallet

One wallet across all services — $1 = 1,000 credits. Every endpoint has its own credit rate, charged per request once the gateway has accepted the call — whatever the result, including empty results and validation errors; calls the gateway refuses cost nothing. Top up from $5 and set auto top-up when the balance drops below a threshold — the wallet works across every service automatically.

How credits work

$1 = 1,000 credits

Top up the wallet from $5 up to $2,000. Credits never expire while the account is active.

Every endpoint has a rate

A search might cost 5 cr, a detail 3 cr. The rate table is public on every product page and in the docs.

Quota first, wallet second

Subscribed requests draw from your plan's included credits; beyond them they bill from the wallet at your contracted rates.

Stay in control

Auto top-up below a threshold you set, every request itemized in your logs, and hard endpoint-level limits where plans define them.

Fine-tuned limits, one clear rule

Plans can price and limit a whole service, a group of endpoints, or one endpoint on its own. Each field resolves independently: the most specific layer that sets it wins, everything else is inherited.

Rates — the most specific layer wins

Every plan is a layered document: global → group → endpoint. A layer that sets a credit rate replaces the one above it entirely for the endpoints it covers.

Everything a layer doesn't set is inherited

An endpoint that only sets its rate still takes its rate limits and quotas from its group, and whatever the group doesn't set comes from the plan. You only ever override the one number that should differ.

Quotas stack across all layers

Request quotas at every layer count at the same time — a request must fit all of them. A hard quota pauses requests until its window resets; a soft quota keeps serving and bills each extra request at that layer's overage rate.

The credit budget is the plan-wide quota

Included credits are the plan's own budget per day, week or billing period. When it runs out, requests either continue from your wallet at your contracted rates or stop — exactly as the plan defines.

Your copy is frozen

Subscribing freezes the whole document onto your account. If the public plan changes later, you keep the terms you signed up for until you switch plans.

WORKED EXAMPLE

GLOBALWhole plan3 cr/req · 10 req/s

GROUPProduct endpoints5 cr/req · 100k req/day

ENDPOINT/products/search8 cr/req

A CALL TO /PRODUCTS/SEARCH RESOLVES TO

8 cr per requestits own rate — not 5, not 3

100,000 requests/day capinherited from the group

10 requests/secondinherited from the plan

Other endpoints in the group bill 5 cr under the same 100k/day cap; everything else on the service bills 3 cr. All quotas count simultaneously — the daily cap and the plan's credit budget both apply to this call.