Readonly access through the API (creating readonly tokens)
We use the API and this includes automated tests running on the build server.
The problem is that the tests must have a token and this token gives access to it all - including destroying the language projects.
Therefore, in order to be compliant, we need to be able to create tokens which only gives readonly access to the projects.
Thank you.
Peter Larsen
shared this idea
Readonly tokens can now be generated in Account > API Access.
-
Andrew Lane
commented
It would also be great if public projects can be exported with any or no API token.
-
panni
commented
Yes, please. This would be insanely helpful for deployment/CI, as well as information gathering purposes.
-
Ondrej Burkert
commented
We also need it for test environment.
-
Tommy Mikkelsen
commented
For me, in an OpenSource Python project, I use the API to retrieve a list of translated languages, as well as download updated translations.
Sadly though, Python is text based, and since OpenSource, I have to provide the API Key in the code :(
A R/O API key would make me sleep a lot better :D
-
Sergey Eremin
commented
If this is implemented the following idea will be complete too:
https://poeditor.uservoice.com/forums/171919-general/suggestions/6558586-create-badges-similar-to-continuous-build-systemsIt would become possible to create badges like this:
https://img.shields.io/badge/translated-62%25-green.svg
