ThreadzSocial
Log in
Developers

Go live

Go live

Production (live) keys operate on the real marketplace. Unlock them by completing the sandbox milestone checklist — then request production for your app.

Path to production

Account → register app → sandbox key → prove /me + sandbox listing → request production → use stz_live_… keys carefully.

Milestone checklist

These map to fields on your developer app (milestone_*_at). Order is recommended; all must be complete before production approval.

  1. 1

    Profile complete

    profile

    Set a username and display name on your ThreadzSocial account so we can identify the app owner.

    Account →
  2. 2

    Accept API Terms

    terms

    Read and accept the API Terms of Use for your developer app.

    API Terms →
  3. 3

    Sandbox key created

    sandbox_key

    Issue a stz_sandbox_… key from your app dashboard on /developers/apps.

    Your apps →
  4. 4

    Authenticated /me

    sandbox_me

    Call GET /api/v1/me with your sandbox key and receive 200 with your profile.

    Auth docs →
  5. 5

    Sandbox listing created

    sandbox_listing

    POST a listing under the sandbox environment. It must not appear on public Discover.

    Listings docs →

App status flow

StatusMeaning
sandboxDefault. Sandbox keys and testing only.
production_pendingMilestones done; awaiting review / approval.
productionLive keys allowed for this app.
suspended / rejectedAccess limited; contact support if unexpected.

Production API host

After go-live, call the production base (same path shape as sandbox testing, with a stz_live_… key):

https://www.threadzsocial.com/api/v1

Example: https://www.threadzsocial.com/api/v1/health, https://www.threadzsocial.com/api/v1/listings.

After approval

  • Create a live key only when you need real marketplace writes.
  • Keep sandbox keys for CI and staging forever — never point production traffic at sandbox.
  • Monitor errors and rate limits; respect API Terms.
  • Prefer idempotent creates: send Idempotency-Key or body external_id on POST /listings so retries do not duplicate inventory.

Related