For strategy owners
Have a trading strategy? Put it on the record.
This page is for people who wrote their own trading strategy and want a public, tamper-evident track record they can eventually sell subscriptions to. Your strategy tells TrueFills what it trades, and each order is sealed the moment it arrives. Two commands, about two minutes.
- 1
Get your key
Name your strategy on your account page. It shows your API key exactly once, so save it then; we store only a hash and cannot recover it. Registration needs an account, so nobody can take a name they have no claim to and every strategy has an owner from the moment it exists.
Scripting it instead? The same endpoint works with your session cookie.
curl -X POST https://
truefills.com/ api/ v1/ strategies \ -H "Content-Type: application/ json" \ -H "Cookie: amx_session=<your session cookie>" \ -d '{"name": "My Mean Reversion Strategy"}' { "slug": "my-mean-reversion-strategy", "apiKey": "f3a9..." } - 2
Post your first order
One call per trade, as your strategy makes it, with the key as a bearer token. Fills only, so there are no limit or stop orders: the trade is priced at the market the moment it arrives, sealed into your public hash chain, and can never be edited or deleted, by anyone.
curl -X POST https://
truefills.com/ api/ v1/ strategies/ my-mean-reversion-strategy/ orders \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/ json" \ -d '{"action":"buy","symbol":"AAPL","qty":10}' { "sealed": true, "order": { "seq": 0, "hash": "..." } } - 3
Done. Your record is live.
- Public page:
truefills.com/s/my-mean-reversion-strategy. Anyone can verify the chain. - Link the brokerage account it trades. The record is then read from your broker, and the strategy can charge.
- Give the date it began trading and its fills from that day are read in too.
- Every broker-verified bot on the board is sealed every day, and any of them can trade your own brokerage account inside limits you set. See the board.
- Public page:
Rate limits: 5 registrations per hour, 60 orders per minute. Keys are hashed, auth is one header, history is append-only. Everything else lives in the reference.