Support channels
Developer Support
Email support@buildmarkets.ai for integration help, technical questions, API issues, scope changes, SDK inquiries, and production access requests.
System Status
Check tappengine.statuspage.io for live
incident reports, component health, and scheduled maintenance windows.
When to use each channel
| Situation | Best channel |
|---|---|
| Integration question, API issue, or production access | Developer Support |
| Active incident or unexpected downtime | System Status (check first) |
| API credential management | Email Developer Support |
| Sample code or open-source tooling | GitHub (github.com/tappengine) |
What to include when contacting support
Including the right information upfront helps the team diagnose and resolve your issue without back-and-forth. When you email Developer Support, provide:- Your company name and Partner Dashboard account email
- Environment — sandbox or production
- The
request_idfrom the API error response (included in every error body) - The error
code— for example,VALIDATION_ERROR - Timestamp of when the issue occurred (UTC)
- Steps to reproduce — the endpoint you called, the request body or parameters, and the full error response
Self-service resources
Most integration questions have documented answers. Check these resources before reaching out:Error Codes
Full catalog of error codes with causes and resolution steps.
Postman Collection
124 pre-built requests organized by endpoint group — ready to run against the
sandbox.
AI Tools
Use llms.txt, llms-full.txt, and the OpenAPI spec to get accurate AI-assisted integration help.
API Reference
Complete endpoint documentation with request schemas, response shapes, and examples.
Requesting production access
When your sandbox testing is complete, email Developer Support with the following:- Your company name and Partner Dashboard account email
- Your integration model — Self-Directed or Wealth Management
- Confirmation that end-to-end sandbox testing is complete
Review the Going Live guide for the full production readiness checklist —
including webhook verification, error handling, and rate limit strategy —
before you request production credentials.