We currently have lots of endpoints for freighter-backend but with no documentation which result in devs spending a lot of time trying to figure out what each endpoint does and return as response or else stealing time from Piyral and Aristides to do so.
We could try using Cursor to create a first version of the API docs for each endpoint then review and polish it so devs can easily check what each endpoint is capable of thus increasing the team performance.
See below for all available endpoints as of today:
- "/ping"
- "/price-worker-health"
- "/rpc-health"
- "/horizon-health"
- "/feature-flags"
- "/user-notification"
- "/account-history/:pubKey"
- "/account-balances/:pubKey"
- "/token-details/:contractId"
- "/token-spec/:contractId"
- "/contract-spec/:contractId"
- "/is-sac-contract/:contractId"
- "/scan-dapp"
- "/scan-tx"
- "/scan-asset"
- "/scan-asset-bulk"
- "/report-asset-warning"
- "/report-transaction-warning"
- "/token-prices"
- "/subscription/token"
- "/subscription/account"
- "/subscription/token-balance"
- "/submit-tx"
- "/simulate-tx"
- "/simulate-token-transfer"
- "/onramp/token"
We currently have lots of endpoints for
freighter-backendbut with no documentation which result in devs spending a lot of time trying to figure out what each endpoint does and return as response or else stealing time from Piyral and Aristides to do so.We could try using Cursor to create a first version of the API docs for each endpoint then review and polish it so devs can easily check what each endpoint is capable of thus increasing the team performance.
See below for all available endpoints as of today: