contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization [https://tools.ietf.org/html/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://www.rfc editor.org/rfc/rfc7231#section-5.3.2] header Authorization [https://www.rfc-editor.org/rfc/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://www.rfc editor.org/rfc/rfc7231#section-5.3.2] header Authorization [https://www.rfc-editor.org/rfc/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://www.rfc editor.org/rfc/rfc7231#section-5.3.2] header Authorization [https://www.rfc-editor.org/rfc/rfc7235#section-4.2] – optional token to authenticate

contain a simple list of source and translation. Weblate supports the following files: Files with header defining fields (location, source, target, ID, fuzzy, context, translator_comments, developer_comments) The authentication uses a token, which you can get in your profile. Use it in the Authorization header: ANY / Generic request behaviour for the API, the headers, status codes and parameters here apply the response content type depends on Accept [https://www.rfc editor.org/rfc/rfc7231#section-5.3.2] header Authorization [https://www.rfc-editor.org/rfc/rfc7235#section-4.2] – optional token to authenticate