Runpod•2mo ago

404 req when using the /status operation

basically what im wrote above i have this link for example "https://api.runpod.ai/v2/sora-2-pro-i2v/status/4867f3cc-2204-464f-bade-3564fve28-e1 " i add auth to the header but always get a 404 response

Jason•10/28/25, 1:41 PM

how does your auth header looks like? replace your api key with APIKEY

JJason how does your auth header looks like? replace your api key with APIKEY

gusoguOP•10/29/25, 2:26 AM

I followed this Template "curl --request GET \
--url https://api.runpod.ai/v2/$ENDPOINT_ID/status/YOUR_JOB_ID \
-H "authorization: $RUNPOD_API_KEY" " what weird is that everything works when I send an asynchronous request "/run" but not when i try to access the status

Jason•10/29/25, 3:59 AM

I usually use bearer token style

Jason•10/29/25, 4:00 AM

Like adding text bearer before the token

Jason•10/29/25, 4:00 AM

I'm not sure why is that but I'd suggest trying the bearer style

Dj•10/29/25, 4:00 AM

You might be seeing a 404 if you have your URL malformed, or maybe the job id just doesn't exist :p

https://docs.runpod.io/serverless/endpoints/send-requests#%2Fstatus

Runpod Documentation

Send API requests to Serverless endpoints - Runpod Documentation

Submit and manage jobs for your endpoints by sending API requests.

Dj•10/29/25, 4:01 AM

If it were your token you'd see a 401 Unauthorized.

DDj You might be seeing a 404 if you have your URL malformed, or maybe the job id ju...

gusoguOP•10/29/25, 4:56 AM

The Problem is when I change the Header I get a 401 response. And I’m taking the id from the generated response from the /run operation

JJason I'm not sure why is that but I'd suggest trying the bearer style

gusoguOP•10/29/25, 4:57 AM

Thanks will try it in the morning

404 req when using the /status operation

Similar Threads

Similar Threads

Similar Threads