List all issues

Updated:

GET/qms/{connection_id}/issue

Returns a list of QmsIssues. Narrow the results with the query parameters before paging, then page through them with limit and offset (the default and maximum page size depend on the integration). Use fields to return only the fields you need and reduce the response size. When the integration supports a total count, it is returned in the X-Total-Count response header. Use each item's id to retrieve, update, or delete it where those operations are supported.

Parameters

limitnumber default=100
offsetnumber default=0
updated_gtedate-time
Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
sort enum
order enum
querystring
Query string to search. eg. email address or name
status enum
type enum
part_idstring
The PLM part ID to filter by
user_idstring
The user/employee ID to filter by (reference to HrisEmployee)
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Returns

A nonconformance, complaint, audit finding or problem report

idstring
created_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
numberstring
Issue number, e.g. NCR-0042
namestring
descriptionstring
type enum
Valid values:
"NONCONFORMANCE"
"COMPLAINT"
"AUDIT_FINDING"
"PROBLEM_REPORT"
"OTHER"
original_typestring
The vendor's own issue type or template name
status enum
Valid values:
"OPEN"
"IN_PROGRESS"
"IN_REVIEW"
"CLOSED"
"CANCELLED"
Normalized status of a quality record
lifecycle_statestring
Vendor's own state or workflow step name
severity enum
Valid values:
"LOW"
"MEDIUM"
"HIGH"
"CRITICAL"
source enum
Valid values:
"INTERNAL"
"SUPPLIER"
"CUSTOMER"
"AUDIT"
"OTHER"
Where a quality issue was found
disposition enum
Valid values:
"USE_AS_IS"
"REWORK"
"REPAIR"
"SCRAP"
"RETURN_TO_VENDOR"
What to do with the nonconforming material
original_dispositionstring
The vendor's own disposition name
affected_items array
supplier_namestring
user_idstring
Owner or assignee (reference to HrisEmployee)
reporter_user_idstring
Who raised the issue (reference to HrisEmployee)
action_idsstring array
Linked QmsAction IDs
change_idsstring array
Linked PlmChange IDs, when the same vendor also provides PLM
opened_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
due_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
closed_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
file_idsstring array
Attachment IDs retrievable from StorageFile
urlstring
Deep link to the vendor UI
metadata array

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'GET',
  url: 'https://api.unified.to/qms/5de520f96e439b002043d8dc/issue',
  headers: {
    authorization: 'bearer .....'
  },
  params: {
    limit: 50,
    offset: 0,
    updated_gte: '2026-01-01T00:00:00.000Z',
    sort: 'updated_at',
    order: 'asc',
    query: '',
    status: '',
    type: '',
    part_id: '',
    user_id: '',
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?