Short version: Ampersands break things in API relevance queries. How do you get around this for append operations?
Long version: In another topic, a relevance statement was suggested for use via
/api/query?relevance=... that included ampersands as append operators. This ends up clipping the relevance off at the ampersand and throwing a “This expression could not be parsed” error. Several regulars suggested that the error was due to a syntax error, but the problem is actually the ampersand, which has special meaning in URLs, HTML, and XML, all of which are involved in using the API. Based on some Googling, I tried replacing the ampersands in the query with
& (HTML) and
&amp; (XML) but they both still clip the query.
Is there actually a way to use append operators in a relevance statement to be passed to the REST API?