Calling from mainland China

The function's own URL is on Google's network, which mainland networks can't reach. A seller's server there calls api.sekaibeyond.com instead. That's a Cloudflare Worker, cloudflare/api-relay, which passes each /v1/* request on to https://sekaibeyond.com/api/v1/*:

• Forwarded: only Authorization, Content-Type, Accept, User-Agent and the body.
• Returned: only the response's Content-Type, Allow and Retry-After, plus Cache-Control: no-store.
• Not cached. The key, its scopes and its rate limit are all checked by the API. The relay itself only refuses a body over 64 KiB, and a JSON body Google's servers would turn away (see Errors).
• Not on *.workers.dev: that's blocked in mainland China, so the relay is on its own hostname only.

ReachabilityCopy Anchor Link

Tested on 2026-10-28 from 25 mainland probes (via Globalping): Alibaba, Tencent and Huawei Cloud, and China Telecom, Unicom and Mobile.

Firebase Hosting answered every probe, so sekaibeyond.com/api/v1/* may work from the mainland too once its route is deployed. Test it then before relying on it. The relay stays the supported way in.

Cloudflare's plans below Enterprise serve mainland visitors from outside China, so calls can be slow at peak hours. If they're too slow, point api.sekaibeyond.com at a server in Hong Kong running the same pass-through instead. Nothing in the API or the seller's app changes.

Checking it from the mainlandCopy Anchor Link

No key is needed to see whether the relay is reachable:

curl -i https://api.sekaibeyond.com/v1/events

From anywhere it can reach, that answers 401 with missing-api-key, which comes from the API itself, so the whole path works. To check from mainland networks, run the same URL through a mainland testing service such as ITDOG, then from the app's real server with its key.

Deploying the relay is covered in Deploying the API relay.