Working with Query Parameters and Filters

Query Parameter

GET and PATCH List endpoints require query parameters.

This section describes the syntax and options used for the query parameter. This is a mandatory parameter for List documents.

The standard format for a “query” parameter is to add the parameter as query={} to the end of a GET request for a List document after the parameter delimiter (“?”), where the value of query= is a JSON object:

http://{APIbase_url}/documentList?query={key: value}

Such as:

http://{APIbase_url}/jmJobList?query={"job_no": "12345"}

Note: The query parameter is supported with GET and PATCH requests of List type documents and is not supported by GET requests for Setup or Maintenance documents.

In the simplest form, the value is a single piece of information, such as a string or integer. In more complex forms, the value is a JSON object containing specific formats as described below.

See section regarding URL encoding requirements:

To return items that match a specified string. The string can either be letters or numbers. Wildcard ‘%’ can be used. Remember to URL encode the % sign.

To return items that fall between a specified minimum and maximum numeric value.

To return items that match one of the values provided in a given set of values. See section below on wildcards

To return items that have NULL values. Note: Put pipe characters around NULL to differentiate it from the literal string “NULL”.

(26.3) An explicit test for whether a field is null, as an alternative to the "|NULL|" value above. The value must be a JSON boolean: true returns records where the field is null, false returns records where it is not.

For character-based fields, a null test also matches blank and whitespace-only values, so {"$isnull":true} returns records where the field is null or empty, and {"$isnull":false} excludes both. Numeric and date fields match true nulls only. The "|NULL|" form behaves identically.

To return items that do not match the specified number, string, or NULL.

To return items where values are greater than or less than a given value.

Full GET example for greater than

(11.1) Ability to query where a field's value does not match an array of supplied values. Usage example: {{server}}/PmProjectList?query={"project_desc":{"$notin":["test", "Sarah"]}} Applies to GET queries.

(11.1) Ability to define an array of matching values that all have to match regardless of the order defined. {{server}}/LibMasterList?{"master_desc":{"$LIKEAND":["%Genesis%","%XHD%"]} Applies to GET queries.

(26.3) Ability to combine several groups of criteria where a record only has to match one of them.

$or is a top-level key rather than a field operator. Its value is an array of filter objects. Fields within a group are AND'd together, the groups are then OR'd with each other, and the whole $or block is AND'd with any other criteria in the same query.

The combined example above returns jobs for customer 123 that are either an active type 4, or any type 9:

cust_id = 123 AND ((job_type_no = 4 AND active = 'Y') OR job_type_no = 9)

Any of the filter operators described above can be used inside a group, for example a range in one group and a wildcard match in another:

query={"$or":[{"job_no":{"$range":[100, 199]}},{"job_desc":{"$likeand":["%Genesis%","%XHD%"]}}]}

Fields allowed in a group. Only fields on the primary List table can be used inside an $or group. A field that comes from a related sub-table will fail the request with a "multi-part identifier could not be bound" error rather than returning results, so check the field is part of the List document itself before using it in a group. This is a known limitation - see .

Fields inside a group are subject to the same parameter validation and user column rights as top-level fields.

The Null parameter returns any record that has a null value for the specified key, which indicates that no value has ever been set. This differentiates it from a 0 value for numbers and true or false values for Boolean properties.

Text fields: for character-based fields a null test also matches blank and whitespace-only values, so empty strings are returned alongside true nulls. Date and numeric fields match true nulls only.

Note: Not all fields support null values. If possible, check the OpenAPI definition whether the field allows nulls.

Values

• String values are not case-sensitive.

• DateTime values should be provided in a valid ISO date format.

When using HTML special characters as part of the query value, they must be URL encoded.

Example: to use a wildcard query such as "%dave%", the % needs substituting with %25. Once URL encoded will look like this %25dave%25

Example GET query with URL encoded wildcard : {{server}}/MoMediaOrderList?query={"wo_desc":"%25dave%25"}&resultcolumns={"L": ["wo_no", "wo_desc"]}

(The reason why %dave% fails to return valid results it that %da is the encoding for the Ú character)

This also applies to datetime values that use the offset attribute with the + sign.

To include a value of "2023-06-01T09:00+5:00" in a URL query parameter, substitute + with %2b

Example: query={"wo_begin_dt":{"$range":["2023-06-01T09:00%2b5:00","2023-06-01T17:00%2b5:00"]}}

A field can be matched against several wildcard values at once. Which operator you use depends on whether all of the values must match or any of them:

For example, to find media assets that have both "Tale" AND "Dark" in their "master_desc" field, in any order, use $likeand:

{"master_desc":{"$likeand":["%Tale%","%Dark%"]}}

A single value can also contain more than one wildcard, but that fixes the order. The example below matches only descriptions where "Tale" appears somewhere before "Dark":

{"master_desc":"%Tale%Dark%"}

Remember to URL encode the % symbol (for instance if using Postman) as %25:

{"master_desc":{"$likeand":["%25Tale%25","%25Dark%25"]}}

Used by the GET method on List and Maintenance endpoints.

resultColumns parameter is used to define the fields you wish to return in the response. Without this parameter, the response will contain all document fields which is not recommended for performance reasons.

For example: {APIbaseurl}/JmJobList?Query={"job_no":2}&resultColumns={"L":["job_no","job_desc"]}

Job No. and Job Description fields will be included in the response. Important to include the “L” as the top-level element.

Sub-Table columns

Many endpoints include related sub-tables in their responses. Example syntax to include specific sub-table columns.

Below example fetches a transmission order description and all it's service row numbers:

{APIbase_url}/XmTransmissionOrder/wo_no_seq=7655-1?resultColumns={"jm_work_order":["wo_desc"],"mo_service_row":["service_row_no"]}

Response:

API Pagination is available for the GET Query on List endpoints.

Sort parameters: Syntax: sort=[field1 sort, field2 sort] Example: sort=["job_desc desc", "job_no desc"]

Note: If you don’t specify pageSize, the ‘page’ and ‘sort’ options are ignored. If you do specify a pageSize and do not pass a page, page will default to 1.

Example: To return the first 10 records on page 1 sorted by product_no:

Full example:

The above example queries for jobs that have job numbers in the range of 1 to 67982, returns job number and job description fields but only the 7th page with 5 jobs sorted first by description (descending) then by job number (descending).

The response header will include a parameter called 'Pagination-Count' which is the count of all records as a result of the query.

This will allows you to call for data in manageable payloads without exceeding memory limitations.

This optional parameter suppresses all null value fields from the response payload. Using this parameter reduces the payload size dramatically, especially for larger queries. (v10.6+)

Applicable for all GET calls with List, Maintenance & Report endpoints. Values are ‘ignore’ or ‘include’ (default). 'include' means that all null values are included in the response.

Examples: URL Parameter:- nullvaluehandling=include (default)

URL Parameter:- nullvaluehandling=ignore (recommended)

Notice how all null value fields are omitted.

This optional parameter suppresses additional key fields from the responses. If you do not need to work with key fields other than the primary key, use this parameter to keep the API call performant and reduce the processing overhead when not working with alternate key fields. (v10.6+)

Applicable for all GET calls with List, Maintenance endpoints.

Values are ‘ignore’ or ‘include’ (default). ‘include’ includes alternate keys in the response.

Example: URL Parameter:- alternatekeyhandling=include (default)

URL Parameter:- alternatekeyhandling=ignore (recomended)

Notice how the additional key fields barcode, external_key & umid are omitted.

The REST API uses Date time formats in ISO format with an optional offset value.

e.g. 2014-11-03T22:20:00+00:00

If you omit the offset value when using POST to create a record, you can use a header parameter to set the time zone your dates are using. The advantage of using this header approach, is that it will respect any daylight savings offset applicable to the date given.

e.g. header: Source-Time-Zone-Name: Pacific Standard Time

This example will will create records in the time zone of Pacific Standard Time. Remember to omit the offset values in your time formats.

See link for list of

(11.1)

REST API calls support the ability to pass the Division as an override to the API API user's default Division.

An optional header called "Division-Code" exists where you can include the Division code. This will ensure the correct results are returned for the API users when using Divisions.

The API user account must have been given user access to the division to be able to successfully pass it in the API call. If not, you will receive an error message.

e.g. Division-Code : GS

Using Postman:

This capability replicates the functionality when a user accesses the webapp with their default division, who will see data filtered by their default Division.

Applicable only to sites that use the Division feature.