I recently set up a new API on the RapidAPI platform and created a basic GET route called /version. However, when I try to test this endpoint using both the built-in testing tool in the dashboard and through my web browser, I keep getting this strange response:
{"version":"kutz-log-nil-tenantid"}
This doesn’t match what I expected my endpoint to return. Has anyone else encountered this specific error message before? I’m wondering if there’s some setting or configuration step that I might have overlooked during the setup process. The endpoint seems to be responding, but clearly something isn’t working as intended.
That error means there’s a tenant ID problem in RapidAPI’s routing system. I’ve seen this before - usually your API config is missing the tenant mapping in the RapidAPI dashboard. Check your API settings in the “Endpoints” section and make sure your route has the right base URL configured. Also verify your actual API server is running and reachable - RapidAPI sometimes throws internal errors when it can’t connect to your backend. The “kutz-log-nil-tenantid” part means their logging caught a null tenant ID, which typically happens with incomplete API setup or failed service connections.
i totally get it, had some issues with api’s too! check your headers and see if ur hitting the right endpoint. sometimes weird stuff happens, so if it keeps acting up, reach out to support. good luck!
This happens when RapidAPI can’t route requests to your actual API endpoint. That “kutz-log-nil-tenantid” response is just RapidAPI’s internal error when their proxy system can’t connect to your backend service. I’ve seen this before - it’s usually because the base URL you entered during registration is wrong or your server isn’t accessible from RapidAPI’s infrastructure. Check that your API server is publicly accessible and the base URL in your RapidAPI config matches exactly what your service expects. Also make sure your endpoint returns the expected JSON response when you hit it directly, not through RapidAPI’s proxy.