Last updated 7 September 2026
Can you help me write or fix my Pine Script or API code?
- Our assistant cannot read or debug long code. Pasting a whole script into the chat will not get you a good answer.
- Use an AI coding assistant instead — ChatGPT, Claude, Gemini, Copilot or any other.
- Full guide: Build with AI — prompts to copy, and a start-from-zero section if you have never used one.
- Give it our documentation first, as one ready-made file. Without it, an AI invents field names that fail at your broker.
- We still answer anything about our side — field names, allowed values, why an alert was refused, what our error messages mean.
- Always test before you risk money. Use the alert checker, then start with the smallest quantity.
When this happens
- 1 Pasting a long Pine Script, AmiBroker formula or program into the chat and asking why it does not work.
- 2 Asking us to write a full TradingView strategy, an AmiBroker formula, or a program that calls our API.
- 3 Asking us to review or fix code that somebody else, or an AI tool, already wrote.
Short answer
Our support assistant is built for product questions, not for reading or writing code. A long script does not fit well in a chat window, so it cannot be read properly, and the answer you got back would be a guess. We would rather tell you this than guess.
The fastest way to get code written or fixed is an AI coding assistant — ChatGPT, Claude, Gemini, Copilot, or any other one you already use. These tools are very good at this, and they get much better when you first give them our reference documentation, so they use our real field names and formats instead of inventing their own.
We have written the whole method down for you, including a start-from-zero section if you have never used one of these tools: Build with AI.
What we help with, and what we do not
| Ask us | Ask an AI coding assistant |
|---|---|
| What a field means, and which values it accepts | Writing a full Pine Script strategy |
| Why an alert was refused, and how to correct it | Writing an AmiBroker formula or a MetaTrader script |
| Why an order was rejected by the broker | Writing a program that calls our API |
| What one of our error messages means | Fixing an error inside your own code |
| Whether something is possible with our software | Explaining what a piece of code does |
| The correct alert format for what you want to do | Backtesting logic, indicators and entry rules |
We are also happy to check a short thing — a single alert message, one field, or one line you are unsure about. It is only long code that we cannot work with. And if we are not certain about something, we will say so and send you here rather than guess — a made-up field name is worse than no answer, because you only find out when an order fails.
One thing never changes: we are a software tool only. We do not provide, sell or recommend trading strategies, so we cannot tell you what your code should decide. The strategy is always yours.
The faster route, in three steps
The full guide — with prompts you can copy and a walkthrough for people who have never used an AI tool — is Build with AI. The short version:
- Give the AI our documentation first. We publish it as one ready-made file, so this is a single upload:
stocksdeveloper.in/ai/alert-automation.txtfor TradingView and Pine Script,stocksdeveloper.in/ai/trading-api.txtfor your own program. An AI that has not read our reference invents field names that look right and fail at your broker. - Ask for what you want, then ask it to check itself. End your message with “check your code line by line against that reference, and list any field you were not sure about instead of guessing it”. That one line catches most mistakes before you run anything.
- Test before you risk money. Paste the alert message into the alert checker, or run one call with the Postman collection. Then start with the smallest quantity, in one account, and watch the Alert Trail and your activity log before you scale up.
Never paste your API key, your password or your private webhook link into an AI chat.
If a check fails and you cannot work out why, come back to us with the one alert message, or the one error you saw — that we can answer quickly.
Why we work this way
Support here is free, and it answers most questions in seconds because it stays with what we can be certain about: our own software, our own formats and our own error messages. Reading and debugging your strategy code is a different job, it is slow, and the answer would often be a guess dressed up as an answer.
Handing an AI assistant our reference documentation gets you a better result in less time, and you keep full control of your own code and your own strategy.
