SUPPORT

Let's get you
moving again.

Start with the request details. Find the right guide. Keep credentials private.

TROUBLESHOOT A REQUEST

Find the next step.

Use the exact response code and request ID from your application.

Check the account connection.

  1. Confirm the key is loaded in your server environment and sent as a bearer credential.
  2. Use the base URL provisioned for the same account. Check for missing or duplicated path segments.
  3. Check whether the account is authorized to use the selected model.
Review authentication →
A FEW THINGS TO KNOW

Frequently asked questions

What should I include in a support report?+

Include a timestamp with timezone, request ID, model ID, HTTP status and a minimal reproduction. Remove API keys, personal data and private input content.

A generation timed out. Should I retry?+

Check the existing request or job status first. A timeout does not prove the generation was never started.

Where do I contact the RunBridge team?+

Prepare a support report using the template below and reach out through the official support channel once account access opens.

PREPARE A SUPPORT REPORT

The details that make a difference.

Make the issue reproducible.

Copy this template, fill in the request details and remove sensitive inputs. Keep it ready for the official support channel when account access opens.

Issue summary:
Timestamp and timezone:
Model ID:
HTTP status / error code:
Request or job ID:
Expected behavior:
Actual behavior:
Steps to reproduce:

Remove API keys and private content before sharing.

One bridge. Your next big idea.

Bring image, video and text models into one development workflow.

Start building ↗