Can you help me write or fix my Pine Script or API code?

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.

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.

Step 1 — give the AI our reference pages

An AI tool that has not read our documentation will guess our format, and the guess is usually wrong. Paste these links into your chat with it, and ask it to read them first.

If you are writing Pine Script for TradingView:

Alert Automation — the alert format, every field, and our free Pine library
Connect TradingView — how the alert reaches your account
Field values — the exact values each field accepts
StocksDeveloperAlerts on TradingView — our free, open-source Pine library, which writes the alert text for you

If you are writing your own program against our APIs:

Broker-Independent APIs — what you can build
API reference — every function, parameter and response
Field values — the exact values each field accepts
Client Setup — how to connect from Java, Python, C#, Excel, AmiBroker, MetaTrader or plain HTTP
Postman collection — try the calls by hand before you write code

Or give it one link for everything: stocksdeveloper.in/llms.txt is a plain-text map of our entire documentation, made for AI tools. Most of them can read it in one go and then open whichever page they need.

Step 2 — copy one of these prompts

Paste the prompt into the AI tool, replace the parts in capitals with what you want, and send it.

For a TradingView Pine Script:

Read these pages first, and use only the field names and values they define:
https://stocksdeveloper.in/documentation/alert-automation/
https://stocksdeveloper.in/documentation/api/api-parameters/

I use AutoTrader Web by Stocks Developer. Write a Pine Script v6 strategy that
DESCRIBE YOUR ENTRY AND EXIT RULES HERE, and fires an alert() in the exact
AutoTrader Web alert format so the order is placed in my account.

Use the free StocksDeveloperAlerts Pine library where it helps.
My account name is MY_ACCOUNT.

Then check your own code line by line against those two pages, and list any
field you were not fully sure about instead of guessing it.

For your own program:

Read these pages first, and use only the functions, parameters and values they
define:
https://stocksdeveloper.in/documentation/api/
https://stocksdeveloper.in/documentation/api/api-parameters/
https://stocksdeveloper.in/documentation/client-setup/

I use AutoTrader Web by Stocks Developer. Write LANGUAGE code that
DESCRIBE WHAT YOU WANT IT TO DO HERE.

Then check your own code line by line against those pages, and list any
function or parameter you were not fully sure about instead of guessing it.

That last line matters. Asking the tool to check its own work against our pages catches most mistakes before you ever run the code.

Step 3 — check it before you risk money

AI tools make mistakes, and they sound confident when they do. Never let generated code place a real order until you have checked it.

Check the alert text. Paste the alert message your script produces into the alert checker on the Alert Automation page. It runs the same checks that run when a real alert arrives, and gives you the exact reason if anything is wrong.
Try the API calls by hand first. For your own programs, run the call once with the Postman collection before you put it in code.
Start with the smallest quantity. Run the first live signals with one lot, or the smallest quantity you can, in one account only.
Watch what actually happened. The Alert Trail and your activity log show every alert that arrived and every order that went out, with the reason if one was refused.
Then add the rest. Only after it behaves the way you expect, raise the quantity or point it at a group of accounts.

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.

When this happens