Request headers and app attribution
X-APP-NAME and X-APP-URL are optional attribution metadata. They do not authenticate requests or change model IDs. Examples comment them out by default. Enable them with real app details to avoid attributing unrelated sample traffic to one placeholder app.
| Header | Value |
|---|---|
| Authorization | Bearer $INONEAPI_API_KEY |
| x-api-key | Anthropic Messages / count_tokens: InOneAPI API Key |
| anthropic-version | 2023-06-01 (Messages clients) |
| Content-Type | application/json; multipart uploads use the client-generated boundary |
| X-APP-NAME | Optional application name |
| X-APP-URL | Optional application HTTP(S) URL |
| X-Gateway-Trace-ID | Response header; not a replacement for an API Key |
Names are whitespace-normalized and capped at 120 Unicode characters. URLs retain only a normalized HTTP(S) origin, without paths, queries or fragments. Fallbacks include X-Title, Referer, HTTP-Referer and recognized User-Agent products. Omitting the two explicit headers does not necessarily disable attribution.
# -H "X-APP-NAME: Your App Name"
# -H "X-APP-URL: https://your-app.example.com"
curl "https://api.inoneapi.com/v1/chat/completions" \
-H "Authorization: Bearer $INONEAPI_API_KEY" \
-H "Content-Type: application/json" \
--data '{
"model": "YOUR_MODEL_ID",
"messages": [
{
"role": "user",
"content": "Hello"
}
]
}'Authentication · SDKs · Trace