Support

Before you write

Most integration problems are one of these, and each has a page:

Symptom	Read
401 or 412 on the first request	Quick Start → Test the connection and Environments
403 integration_not_permitted	Authentication → provider types
422 validation_failed	Errors
A lead is “missing”	Submissions & Troubleshooting — check the submission log first
202 received and nothing created	Submissions & Troubleshooting → received
429	Rate Limits
A form-builder webhook is rejected	Inbound Forms
The WordPress plugin	WordPress and the plugin’s support forum

Talk to a person

• Book a training session — a walkthrough of Settings → Integrations and the wizard, useful before connecting a form builder or Zapier.
• Request a callback — pick a time and we call you.

Contact

Email support@bytephase.com from the address on your BytePhase account, or use the help option inside BytePhase.

Include:

1. The request id — the X-Request-Id header or request_id in the body. With it we can find the exact request in seconds; without it we are guessing.
2. Your workspace name and the integration’s name as shown in Settings → Integrations.
3. The HTTP status and error.code you received, and roughly when.
4. What you sent (with personal data removed) and what you expected.

Never send an API key. If you believe a key has been exposed, rotate it in BytePhase immediately — the old key stops working at once — and then tell us.

Security reports

Report a security concern about the API to support@bytephase.com with “Security” in the subject. Please do not test against workspaces that are not yours.

Documentation feedback

Every page has an “Edit page” link that opens the source in the public repository. Corrections, clearer wording and better examples are welcome as issues or pull requests.

Elsewhere

• bytephase.com — the product site, with a trial workspace for testing.
• Integration pages with screenshots: Zapier, Typeform, WordPress.
• How it works — the non-technical picture, with links to the blog.

Feature requests

The documented API is deliberately small. If your integration needs something that is not here — a resource, a filter, outbound webhooks — tell us what you are building and why. Demand is how the roadmap is ordered.