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, transla- tor_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 type depends on Accept header • Authorization – optional token to authenticate as Authorization: Token YOUR-TOKEN Response Headers • Content-Type – this depends on Accept header of request • Allow –

contain a simple list of source and translation. Weblate supports the following files: • Files with header defining fields (location, source, target, ID, fuzzy, context, transla- tor_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 automate the navigation). Request Headers • Accept – the response content type depends on Accept header 94 Chapter 1. User docs The Weblate Manual, Release 4.12.1 • Authorization – optional token to

contain a simple list of source and translation. Weblate supports the following files: • Files with header defining fields (location, source, target, ID, fuzzy, context, transla- tor_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 automate the navigation). Request Headers • Accept – the response content type depends on Accept header 94 Chapter 1. User docs The Weblate Manual, Release 4.12 • Authorization – 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, transla- tor_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 type depends on Accept header • Authorization – optional token to authenticate as Authorization: Token YOUR-TOKEN Response Headers • Content-Type – this depends on Accept header of request • Allow –

contain a simple list of source and translation. Weblate supports the following files: • Files with header defining fields (location, source, target, ID, fuzzy, context, transla- tor_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 automate the navigation). Request Headers • Accept – the response content type depends on Accept header 102 Chapter 1. User docs The Weblate Manual, Release 4.13 • Authorization – optional token to

contain a simple list of source and translation. Weblate supports the following files: • Files with header defining fields (location, source, target, ID, fuzzy, context, transla- tor_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 automate the navigation). Request Headers • Accept – the response content type depends on Accept header 94 Chapter 1. User docs The Weblate Manual, Release 4.12.2 • Authorization – optional token to

contain a simple list of source and translation. Weblate supports the following files: • Files with header defining fields (location, source, target, ID, fuzzy, context, transla- tor_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 automate the navigation). Request Headers • Accept – the response content type depends on Accept header 1.12. Weblate’s REST API 105 The Weblate Manual, Release 4.14 • Authorization – optional token