API does not allow access to shared projects
Thank you for a great service! We have been using the POEditor API and stumbled upon a slight issue.
A project can have multiple admins but the API will only allow access to the project owner.
For example, listprojects will not include projects shared by another admin, and viewproject will fail with status 403 ("You don't have permission for this resource") against a shared project.
As a consequence, the admin is forced to share his/her API token with other admins, and this in turn means that other admins will have access to all projects, including those that are not shared with him/her.
If other admins can manage a shared project, it would make sense to provide them the same level of access via the API.
Thanks in advance!
Guilherme Oliveira
shared this idea
You you can manage using your own API shared projects also.
-
Guilherme Oliveira
commented
It works perfectly, thank you very much!
Fantastic incident response time :-)
-
Guilherme Oliveira
commented
I need to share the API, or more correctly, I need to share projects with other admins who are not translators. For translators, the web interface is quite good in our case.
Use case: multiple admins use the API to periodically upload terms and download translations.
The purpose is to ensure a project can be maintained by multiple admins with tools that can automate the process (via the API). Other admins can already access projects that have been shared with them, but only through the web interface - it would be natural to extend this idea to the API.
Of course, we could use a shared account instead, but I do not think that is the best solution.
-
Luigi
commented
Just one question: do you need to share the API or the RESULT of the api?
I'm asking because for example I allow contributors to update the translation on the web pages through a specific PHP page which calls the API.
They don't have the API key, they just have access to one page which makes use of the API.
Not sure if this is what you need....