Skip to main content

NWS Winter Storm Warning — shipments to Midwest, Pacific, Southeast may be affected. Check carrier tracking for delivery updates.(Source: National Weather Service · Updated 11/17/2026, 3:20:00 AM)

Choose your API access level

These API plans are separate from buyer and seller subscriptions. Review the limits before registering. Every new app starts at Starter; Premium and Commercial require FairClose approval.

Developer API request limits before application registration
API planRequests per minuteRequests per dayAccess and pricing
Starter301,000Initial access after app approval
Premium30020,000Approval required · Contact FairClose for pricing
Commercial1,000100,000Approval required · Contact FairClose for pricing

Each app shares its quotas across all seller connections. Daily quotas reset at 00:00 UTC. Both limits apply; unused requests do not roll over. On HTTP 429, wait for Retry-After before retrying. Existing approved apps retain their established limits until a plan is assigned.

Developer documentation

Start building

API base: https://fairclose.co/api/v1/oauth

1. Register and complete review

Register exact HTTPS callback URLs, a support website, a privacy-policy URL, and the scopes your integration needs. Keep confidential app secrets on your server. Public apps do not receive a secret. All clients require PKCE S256.

My applications

2. Connect a seller

After approval, redirect the seller to the FairClose consent page. Generate a fresh state value and verifier for every request; verify state and issuer on return. Exchange the single-use code on your server. Never place a client secret in browser code or a URL.

Full OAuth authorization guide

Metadata: https://fairclose.co/api/v1/oauth/metadata

3. Call the supported resources

Paths below are relative to the API base. Use the existing seller listing schema for writes. Timeline changes also require publish and end scopes.

Available FairClose OAuth resources
MethodPathScopeBehavior
GET/meprofile.readSeller identity
GET/listingslistings.readOwn listings; limit 1–200, skip ≥0, optional status
GET/listings/{listing_id}listings.readOne owned listing
POST/listingslistings.writeCreate a draft using the seller listing schema
PUT/listings/{listing_id}listings.writeUpdate an owned listing
POST/listings/{listing_id}/publishlistings.publishExisting plan and wallet fee rules apply
POST/listings/{listing_id}/endlistings.endExisting bid and order protections apply
curl "https://fairclose.co/api/v1/oauth/listings?limit=100&skip=0" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Scopes

profile.read — Read your seller identity

listings.read — Read and export your own listings, including drafts

listings.write — Create drafts and update your own listings

listings.publish — Publish your listings under your existing plan and listing fee rules

listings.end — End your listings subject to existing bid and order protections

offline_access — Maintain access while you are away, for up to 30 days

Limits and failures

Access tokens last up to 10 minutes. Offline grants last up to 30 days. Refresh tokens rotate; replace the old token immediately and never reuse it.

Resource limits are shown in the API plan table and in each application's settings. New Starter apps have 30 requests per minute and 1,000 per UTC day shared across seller connections. Premium and Commercial require approval. On 429, honor Retry-After. On 401, refresh once if possible or reconnect. On 403, check scopes and permissions. On 404, verify ownership and the listing ID.

Publishing may debit the seller wallet under existing fee rules. Use drafts during development. This portal does not provide a public sandbox or waive fees.

System status