Build against the Tetrees EX API with a clear, safe contract

Quickstart

Prove authentication before calling an owner route

curl --request GET \
  "https://ex.tetrees.ai/api/auth/api-token-status" \
  --header "Authorization: Bearer $TETREES_TOKEN" \
  --header "Accept: application/json"

{
  "authenticated": true,
  "principal": "api_token",
  "accountType": "seller",
  "capability": "read_and_confirmed_seller_prep",
  "permissions": [
    "catalog:read",
    "seller_products:read",
    "seller_prep:quote",
    "seller_prep:confirmed_run",
    "seller_report:read"
  ]
}

Token scope and browser boundaries

A scope-blocked request returns an authenticated 403, not an anonymous 401. This distinction tells you the token worked but the action belongs in the seller console.

Endpoint reference

Base URL: https://ex.tetrees.ai. All protected requests use a bearer token and JSON unless the endpoint returns a short-lived download URL.

Catalog query parameters

curl --get "https://ex.tetrees.ai/api/catalog/products" \
  --header "Authorization: Bearer $TETREES_TOKEN" \
  --data-urlencode "q=payment integration" \
  --data-urlencode "verified=true" \
  --data-urlencode "sort=top_rated" \
  --data-urlencode "page_size=12"

Quote, confirm, then run seller prep

Never reuse a cached price blindly. The quote is size- and version-aware. A version or cost mismatch returns 409 without spending points, and concurrent starts are rejected to prevent double charging.

# 1. Quote the current immutable version and all four tiers.
curl "https://ex.tetrees.ai/api/seller/products/$PRODUCT_ID/prep-quote" \
  --header "Authorization: Bearer $TETREES_TOKEN"

# 2. Copy currentVersion and the chosen tier's points from that response.
curl --request POST \
  "https://ex.tetrees.ai/api/seller/products/$PRODUCT_ID/prep" \
  --header "Authorization: Bearer $TETREES_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "tier": "verified_listing",
    "expectedVersion": "1.0.1",
    "expectedPoints": 956,
    "confirmation": "RUN_SELLER_PREP"
  }'

Postman in four steps

1. 1

   Import

   Download and import the collection. It contains only routes supported by ordinary API tokens.

2. 2

   Set token

   Open collection variables and place your txk_ value in the Current value for token.

3. 3

   Discover IDs

   Run List my seller products. Its test script stores the first productId when one is returned.

4. 4

   Guard spending

   Set allowPointSpend to RUN_SELLER_PREP only after copying the current quote into expectedVersion and expectedPoints.

Errors and debugging

{
  "error": {
    "code": "API_TOKEN_SCOPE_FORBIDDEN",
    "message": "Token authenticated successfully, but this route is outside the token scope."
  },
  "authentication": {
    "authenticated": true,
    "principal": "api_token",
    "capability": "read_and_confirmed_seller_prep"
  }
}