Overview
J7Tracker HTTP API — deploy, sell and buy tokens.
Same flows as the app, over HTTP. One route, POST {base}/submit, with a JSON body whose type picks the action and whose mode picks the launchpad.
Base URL
Pick the region closest to you. Every base ends in /deploy.
| Region | Base |
|---|---|
| NA East | https://tx-nyc.j7tracker.io/deploy |
| NA West | https://tx-lax.j7tracker.io/deploy |
| Europe | https://tx-fra.j7tracker.io/deploy |
| Asia | https://tx-sgp.j7tracker.io/deploy |
The old nyc / lax / eu / sgp hosts are retired for the deploy API. GET /ping on any base returns latency for region selection.
sniper_wallets and mode: "ansem" requests must go to NA East.
Auth
Authorization: Bearer <jwt>Or put the same JWT in the body as session_id. Wallet signing uses an encrypted api_key from the app — see API keys.
Endpoints
| Method | Path | type | Purpose |
|---|---|---|---|
| POST | /submit | create_token | Deploy a token |
| POST | /submit | sell_token | Sell a % of a wallet's balance |
| POST | /submit | buy_token | Buy with a SOL amount |
| POST | /submit | bundle | Bundle 1–4 buys / sells atomically |
| GET | /ping | — | Returns ok. Call it every 15–30 s to keep the TLS path warm |
Quote-pair lists live on the same hosts under /token/… — see Pair registries.
Requests
- Send the JSON as
Content-Type: text/plain;charset=UTF-8to skip the CORS preflight (browsers / extensions).application/jsonworks too. usernameis taken from the JWT; anything in the body is overwritten.- A response arrives within 30 s (
stroid~45 s), otherwise 504 with an optionallast_status. - Errors are
{ "type": "<action>_error", "error": "…" }. The HTTP layer may also return 401 (bad JWT) or 400 (badtype).