Skip to main content

​
Support Channels

GitHub Issues

Report bugs, request features, and track known issues. Search existing issues before opening a new one. Your question may already have an answer.

Discord Community

Join our community for real-time help, discussions, and announcements. The #help channel is monitored by the Synap team and experienced community members.

Email Support

For private issues, account questions, or enterprise support, email us at [email protected]. We respond within one business day.

Status Page

Check real-time system status, view incident history, and subscribe to outage notifications. Bookmark this page for quick access during incidents.

​
Follow us

X (Twitter)

Release notes, product updates, and engineering posts. Reply on threads or DM us.

LinkedIn

Company news, hiring, and longer-form posts about agent memory and architecture.

Discord

Live chat with the team and community in #help, #announcements, and #feedback.

​
When Contacting Support

To help us resolve your issue as quickly as possible, please include the following information:
1

Correlation ID

Every SDK response includes a correlation ID. Capture it from the response (or from the error you caught) and include it in support tickets. This ID traces the request through the entire Synap processing pipeline and is the single most useful piece of information for debugging.
2

Instance ID

Include the instance ID where the issue occurred. Format: inst_<hex16>.
3

Timestamp

Provide the approximate time when the issue occurred, including your timezone. ISO 8601 format is preferred.
4

Error message and code

Include the exception class name and message printed by the SDK.
5

Steps to reproduce

If possible, describe the sequence of SDK calls that trigger the issue. Include arguments (with API keys redacted).
Never share your API key or signing secret in support requests, GitHub issues, or Discord messages. Redact them before posting. If you believe a credential has been compromised, revoke it immediately from the Dashboard.

​
SLA Tiers

Response times vary by support tier:
SLA timers run during business hours (9am-6pm PT, Monday through Friday) for Standard and Priority tiers. Critical tier SLAs apply 24/7 including holidays.

​
Reporting Security Issues

If you discover a security vulnerability, please do not report it via public channels (GitHub Issues, Discord). Instead:
  1. Email [email protected] with a detailed description of the vulnerability
  2. Include steps to reproduce the issue
  3. Allow us a reasonable timeframe to address the issue before public disclosure
We take security reports seriously and will acknowledge receipt within 24 hours.

​
Useful Resources

Before contacting support, these resources may help resolve your issue:

Error Codes Reference

Complete list of error codes with descriptions, common causes, and resolution steps.

FAQ

Answers to the most common questions about Synap, the SDK, memory management, and billing.

SDK Overview

Authentication, configuration, and common SDK patterns.

Changelog

Recent changes, bug fixes, and new features. Check here first if something stopped working after an update.

​
Feedback

We actively use feedback to prioritize features and improve the platform. Share your thoughts through any of these channels:
  • Feature requests: Open a GitHub Issue with the enhancement label
  • Documentation feedback: Use the “Was this page helpful?” widget at the bottom of any docs page
  • General feedback: Post in the #feedback channel on Discord or email [email protected]
  • Integrations: Let us know which frameworks and languages you would like Synap to support natively
The best feature requests include a description of the problem you are trying to solve, not just the solution you want. Understanding the “why” helps us design better features for everyone.