Skip to main content

Hi,

 

I’m testing a token refresh method that uses OAuth to enable the regular execution of processes that were previously handled via personal access tokens(PAT).

Using a PAT for a specific organization account, we can successfully extract data from organization projects and retrieve all of the following:

  • /v1/teams/:team_id/projects
  • /v1/projects/:project_id/files
  • /v1/files/:file_key

 

However, after switching to OAuth, creating an app, and publishing it with the `file_content:read` and `projects:read` scopes enabled, I can only retrieve `/v1/files/:file_key` data. `/projects` list and `/files` list return a "Not Found" error and cannot be retrieved.

According to the documentation, enabling and publishing the "projects:read" scope should grant access. Why are we receiving a 404 error?

 

I changed the team permissions from 'Can edit' to 'Admin', but I'm still getting 404 errors on the `:team_id` and `:project_id` endpoints. Still I can only retrieve the `:file key`.

 

Is there some additional configuration required when retrieving via OAuth, unlike when using a PAT?

Hi there,
 

Thanks for flagging this!

I noticed that you’ve already submitted a support request regarding this issue and have been in contact with our Technical Quality team (thanks for that!).

I’ll go ahead and close this topic for now, but if anything else comes up related to this issue, please continue the conversation via your existing support ticket.
If you have any other questions outside of this topic, feel free to create a new post here in the forum.

 

For any community members who come across this post, this was related to a known issue that our engineering team has since fixed.

 

Thanks,

Terms & ConditionsCookie settingsAccessibility statement