Please. I'm not asking for perfection. I'm asking for sanity.

India wants to lead in fintech. But under the hood we’re playing Jenga with undocumented APIs, inconsistent casing, and error messages that gaslight you.

This is just one broker. I have five more to go. Each one is its own psychological thriller. By the end of this I’ll have trust issues and a PhD in reverse engineering.

It’s not just inconsistent. It’s deliberately confusing. Case sensitivity roulette. Typos in field names. Same word spelled three different ways across three endpoints. This codebase has beef with developers.

Every morning, before you can place a trade, you must bow before the holy CSV. Manually updated, spiritually cursed, forever essential. Miss a code? Trade fails. This is not a pipeline. This is a pilgrimage.

Want to place an order? You must: Download a CSV from the broker Look up your symbol fetch the scripcode Send *both* in the API request It’s automated trading, brought to you by Microsoft Excel and prayers.

Error handling? They respond with 200 OK, but inside the body: Oh cool, so everything’s broken but legally it’s fine. The gaslighting is industrial-grade.

The documentation refers to “ScripCode.” Except they spelled it… ScriCode. I thought it was a trap. It wasn’t. It’s just bad spelling in production docs.

One response has two status keys. One is Status, one is status. They mean different things. You’d think this is a joke. It’s not.

Fun twist: You do need to send a key in the body. but also a JWT in the headers. Guess what’s inside the JWT? ANOTHER key. It’s keys all the way down. This API was designed by a locksmith with a grudge.

Want to call API? You must include a Head block. But not in the headers—no no—in the body. And inside it? A Key. Or maybe key. It’s like they let a Java dev and a Node dev argue and just pushed both versions to prod. Surprise, it is .NET

The API docs have example responses. They look fine… until you realize they’re fictional. Fields are missing, extra, or spelled like a drunk intern named them at 4 AM. You’d get more accurate info from reading tea leaves.

I’m building a bridge between Indian brokers. This isn’t just bad tech. This is a shrine to chaos. And I need to say this out loud: The current state of Indian fintech is a dumpster fire held together with Excel, prayer, and lies.

Adventures in Indian Fintech Hell The docs are fake. The responses lie. The CSV is holy. #Fintech #IndiaTech #DevHumor #TradingAPI #AlgoTrading #IndianStartups #DigitalIndia #TechTwitter #APIDesign #SoftwareEngineering

We are bootstrap startup looking for our super 100 users. We are in Personal Finance space. working on giving wall street level tools to common people in india. please check us here