You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in the Projects API, the user-id is used as a parameter for multiple API calls. However, it is not clear which API endpoint can be used to obtain the current user's user-id.
Although inefficient, a possible workaround would be:
To call the Deploy API first, get the apps for the user,
Then use /projects/{project-id}/members for a random app, which the user must be a part of,
Then for each member of that project, try the /users/{user-id}/projects,
And for the member that does not return a 401 but instead a 200, that must be the user's user-id.
The text was updated successfully, but these errors were encountered:
Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: projects-api
Document link: projects-api-v2.md
My Issue/Suggestion
Currently, in the Projects API, the user-id is used as a parameter for multiple API calls. However, it is not clear which API endpoint can be used to obtain the current user's user-id.
Although inefficient, a possible workaround would be:
/projects/{project-id}/members
for a random app, which the user must be a part of,/users/{user-id}/projects
,The text was updated successfully, but these errors were encountered: