Contact & Review FAQ
This page bundles the contact path, review expectations, and the questions PU Prime or another broker team typically wants to clarify before a live pilot.
Contact Path
For partnership, operations, or integration teams, communication currently runs centrally through GramGrow. This avoids scattered requirements and lets us coordinate review, payload questions, and pilot access consistently.
Email: admin@gramgrow.io
Subject: PU Prime Pilot Access
Suggested content:
- team / role
- review goal
- technical contact
- preferred timeline
- available API docs or sample exportWhat We Need From a Broker Team
For a fast live step
- Official reporting or partner API documentation
- An anonymized sample export or example response
- Clarification of the allowed read-only scope
- Available keys for matching and reporting, such as broker UID, external ID, and timestamps
- Whether the integration is pull-only or whether webhooks / postbacks are possible
What GramGrow Provides During Review
| Area | What Is Provided |
|---|---|
| Pilot workspace | Read-only review environment on the official domain |
| Connector flow | Production-style UX for official API / reporting-based broker integration |
| Data model | Controlled demo payloads with shared-ID and event mapping |
| Security boundary | No trades, no mutations, no public credentials |
FAQ
Can real broker data be viewed in the pilot?
No. The documentation and the pilot intentionally show controlled demo data only. Real broker data is only introduced after approval, scope confirmation, and field validation.
Is GramGrow about trading or account control?
No. GramGrow focuses on reporting, attribution, and operational visibility. Trading, order creation, or account mutations are intentionally outside the scope.
Which teams should review the docs?
Typically partnership, integration, operations, and when necessary compliance or security. The pages are structured so that not only a developer but also a business reviewer can quickly understand what is being shown.
What is the fastest path into a real live pilot?
A read-only scope, an anonymized sample export or sample response, and a short auth description are usually enough to close the live mapping quickly.