This topic was automatically generated from Slack. You can find the original thread here.
Niel V. : Hey everyone. Is anyone having an issue using the Pipedream API? I’m getting a 404 error “record not found” for all endpoints.
This topic was automatically generated from Slack. You can find the original thread here.
Niel V. : Hey everyone. Is anyone having an issue using the Pipedream API? I’m getting a 404 error “record not found” for all endpoints.
Dylan Pierce : Can you share a few examples?
Niel V. : Here’s a request current user info
Niel V. : Subscription request
Niel V. : Is there something I’m doing wrong on the request side?
Dylan Pierce : Hmm, I’m sorry I’m not able to reproduce. Could you DM me your Pipedream account name?
Dylan Pierce : Tagging in for additional visibility
Dylan Sather (Pipedream) : Thanks for reaching out. Can you confirm the API key at https://pipedream.com/settings/account is the same one that you’re using? Could you try copying and pasting the API key from the Pipedream UI into your shell once more, just to confirm you’re using the same key?
We’ll return a 404 any time the given key doesn’t have access to the resources. Is it possible you have multiple Pipedream accounts and are using the key for one to make requests for resources tied to a separate account?
Niel V. : I am using the API key from the correct account. I haven’t been able to successfully revoke the key for some reason. It is the same API key for the organization I setup, if that helps.
Niel V. : But what’s weird is I receive the same 404 error (record not found) when I don’t pass the authorization header. So the problem might be something else entirely.
Dylan Sather (Pipedream) : The API key you see is actually tied to your user, not the org. Can you try switching to your user context and try revoking the API key there?
Note that some endpoints require you to pass the org_id as a parameter explicitly. See the common params docs for more information on that, if it helps.
Niel V. : I tried to revoke the token in the user context and nothing happens. I tried again 2 more times. The same token remains.
Dylan Sather (Pipedream) : Thanks, I see the issue. Working with the team to address.
Niel V. : Awesome!
Dylan Sather (Pipedream) : Could you try one more time?
Niel V. : It worked. I successfully revoked my API key.
Niel V. : Thanks for your help! I’m going to try API calls.
Niel V. : Unfortunately, I’m still getting a 404 error for API calls.
Niel V. : HTTP/1.1 404 Not Found
Vary: Accept-Encoding, Origin
Content-Type: application/json; charset=utf-8
Transfer-Encoding: Identity
Date: Tue, 18 Oct 2022 13:39:45 GMT
Content-Encoding: gzip
X-Request-Id: c5b8ed25-dfd8-4f3a-9027-d63a5ae8c706
X-Runtime: 0.000944
Cache-Control: no-cache
Connection: keep-alive
{“error”:“record not found”}
Dylan Pierce : Which URL are you attempting to reach?