Trace and Debug Your Fhddos API Calls with Request IDs

Every time you call the Fhddos API — whether for chat completions, image generation, video, audio, embeddings, or reranking — the platform automatically assigns a unique request ID to that call and returns it in the response. You don’t need to configure anything; the ID is always there, ready for you to capture.

Response Headers

Each API response includes the following headers:

Header	Meaning
`X-Oneapi-Request-Id`	Fhddos’s platform request ID — unique per API call
`request-id`	Alias for `X-Oneapi-Request-Id`; included for client compatibility
`X-Upstream-Request-Id`	The upstream provider’s own request ID, if the provider returns one

Request IDs in Error Responses

When a request fails, the JSON error body also carries both IDs so you can correlate errors with headers even when you can’t inspect headers directly:

{
  "error": {
    "message": "Error description...",
    "type": "error_type",
    "request_id": "20260320153045abcdefgh",
    "upstream_request_id": "req_abc123..."
  }
}

Field	Meaning
`error.request_id`	Platform request ID
`error.upstream_request_id`	Upstream provider’s request ID

Read Request IDs in Your Code

cURL
Python
Node.js

Pass the -i flag to print response headers alongside the body:

curl -i https://aiapi.fhddos.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-4o","messages":[{"role":"user","content":"Hello"}]}'

Look for these lines in the output:

X-Oneapi-Request-Id: 20260320153045abcdefgh
request-id: 20260320153045abcdefgh
X-Upstream-Request-Id: req_abc123...

Use with_raw_response to access the underlying HTTP response and read headers directly:

import openai

client = openai.OpenAI(
    api_key="YOUR_API_KEY",
    base_url="https://aiapi.fhddos.com/v1"
)

response = client.chat.completions.with_raw_response.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Hello"}]
)

platform_request_id = response.headers.get("X-Oneapi-Request-Id")
upstream_request_id = response.headers.get("X-Upstream-Request-Id")

print(f"Platform request ID: {platform_request_id}")
print(f"Upstream request ID: {upstream_request_id}")

Call .asResponse() to get the raw Response object and read its headers:

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: "YOUR_API_KEY",
  baseURL: "https://aiapi.fhddos.com/v1",
});

const response = await client.chat.completions
  .create({
    model: "gpt-4o",
    messages: [{ role: "user", content: "Hello" }],
  })
  .asResponse();

const platformRequestId = response.headers.get("X-Oneapi-Request-Id");
const upstreamRequestId = response.headers.get("X-Upstream-Request-Id");

console.log(`Platform request ID: ${platformRequestId}`);
console.log(`Upstream request ID: ${upstreamRequestId}`);

Use Cases

Submit Support Tickets

Always include the platform request ID when opening a ticket. It lets the support team locate the exact call and internal upstream trace within seconds.

Upstream Tracing

If you need to escalate an issue to an upstream provider, supply X-Upstream-Request-Id as the reference. Without it, upstream teams can’t locate the original request.

Programmatic Logging

Capture request IDs in your application code and write them to your own observability system. This gives you end-to-end traceability from your user sessions all the way to upstream providers.

In production, log the platform request ID for every API call. If something goes wrong hours or days later, the ID is the fastest path to a resolution.

​Response Headers

​Request IDs in Error Responses

​Read Request IDs in Your Code

​Use Cases

Submit Support Tickets

Upstream Tracing

Programmatic Logging

Response Headers

Request IDs in Error Responses

Read Request IDs in Your Code

Use Cases