The Weblate Manual 4.3.1
code: fetch(("https://weblate- cdn.com/a5ba5dc29f39498aa734528a54b50d0a/cs.json") .then(response => response.json()) .then(data => console.log(data)); The actual localization logic needs to be implemented repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values0 码力 | 664 页 | 9.34 MB | 1 年前3The Weblate Manual 4.3
code: fetch(("https://weblate- cdn.com/a5ba5dc29f39498aa734528a54b50d0a/cs.json") .then(response => response.json()) .then(data => console.log(data)); The actual localization logic needs to be implemented repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values0 码力 | 662 页 | 9.33 MB | 1 年前3The Weblate Manual 4.4.1
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 703 页 | 9.34 MB | 1 年前3The Weblate Manual 4.4.2
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 703 页 | 9.34 MB | 1 年前3The Weblate Manual 4.3
following code: fetch(("https://weblate-cdn.com/a5ba5dc29f39498aa734528a54b50d0a/cs.json") .then(response => response.json()) .then(data => console.log(data)); The actual localization logic needs to be implemented well. Query Parameters 1.12. Weblate’s REST API 95 The Weblate Manual, Release 4.3 • format – Response format (overrides Accept). Possible values depends on REST frame- work setup, by default json and interface for API. Request Headers • Accept – the response content type depends on Accept header • Authorization – optional token to authenticate Response Headers • Content-Type – this depends on Accept0 码力 | 424 页 | 3.98 MB | 1 年前3The Weblate Manual 4.5.2
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 733 页 | 9.45 MB | 1 年前3The Weblate Manual 4.5.3
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 733 页 | 9.45 MB | 1 年前3The Weblate Manual 4.5
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 714 页 | 9.40 MB | 1 年前3The Weblate Manual 4.5.1
repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in version 2.6: The REST API is available since Weblate the API, the headers, status codes and parameters here apply to all endpoints as well. format – Response format (overrides Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2]). Possible values web browser interface for API. Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] – the response content type depends on Accept [https://tools.ietf.org/html/rfc7231#section-5.3.2] header Authorization0 码力 | 722 页 | 9.40 MB | 1 年前3The Weblate Manual 4.4
status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- work setup, by default json and interface for API. Request Headers • Accept – the response content type depends on Accept header • Authorization – optional token to authenticate Response Headers • Content-Type – this depends on Accept Accept header of request • Allow – list of allowed HTTP methods on object Response JSON Object • detail (string) – verbose description of failure (for HTTP status codes other than 200 OK) • count (int)0 码力 | 418 页 | 3.61 MB | 1 年前3
共 274 条
- 1
- 2
- 3
- 4
- 5
- 6
- 28