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://{APIbaseURL}/documentList?query={key: value}

Such as:

http://{APIbaseURL}/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: URL encoding of special characters

Query Filters

String or Number

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.

Range

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

In

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

Null (empty)

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

NE (not equal)

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

Greater than and less than new query parameters

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

Full GET example for greater than

curl --location --globoff 'http://{APIbaseURL}/LibMasterList?resultcolumns={"L": ["master_no", "master_desc", "date_added","desc_3"]}&query={"title_no":{"$gt": 1102}}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic ******' \
--data ''

NOTIN (Not in)

(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.

LIKEAND (Like and)

(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.

Query Filter Tips

NULL Values

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 an empty string for text-based or date-based properties, a 0 value for numbers, and true or false values for Boolean properties.

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.

URL encoding of special characters

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, it will look like this: %25dave%25

Example GET query with URL encoded wildcard:

{{APIbaseURL}}/MoMediaOrderList?query={"wo_desc":"%25dave%25"}&resultcolumns={"L": ["wo_no", "wo_desc"]}

(Specifically, 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"]}}

Searching for multiple wildcard values

If you want to search for multiple wildcard values contained within a single field that all need to exist, then you can include a list of wildcard values.

For example, if you want to search for media assets that have "Tale" AND "Dark" in their "master_desc" field, you can use the following query parameter:

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

Note you may need to encode the % symbol (for instance if using Postman):

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

Result Columns Parameter

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:

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

Response:

{
    "jm_work_order": [
        {
            "mo_service_row": [
                {
                    "service_row_no": {
                        "external_key": null,
                        "service_row_no": 9933
                    }
                },
                {
                    "service_row_no": {
                        "external_key": null,
                        "service_row_no": 9934
                    }
                }
            ],
            "wo_desc": "WS Transmission Test"
        }
    ]
}

Performance recommendation.
Always use the resultColumns parameter. Otherwise, responses return large numbers of fields, most of which are not required and only add to the system performance overhead. In the future API v3, this will become a mandatory parameter.

Pagination and Sort Parameters

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 specify a pageSize and do not pass a page, the page will default to 1.

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

GET {APIbaseURL}}/JmOrgProductList?query="active":"Y"}&resultColumns="L":"product_no","product_desc"]}&sort="product_no_desc"]&pageSize=10&page=1

Full example:

{APIbaseURL}/JmJobList?query={"job_no":{"$range":[1,67982]}}&resultcolumns={"L": ["job_no", "job_desc"]}&pageSize=5&page=7&sort=["job_desc desc", "job_no desc"]

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 allows you to call for data in manageable payloads without exceeding memory limitations.

Null Value Handling Parameter

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, and Report endpoints.
Values are ‘ignore’ or ‘include’ (default).
'include' includes null values in the response.
'ignore' omits all null values from the response.

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

{
    "L": [
        {
            "barcode": "MM915",
            "company_name": null,
            "cust_id": null,
            "master_desc": null,
            "master_no": {
                "barcode": "MM915",
                "external_key": "VX-90",
                "master_no": 915,
                "umid": null
...

URL Parameter:- nullvaluehandling=ignore (recommended)

{
    "L": [
        {
            "barcode": "MM915",
            "master_no": {
                "barcode": "MM915",
                "external_key": "VX-90",
                "master_no": 915
...

Performance Recommendation
Always include this parameter with the value 'ignore', unless visibility of null values is required.

Alternate Key Handling Parameter

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 and Maintenance endpoints.

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

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

{
    "L": [
        {
            "barcode": "MM915",
            "company_name": null,
            "cust_id": null,
            "master_desc": null,
            "master_no": {
                "barcode": "MM915",
                "external_key": "VX-90",
                "master_no": 915,
                "umid": null
...

URL Parameter:- alternatekeyhandling=ignore (recomended)

{
    "L": [
        {
            "barcode": "MM915",
            "company_name": null,
            "cust_id": null,
            "master_desc": null,
            "master_no": {
                "master_no": 915
...

Performance Recommendation
Always include this parameter with the value 'ignore', unless you are working with alternate keys.

Source Time Zone Name Header

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.

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

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

Division

(11.1)
REST API GET 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

In postman: