Get the current account
The account the API key acts as
apiKeyAuthorizationBearer <token>The key the team leader created in Redokun, sent as Authorization: Bearer rdk_.... A read key is rejected on every call that writes (any method other than GET, HEAD or OPTIONS).
The account the API key acts as
application/json- response
account*The fields that identify an account wherever one is referenced. A full account representation, if one is ever published, gets its own schema.
links*array<>The resources related to this one. Follow these links instead of building the URLs yourself, so a change of path does not break the client
curl -X GET 'https://api.redokun.com/v1/me'{ "account": { "id": 0, "name": "string" }, "links": [ { "rel": "string", "href": "string" } ]}Links
Follow the links in a response instead of building URLs.
Add or update a translation of a document PUT
Adds a target language to the document, or changes the translators of a language it already has. The `translators` of the body replace the current ones: a translator left out is removed from the language, and an empty list assigns the language to you. Sending the same body again changes nothing. An address of a member of the team (a manager, you included, or a translator) is assigned as it is. Any other address is invited to the team as a translator, within the translator seats of the plan, and receives the invitation by email. A translator invited by a call that fails later stays invited. Each translator who is not you gets a translation job by email, like an assignment from the app. The document can be `UPLOADED` or `INDEXED`. A new language of an indexed document can be translated at once. The translators of a translation can change whatever its status.