SMS Notification Interface Test
To test the SMS notification interface, please register an account on an SMS platform that supports APIs (SMS Treasure is recommended), and then enter the sent URL into the interface. For example…
To test the SMS notification interface, please register an account on an SMS platform that supports APIs (SMS Treasure is recommended), and then enter the sent URL into the interface. For example http://www.xxxx.com/sms.php?phone=1111111&c={BODY} Test whether the SMS can be received
Parameters
| Name | Default | What it controls |
|---|---|---|
| SMSAPI | http:// | SMS interface |
| Msg | Hello, test successful | sent message |
Source JavaScript
function main() {
if (SMSAPI.length > 10 && SMSAPI.indexOf('http') == 0 && SMSAPI.indexOf('{BODY}') != -1) {
Log('Send: ', Msg);
HttpQuery(SMSAPI.replace('{BODY}', encodeURIComponent(Msg)));
Log('Sending completed, Please check if the SMS is received');
} else {
Log('Parameter configuration error, Please retest the SMS interface');
}
}Published by Zero on the FMZ strategy square · last modified 2014-09-25. Collected in the Quant Trading Vault. Unvalidated research: re-test with your own data and costs before trusting it.
Build this with AgenKit
A spec is not a trading system. Paste this into your coding agent and AgenKit runs a specialist team — architecture, test-first build, risk gates, review — with paper trading on by default.
/agenkit build a production-grade trading bot with a backtest engine, risk controls and paper trading by default from strategies/SMS-Notification-Interface-Test.md- npx agenkit install engineering-kit in your project
- Paste the command into your agent and approve each phase
- Get tests, backtest, risk controls and a paper-trading switch
Understand it first
Before you run this, read the lesson behind the idea and how to backtest it honestly. Specs like this one are the survivors of an unknown number of trials; deflate their results accordingly.