The reference explains the contract, but support questions still need a human path
Use the contact page when you need product help, partnership discussion, or rollout support
The docs should get you to a working integration, but some questions still belong in a direct conversation. If you need product clarification, rollout help, or a broader conversation about how Vidbyte should fit into your workflow, use the contact page instead of trying to reverse-engineer intent from the API reference alone.
Best for
Human follow-up
Use contact when the question is about fit, rollout, support, or relationship rather than one route detail.
When to use it
After docs
Reach out after you have enough context to explain what you are trying to build.
Surface
Contact page
Vidbyte keeps direct outreach on the dedicated contact page.
Good reasons to contact Vidbyte
Reach out when the docs are not the right tool for the question anymore
You need product guidance for a real integration rollout.
You want to discuss how connectors or route families fit your workflow.
You have a support or partnership question that is not answered by the route reference.
Where to go
Use the contact page rather than relying on undocumented assumptions
If the question is commercial, operational, or product-scoped, the safest path is to use the dedicated contact surface and explain what you are building. That is a better path than guessing from implementation details that are not part of the public contract.