API not functional - authentication issues even with read key

TL;DR

Reporter self-solved and documented it (reporter, RowanAldean): two gotchas, (1) EU users must use eu.api.helicone.ai instead of api.helicone.ai (the key was provisioned in an EU region), and (2) the request/query endpoints require a well-formed JSON body from the docs or they return an unhelpful error.

Steps

1. Reporter self-solved and documented it (reporter, RowanAldean): two gotchas, (1) EU users must use eu.api.helicone.ai instead of api.helicone.ai (the key was provisioned in an EU region), and (2) the request/query endpoints require a well-formed JSON body from the docs or they return an unhelpful error. The examples/export typescript script also needs the eu prefix on the target URL.

When to use

You are seeing this: Helicone REST API returns { "error": "No API key found" } for every endpoint, including https://api.helicone.ai/v1/request/query, even with a fresh read/write key, via header and via the https://api.helicone.ai/sk-[key]/... Use this skill when you run into "API not functional - authentication issues even with read key".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://api.helicone.ai/v1/request/query`
• https://api.helicone.ai/sk-[key

In gh:Helicone/helicone#2760 (https://github.com/Helicone/helicone/issues/2760), the question was: Helicone REST API returns { "error": "No API key found" } for every endpoint, including https://api.helicone.ai/v1/request/query, even with a fresh read/write key, via header and via the https://api.helicone.ai/sk-[key]/... URL form. The reporter uses Azure OpenAI through the proxy. The verified resolution: Reporter self-solved and documented it (reporter, RowanAldean): two gotchas, (1) EU users must use eu.api.helicone.ai instead of api.helicone.ai (the key was provisioned in an EU region), and (2) the request/query endpoints require a well-formed JSON body from the docs or they return an unhelpful error. The examples/export typescript script also needs the eu prefix on the target URL.