Log in to the API.
A POST /coins/login with your DrenoxBot user and password (the same ones from the launcher and community) returns a token.
Coin API · Pro and Pro Max add-on
Coin API for GuildBank: your guild's Tibia Coins ledger.
The DrenoxBot Coin API is a read-only Tibia Coins ledger, per account. The bot reads the store packets the Tibia client already receives — balance, history and the transfers you make — and reports them to DrenoxBot. With it, a guild that runs a coin bank sees who sent what, when and to which character, with an audit trail instead of trusting screenshots.
Login, token, then the balance and ledger over HTTP.
With the add-on active, the bot records the coin data the client already receives into your account's private ledger. You read that ledger through an external API.
Get the 7-day token.
The token lasts 7 days. Send it in the Authorization: Bearer header on the following calls.
Read GET /coins.
The response has the current balance — total, transferable and auction — and the ledger of who sent and received coins.
Build your script.
Poll the API over time and compare transactions by id: each new id is a deposit not yet counted.
Full step by step, examples in curl, Python and JavaScript, and the base URL in the Coin API docs.
Reconcile the guild's deposits, no screenshots to trust.
Guilds that run a coin bank — each member sends Tibia Coins to a treasurer character — can check the deposits automatically. Every member's bot logs its coin transfers, so the guild sees who sent what, when and to which character.
An audit trail for the treasury
- Each member enables the Coin API on their own account and shares their token
- A guild tool calls
GET /coinsper member - Balances and transfers become one deposit/withdrawal ledger
- Transparency: who deposited how much, when and to which character
The boundary, honestly
- It is read-only accounting, there are no automated transfers
- Outgoing transfers appear because the player made them in the client
- Each member opts in with their own account and their own add-on
- Without a member's token, the guild cannot see their ledger
The shape of GET /coins.
The balance in total, transferable and auction, plus the transaction ledger with the counterparty, the amount and the kind (received, sent or store). Illustrative example:
{
"balance": { "total": 1250, "transferable": 1100, "auction": 150, "at": 1730000000 },
"entries": [
{ "id": 42, "ts": 1730000500, "delta": 250, "kind": "received", "counterparty": "Guild Banker", "desc": "transfer" },
{ "id": 41, "ts": 1730000100, "delta": -100, "kind": "sent", "counterparty": "Treasurer", "desc": "transfer" },
{ "id": 40, "ts": 1729999000, "delta": -25, "kind": "store", "counterparty": "", "desc": "store purchase" }
],
"sends": [
{ "to": "Guild Banker", "amount": 250, "at": 1730000500 }
]
}
balance — the coin totals, with at for when they were measured. entries — the history: delta is the signed change (+ received / - spent) and kind is received, sent or store. sends — the outgoing transfers the player made in the client.
What the Coin API does not do.
It only observes and reports. That is the boundary, and it is by design.
It never moves coins
- It does not send, withdraw, move or control coins or accounts
- It does not inject or send anything to the game — it only reads the packets the client receives
- Outgoing transfers appear because you made them in the client, never because the API executed them
- There are no automated payouts
Per account and opt-in
- The ledger is per account: you only see your own coins
- A guild aggregates only the accounts whose owners have the add-on and share their token
- Without an active Pro or Pro Max plan and the add-on, the API returns 403
An add-on of R$16.50/month on top of Pro or Pro Max.
The Coin API is not a separate plan. It comes along with an active Pro or Pro Max plan — it does not work on the free trial.
From the panel
With an active plan, the Coin API card in your Panel turns the add-on on, the same as the other add-ons.
At checkout
On a new plan, tick Coin API in the add-on box at checkout: it runs for the same period as the plan, in the same payment.
API panel
Once the add-on is active, the Panel gains the base URL, the endpoints, the balance and ready-made examples in curl, Python and JavaScript, already with your user.
Frequently asked questions.
Does the Coin API move or send Tibia Coins?
No. The Coin API is read-only: it observes and reports. The bot reads the store packets the client already receives and records balance, history and the transfers you made yourself in the client. It never sends, withdraws, moves or controls coins or accounts, and there are no automated payouts.
How do I build a guild Tibia Coins bank with it?
Each member enables the Coin API on their own account and shares their token. A guild tool calls GET /coins per member and aggregates the balances and transfers into one ledger, so you see who deposited how much, when and to which character — an audit trail instead of trusting screenshots.
How much is it and what do I need?
The Coin API is an add-on of R$16.50 per month on top of an active Pro or Pro Max plan — it does not work on the free trial and is not sold on its own. You enable it from the panel or tick it at checkout, the same as the other add-ons.
Which servers does the Coin API work on?
It works wherever the DrenoxBot client runs: today on OTs with the CipSoft client 15.23+ and 15.30 and on OTs with OTClient. Support for RubinOT and Tibia Global arrives with the Pro Max plan in 2027.
Can anyone else read my coins?
No. The ledger is per account and opt-in: you only see your own coins, and a guild only aggregates the accounts whose owners have the add-on and share their own token. Without the token, nobody reads your ledger.