API Terms of Service

1. Agreement

By creating API keys, registering a developer app, or calling the ThreadzSocial API, you agree to these API Terms. If you use the API on behalf of an organization, you represent that you have authority to bind that organization.

Developer hub: /developers. Production API base: https://www.threadzsocial.com/api/v1.

2. Acceptable use

You may use the API to build tools, dashboards, and workflows that:

• Respect user privacy and platform safety rules
• Display accurate attribution when showing ThreadzSocial content
• Handle keys securely (secrets vault / env; never commit keys)
• Comply with applicable law and our platform Terms

You must not:

• Scrape, bulk-harvest, or mirror the marketplace beyond documented endpoints and rate limits
• Circumvent authentication, rate limits, quotas, or access controls
• Use the API for spam, fraud, phishing, unauthorized automation of purchases, or harassment
• Resell raw API access, share live keys publicly, or use another party’s keys without permission
• Attempt to reverse-engineer non-public systems or exploit bugs without responsible disclosure
• Use sandbox credentials, sandbox listings, or sandbox data as a substitute for production capacity or to serve real end-user traffic

3. Rate limits

We apply rate limits to protect the service. Soft limits may appear as HTTP 429 with code rate_limited and X-RateLimit-* headers. Typical soft stub targets (subject to change):

• Anonymous / no key: about 120 requests per minute per client
• Valid API key: about 600 requests per minute per key

Limits may differ by environment, plan, or risk score. Bursting, rotating IPs or keys to evade limits, or coordinated high-volume scraping is a violation of these Terms. Contact us if you need a higher legitimate quota after production approval.

4. Sandbox vs production

Sandbox keys (stz_sandbox_…) and listings with api_environment = sandbox exist for integration testing only. Sandbox listings are not shown on the public feed and must not be used for real commerce or production end-user traffic.

Live / production keys (stz_live_…) and live data are for approved production use after any required milestones and staff approval. Do not treat sandbox as a free unlimited production environment.

5. Keys, apps & security

You are responsible for all activity under your API keys and developer apps. Store secrets safely; rotate by revoking old keys and creating new ones. We store key hashes, not plaintext secrets, after creation.

Production access may require completing milestones (profile, terms acceptance, sandbox proof) and staff approval of your developer app.

6. Revocation & suspension

We may revoke API keys, suspend or reject developer apps, throttle traffic, or block access at any time — including for Terms violations, security risk, abuse, legal obligations, or to protect users and the platform — with or without prior notice.

You may revoke your own keys anytime in Account → Developer. Revocation does not entitle you to compensation for lost integrations.

7. Data & privacy

Use of personal data obtained via the API must comply with our Privacy Policy and applicable privacy laws. Do not use the API to build competing scrape-based catalogs of user content without permission. Respect user blocks, takedowns, and content removal requests when you cache data.

8. Hub, multi-platform tools & other marketplaces

If your integration creates, updates, or syncs listings, inventory, orders, or credentials involving third-party marketplaces (via Hub, cross-listing helpers, or any future connection APIs), end users of your app remain responsible for each marketplace’s own terms, prohibited-item policies, fees, and seller rules. ThreadzSocial API access does not grant rights on eBay, Etsy, Depop, Mercari, or any other platform, and does not excuse violations of those platforms’ rules.

You must design your product so users authorize connections through consented flows, understand that multi-channel selling can create inventory and policy risk, and do not use our API to scrape or bypass other services. Platform Terms §5 (Hub & other marketplaces) and our Community Guidelines also apply where relevant.

9. Changes; no warranty

The API is provided “as is.” Endpoints, limits, and features may change. We will document breaking changes when practical. Continued use after posted updates constitutes acceptance.

Liability limits and governing law follow the platform Terms of Service unless a separate signed agreement says otherwise.

10. Contact

Questions about API access or these terms: hello@threadzsocial.com, or in-app support when available. See also API docs, platform Terms, and the operator runbook (Docs/DEVELOPER_API.md).

← Back to Developers