For a trading affiliate the moment that matters is not the checkout. There is no checkout. The paying event is a lead opening a live account under your link and funding it, and that happens entirely inside a broker's systems where your Telegram cannot see it. The usual workaround is a spreadsheet and a daily login. It works until the volume is real.
PuPrime, like most brokers running an introducing broker programme, publishes an IB access API: your own affiliate account, exposed programmatically, listing the accounts registered under your link and the deposits made on them. Scalegram connects to it so that data lands on the contact record where the conversation already is. Nothing about the connection discloses anything new to the broker. You are reading your own affiliate reporting, in a different window.
The shape of the API decides the architecture
The single most important fact about this class of API is that it answers ranges, not questions. You do not ask "is UID 1234567 funded". You ask for everything that happened between two dates and read the answer yourself. There is no live lookup to hang a conversation on.
That rules out the naive design, where the bot queries the broker at the instant a lead types a number. It would be slow, it would break the conversation while it waited, and it would burn an allowance that has to serve everything else. So Scalegram pulls the ranges on a schedule and keeps the results in a local cache, and every question the product asks about accounts and deposits is answered from the cache with a plain database query.
The cache is what makes the checks in automatic UID checking possible at conversation speed. It is also the same discipline the ads integration uses, and for the same reason, covered in the quota guard.
A cache has an age. An account opened four minutes ago may not be in it yet, which is a normal state and not an error. Any workflow built on this data has to handle "not found yet" as a real answer, because a lead who genuinely just registered will hit it.
Deposits without amounts
Affiliate APIs differ from one another far more than their documentation suggests, and one difference bites hard in this niche: some report that a deposit occurred without reporting how much it was. The feed tells you an account was funded. It does not tell you the figure.
That is not a bug you can code around, and it changes what you may claim. A verified deposit is not automatically a verified amount, so any rule that depends on a threshold has to be checked against something that actually carries a number, or reviewed by a person. Sending a fabricated value into a pixel because the feed did not supply one is exactly the failure described in verified conversions, and it does real damage to value based bidding.
Where the feed does carry amounts, they are the best data in your funnel, because they came from the broker rather than from a lead typing a number into a form.
Connected per bot, not per campaign
The broker connection is attached where the conversation happens. Each bot gets a connect card, so an operator running one bot for a Romanian audience and another for an Italian one can point them at the right affiliate relationship rather than sharing one blurred pool of accounts. The credentials themselves are held once at the account level on the Integrations screen, which is the rule everywhere in Scalegram: connect once, select everywhere else.
Team permissions apply on top. Read, add, write and delete are set per area, and an affiliate feed carrying account numbers and deposit records is not something every person answering messages needs to open.
What it changes in practice
Three things, in order of how much time they save.
The stage moves itself. A contact who registered under your link stops being a lead the moment the account appears in the cache, without anyone updating a tag. The assistant answers accordingly.
The claim gets checked. When a lead says they have opened and funded an account, the number they give is matched against accounts genuinely registered under you, rather than believed. The full handling of every outcome, including the awkward ones, is in verifying a deposit before the VIP invite.
Your commission reporting and your client list stop being two separate stories. Which accounts sit under which contact is on the record, so the question "who is actually producing" has an answer that does not require an export.
The limits worth stating out loud
The feed reports registrations and deposits. It is not a risk system, it is not a compliance check, and it says nothing about whether trading on those accounts is going well. Trading is high risk and most of what happens on a funded account is outside your visibility and none of your business.
Nor does the feed replace your own records. Affiliate reporting is the broker's account of what you are owed, and it is the same document you would want to reconcile against your own count if a commission figure ever looked wrong. Keeping the data in your own storage rather than only reading it in someone else's dashboard is worth something on the day that conversation happens.
Broker programmes also change. Terms, endpoints, what fields are published and which regions are eligible are all the broker's to alter, and an integration is a dependency on somebody else's product decisions. Build the funnel so it degrades to human review rather than stopping, because at some point the feed will be unavailable for a morning. Introducing broker programmes are structured differently from one broker to the next, and the terms matter as much as the API does.
"The feed tells you an account exists and that money arrived. It will not tell you the size half the time, and pretending otherwise is how affiliates end up reporting numbers they cannot defend."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- An IB access API exposes your own affiliate reporting programmatically: accounts registered under your link and deposits on them, with nothing new disclosed to the broker.
- These APIs answer date ranges rather than single lookups, so Scalegram pulls on a schedule into a local cache and answers every question from there.
- Some feeds report that a deposit happened without an amount, so a verified deposit is not always a verified figure.
- The broker connection is attached per bot while credentials live once on the Integrations screen, and any workflow must handle a not yet cached account as a normal outcome.
Frequently Asked Questions
Does connecting an IB API share my clients with the broker?
No. The connection reads your own affiliate account, listing accounts that were already registered under your link. Nothing new is disclosed to the broker by connecting it.
Why is a new account missing from Scalegram?
The data is pulled on a schedule into a local cache, so an account opened minutes ago may not be there yet. Treat it as a normal not yet state and let the workflow fall back to human review.
Can I use the deposit amount for value based ad bidding?
Only where the feed actually publishes an amount. Some report a deposit with no figure attached, and inventing a value to fill the gap is what corrupts value optimisation in the first place.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.