RunPod•2mo ago

Requests using RUNPOD_API_KEY fail with 403 unauthorized.

Hello, I'm experimenting with using runpod for running a bunch of one-off jobs. According to the [pods environment variables] page, the RUNPOD_API_KEY is an api key for making api calls scoped to the specific job. Basically, I want to terminate (or at least shut down) the pod once it is done with its task. However when I make a call to the rest api, I get 403 Forbidden and an empty response body. Here is how I am calling the api (nodejs from within the container):

fetch('https://rest.runpod.io/v1/pods/' + process.env.RUNPOD_POD_ID + "/stop", {
  method: 'POST',
  headers: {
    Authorization: 'Bearer ' + process.env.RUNPOD_API_KEY,
    "user-agent": "RE-TEST/1.0.0"
  }
})

fetch('https://rest.runpod.io/v1/pods/' + process.env.RUNPOD_POD_ID + "/stop", {
  method: 'POST',
  headers: {
    Authorization: 'Bearer ' + process.env.RUNPOD_API_KEY,
    "user-agent": "RE-TEST/1.0.0"
  }
})

Any help with this would be highly appreciated

16 Replies

Dj•2mo ago

Hey, the RUNPOD_API_KEY is scoped to the current Pod. I believe something similiar to this is on our roadmap, I can look into it for you in the morning when the rest of the team is available. I guess as a quick workaround you can make the pods with a superuser key in the env with another name? 😅

ajgeiss0702OP•2mo ago

I'm not sure i'm understanding this correctly. If the api key is scoped to the current pod, then why is it failing? Since I am trying to stop the current pod

ajgeiss0702OP•2mo ago

I guess i forgot to mention this, but I also logged the two mentioned variables to be sure they were set, and they were

Jason•2mo ago

maybe, its scoped for only graphql just guessing..

Dj•2mo ago

They're the same auth mechanism, I'm reading the code to make sure I understood this right

ajgeiss0702OP•2mo ago

I set this thread to send me notifications, but its not for some reason. So if you do find an answer, please ping me

Dj•2mo ago

Okay, I don't actually work on our tools so this took me some time to read through and figure out. DeletePod requires ReadWrite permissions, and I'm going to guess (because I can't tell entirely) the API_KEY loaded into the pod only has Read. In the morning, I'll have the engineer who maintains the REST API follow up with you here - so I won't mention you just yet. I'll also look into getting the docs clarified about the permissions the key actually has.

ajgeiss0702OP•2mo ago

ok, thank you!

Dj•2mo ago

@nathaniel Can you help here?

nathaniel•2mo ago

yes, I believe this is a scope issue with the api key that gets generated for the pod. let me check how it’s supposed to work in code if it usually works with things like runpodctl stop which I think I’ve seen people do, then it’s an issue with how rest api parses the scopes

ajgeiss0702OP•2mo ago

i'm using this for now, but in the future i would like to be able to use the pod-scoped key to terminate the pod

nathaniel•2mo ago

that makes sense. will get back to you on this in next few days

ajgeiss0702OP•2w ago

has there been any updates to this? bump 🙂 i've started using the runpodctl command for this usecase instead of the api, and that works. Would like to see the rest api to get some love though, as it appears to be completly broken right now. Any request I send fails, even examples copied from the docs. I'll probably make a post in the new #🔧｜api-opensource forum at some point

Jason•2w ago

so it uses the graphql, and the graphql works but the rest hasnt worked right?

ajgeiss0702OP•7d ago

Correct. Neither terminating/deleting or creating pods has worked with the rest api

Noor Elsheikh•6d ago

Does anyone know how to properly create a pod ("podFindAndDeployOnDemand") with GraphQL? Specifically with an existing volume attached.

Gaming

Programming

Requests using RUNPOD_API_KEY fail with 403 unauthorized.

Did you find this page helpful?