Build, Test, and Troubleshoot Faster.

Quick Start

Use your Ringed Horizon API key with the Authorization header on every protected API request.

Authorization: Bearer YOUR_API_KEY

Security: Treat your API key like a password. Do not place it in public repositories, screenshots, browser-side JavaScript, or support tickets.

Authentication

If a request returns 401 Unauthorized, verify all of the following:

• The Authorization header is present.
• The value starts with Bearer .
• The API key has not been copied with extra spaces or characters.
• The API key has not been revoked or replaced.

Authorization: Bearer YOUR_API_KEY

Example Request

Use this basic request to confirm that authentication and API connectivity are working.

curl https://api.ringedhorizon.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"message\":\"Hello\"}"

Note: The exact request format and available model IDs may vary by API version and enabled services.

Connectivity Troubleshooting

1. Check DNS

nslookup api.ringedhorizon.com

If DNS resolution fails, verify your internet connection, DNS configuration, VPN, and local network settings.

2. Check HTTPS and TLS

curl -Iv https://api.ringedhorizon.com

If you receive a certificate error, verify the system date and time and ensure your operating system's trusted CA certificates are current.

3. Check API Health

curl -I https://api.ringedhorizon.com/health

If the host resolves but the connection times out, check outbound HTTPS access, firewalls, proxies, VPN policies, and security software.

Common API Errors

Status	Meaning	What to Check
400	Bad Request	Check JSON syntax and required request fields.
401	Unauthorized	Verify the API key and Bearer authorization header.
403	Forbidden	Check account, organization, plan, or permissions.
404	Not Found	Verify the API hostname, version, and endpoint path.
429	Too Many Requests	Reduce request frequency and review plan or usage limits.
500	Server Error	Retry the request. If persistent, contact support with the timestamp.
502	Bad Gateway	Retry after a short interval. The upstream service may be restarting or temporarily unavailable.
503	Service Unavailable	The requested service or model may be temporarily unavailable.

Rate Limits and Usage

API access is subject to the limits associated with your Ringed Horizon plan.

A 429 Too Many Requests response may indicate that requests are being sent too quickly or that an applicable usage limit has been reached.

Review your account and plan details before retrying large workloads.

Before Contacting Support

Include the following information so the issue can be investigated faster:

• Date and approximate time of the problem.
• HTTP status code.
• API endpoint being called.
• Model requested, if applicable.
• Operating system or application being used.
• Relevant error message.
• Whether the issue happens consistently or intermittently.

Never send your API key, password, MFA code, access token, or other credentials to support.