I set up a new API on RapidAPI with a basic GET route (/info) but I’m getting weird results. When I test it using the platform’s built-in testing tool or make requests directly from my browser, the response always shows:
{"info":"kutz-log-nil-tenantid"}
Has anyone else run into this issue? I’m wondering if there’s some setting I overlooked during the setup process. The configuration looks correct to me but clearly something isn’t right. Any ideas what might be causing this unexpected output?
This looks like a tenant ID validation error from RapidAPI’s internal systems. I encountered something similar when I first deployed an API there and it turned out to be related to how RapidAPI handles request routing. The “kutz-log-nil-tenantid” message suggests that the platform isn’t properly associating your API requests with your account’s tenant identifier. Check your API configuration in the RapidAPI dashboard and make sure the endpoint mapping is correctly set up. Also verify that your API is properly published and not still in draft mode. Sometimes republishing the API after making sure all required fields are filled out resolves this kind of routing issue.
sounds like a rapid api middleware issue tbh. ive seen this exact error before and it usualy means the tenant mapping got messed up somewhere. try deleting and recreating the endpoint - i know it sucks but sometimes thats the only fix. also double check your base url isnt conflicting with existing apis on the platform
I had this exact same problem about six months ago and it drove me crazy for hours. The issue is typically with the X-RapidAPI-Host header configuration in your endpoint settings. When RapidAPI can’t properly identify which API instance should handle the request, it defaults to that kutz-log-nil-tenantid response you’re seeing. Go into your API settings and verify that the Host field matches exactly what you have configured in your actual API server. Even a small typo or missing subdomain will cause this error. In my case, I had forgotten to update the host field after changing my server domain, and once I corrected it everything worked perfectly.