Invalid Time
The provided time is invalid. When time is provided it must be an ISO-8601 date and time (or a Unix timestamp) that TradersPost can read and that is not more than five minutes in the future.
This message indicates that the time value in a signal sent from the TradersPost app, the MCP server or the API cannot be used. When time is provided it must be an ISO-8601 date and time (for example 2026-01-15T14:30:00Z) or a Unix timestamp that TradersPost can read, and it must not be more than five minutes in the future. The request is not processed.
- A webhook request that reaches TradersPost directly (for example from TradingView) is not checked this way: a `time` that cannot be read is ignored and the time of receipt is used. Without a `time` the time of receipt is always used.
The time property is the time your system generated and sent the signal. TradersPost keeps it as you sent it and compares it with the time it received the signal: the difference is the latency shown in the signal log, and the age of the signal is measured from it for rejectAfter. A few minutes of tolerance are allowed for a clock that runs slightly fast.
Invalid time example:
{
"ticker": "AAPL",
"action": "buy",
"time": "next Tuesday-ish"
}
Valid time example:
{
"ticker": "AAPL",
"action": "buy",
"time": "2026-01-15T14:30:00Z"
}
In the examples above, the valid time is a moment TradersPost can read that is not in the future, so the signal is processed.
Ready to put Invalid Time to work?
Free 7-day trial
Set-up in 3 minutes
Paper account for testing
By continuing, you agree to the TradersPost Terms of Service and Privacy Policy. This site is protected by reCAPTCHA.
