Connect through Spotware
Users authorize cTrader access through Spotware OAuth. Markitel never asks for or stores a cTrader password.
No-index preview - not a live Store listing
Approved Open API path, Store path still separate
Markitel as the cTrader engagement layer.
A lightweight cTrader-facing wrapper for Spotware OAuth connection, signal rationale, education, and guided trade workflows. Markitel complements cTrader; it does not replace cTrader execution, charting, or platform UX.
Review signal rationale
The wrapper points traders into Markitel's evidence-scored signal explanations and education loop.
Keep execution controlled
Execution-related actions remain behind Markitel's separate product gates, risk controls, and user authorization.
Support and disclosures
The preview keeps support, privacy, terms, and risk disclosures one click away for Store review.
Before Store submission
- Confirm with Spotware whether the correct Store lane is WebView plugin, external Open API app listing, broker package, or a combination.
- Complete seller or reviewer requirements requested by cTrader Store before submission.
- Capture screenshots from real product states only; do not mock connected-account proof.
- Use connect-only or demo-account proof for the first review unless Spotware explicitly requires execution proof.
Questions for Spotware
These are the review-path answers Markitel needs before packaging the Store product. The preview stays connect-first until Spotware confirms the distribution shape.
- 1Should Markitel v1 be a WebView plugin wrapper, a direct Open API app listing, a broker package, or a combined route?
- 2Which category, tags, screenshot sizes, logo sizes, seller steps, and reviewer credentials should we prepare?
- 3Can first review pass with connect-only or demo-account evidence, or does Spotware want demo-execution evidence before submission?
- 4Can the listing say "approved Open API app" without implying an official endorsement beyond the actual approval?