to 2019-04-01] Changed between two given dates. 1.6.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

to 2019-04-01] Changed between two given dates. 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

to 2019-04-01] Changed between two given dates. 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

to 2019-04-01] Changed between two given dates. 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

changed:[2019-03-01 to 2019-04-01] Changed between two given dates. Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly store the translations, you already have a repository within Weblate can base your integration on. Query Parameters: Request Headers: Response Headers: Response JSON Object: Weblate’s REST API New in component (string) – Component URL slug language (string) – Translation language code q (string) – Search query string Searching (optional) results (array) – array of component objects; see GET /api/units/(int:id)/

to 2019-04-01] Changed between two given dates. 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

to 2019-04-01] Changed between two given dates. 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- (string) – Component URL slug • language (string) – Translation language code • q (string) – Search query string Searching (optional) Response JSON Object • results (array) – array of component objects;

User docs The Weblate Manual, Release 4.14.1 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- format. Parameters • project (string) – Project URL slug • component (string) – Component URL slug Query Parameters • format (string) – The archive format to use; If not specified, defaults to zip; Sup-

1. User docs The Weblate Manual, Release 4.11 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- format. Parameters • project (string) – Project URL slug • component (string) – Component URL slug Query Parameters 116 Chapter 1. User docs The Weblate Manual, Release 4.11 • format (string) – The archive

User docs The Weblate Manual, Release 4.12.1 1.7.5 Exact operators You can do an exact match query on different string fields using = operator. For example, to search for all source strings exactly behaviour for the API, the headers, status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- format. Parameters • project (string) – Project URL slug • component (string) – Component URL slug Query Parameters • format (string) – The archive format to use; If not specified, defaults to zip; Sup-