How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ServiceChannel IssueList API

The IssueList API from ServiceChannel — 36 operation(s) for issuelist.

ServiceChannel IssueList API is one of 66 APIs that ServiceChannel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include IssueList. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 38 operations across 36 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version bearer.v1.

Requests are made against a single base URL, https://sb2fixxbook.servicechannel.com:443/api.

38 operations 36 paths 10 schemas 35 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
bearer.v1
Base URL
https://api.servicechannel.com/v3
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

ServiceChannel IssueList API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. By default, every request must be authenticated.

  • oauth2 — OAuth2 Authorization

Paths & Operations 38

Across 36 paths, the API surfaces 38 operations — 35 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

IssueList 38
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist
The get.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist 2 params → 200
GET
/api/subscribers/{subscriberId}/issuelists
The post.
GETv3_api_subscribers_{subscriberId}_issuelists?keyword={keyword}&pageIndex={pageIndex}&pageSize={pageSize} 4 params → 200
POST
/api/subscribers/{subscriberId}/issuelists
The post.
POSTv3_api_subscribers_{subscriberId}_issuelists 1 param body → 200
GET
/api/subscribers/{subscriberId}/issuelists/history
The get issue list history.
GETv3_api_subscribers_{subscriberId}_issuelists_history?pageIndex={pageIndex}&pageSize={pageSize} 3 params → 200
PUT
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/{issueListId}
The set issue list for dashboard.
PUTv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_{issueListId} 3 params body → 200
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/fields
The get global fields.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_fields 2 params → 200
GET
/issuelist/globalfields
The get global fields. Authorized version of 'storedashboards/{dashboardId:int}/issuelist/fields'
GETv3_issuelist_globalfields?locationId={locationId}&subscriberId={subscriberId}&setupId={setupId} 3 params → 200
GET
/providers/current/subscribers/{subscriberId}/applicationissuelist/globalfields
The get global fields. Authorized version of 'storedashboards/{dashboardId:int}/issuelist/fields'
GETv3_providers_current_subscribers_{subscriberId}_applicationissuelist_globalfields?locationId={locationId} 2 params → 200
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/areas/{areaId}/problemtypes
The get problem types.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_areas_{areaId}_problemtypes 3 params → 200
GET
/subscribers/current/storedashboards/current/issuelist/areas/{areaId}/problemtypes
Get Problem types
GETv3_subscribers_current_storedashboards_current_issuelist_areas_{areaId}_problemtypes?locationId={locationId}&setupId={setupId}&subscriberId={subscriberId} 4 params → 200400401
GET
/providers/current/applicationissuelist/areas/{areaId}/problemtypes
Get Problem types
GETv3_providers_current_applicationissuelist_areas_{areaId}_problemtypes?locationId={locationId}&setupId={setupId}&subscriberId={subscriberId} 4 params → 200400401
GET
/issuelist/problemtypes
Get Problem types
GETv3_issuelist_problemtypes?areaId={areaId}&locationId={locationId}&setupId={setupId}&subscriberId={subscriberId} 4 params → 200400401
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/areas/{areaId}/items
The get items filtered by area type and location.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_areas_{areaId}_items?problemType={problemType}&locationId={locationId} 5 params → 200
GET
/api/subscribers/{subscriberId}/issuelist/headers
GETv3_api_subscribers_{subscriberId}_issuelist_headers 1 param → 200
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/areas/{areaId}/problems
The get problems filtered by area type and location.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_areas_{areaId}_problems?problemType={problemType}&item={item} 5 params → 200
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/issuechoice
The get issue choice.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_issuechoice 2 params body → 200
POST
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/issuechoice
Find issue choice.
POSTv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_issuechoice 2 params body → 200
GET
/subscribers/current/storedashboards/current/issuelist/issuechoice
GETv3_subscribers_current_storedashboards_current_issuelist_issuechoice?problemType={problemType}&equipmentType={equipmentType}&problemCode={problemCode}&locationId={locationId}&setupId={setupId} 5 params → 200
GET
/issuelist/issuechoice
GETv3_issuelist_issuechoice?problemType={problemType}&equipmentType={equipmentType}&problemCode={problemCode}&locationId={locationId}&setupId={setupId} 5 params → 200
GET
/subscribers/current/storedashboards/current/issuelist/specific/issuechoice
Get specific issue choice
GETv3_subscribers_current_storedashboards_current_issuelist_specific_issuechoice?SubscriberId={SubscriberId}&DashboardSetupId={DashboardSetupId}&Trade={Trade}&Priority={Priority}&Category={Category} 5 params → 200
GET
/api/subscribers/{subscriberId}/storedashboards/{dashboardId}/issuelist/issuechoice/fields
The get issue choice fiels.
GETv3_api_subscribers_{subscriberId}_storedashboards_{dashboardId}_issuelist_issuechoice_fields?problemType={problemType}&item={item}&problem={problem} 5 params → 200
GET
/subscribers/current/storedashboards/current/issuelist/areas
Get Areas
GETv3_subscribers_current_storedashboards_current_issuelist_areas?locationId={locationId}&setupId={setupId} 2 params → 200400401500
GET
/issuelist/areas
Get Areas
GETv3_issuelist_areas?locationId={locationId}&setupId={setupId} 2 params → 200400401500
GET
/providers/current/subscribers/{subscriberId}/applicationissuelist/areas
Get Areas
GETv3_providers_current_subscribers_{subscriberId}_applicationissuelist_areas?locationId={locationId} 2 params → 200400401500
GET
/providers/current/subscriber/{subscriberId}/location/{locationId}/applicationissuelist/problemtypes
GETv3_providers_current_subscriber_{subscriberId}_location_{locationId}_applicationissuelist_problemtypes 2 params → 200
GET
/subscribers/current/storedashboards/current/issuelist/areas/{areaId}/equipmenttypes
Get Equipment items
GETv3_subscribers_current_storedashboards_current_issuelist_areas_{areaId}_equipmenttypes?locationId={locationId}&problemType={problemType}&setupId={setupId} 4 params → 200400401500
GET
/issuelist/items
Get Equipment items
GETv3_issuelist_items?locationId={locationId}&areaId={areaId}&problemType={problemType}&setupId={setupId} 4 params → 200400401500
GET
/subscribers/current/dashboard/{setupId}/issuelist/equipmenttypes
Get Equipment items not filtered by location.
GETv3_subscribers_current_dashboard_{setupId}_issuelist_equipmenttypes?areaId={areaId}&problemType={problemType} 3 params → 200400401500
GET
/providers/current/subscribers/{subscriberId}/applicationissuelist/items
Get Equipment items
GETv3_providers_current_subscribers_{subscriberId}_applicationissuelist_items?locationId={locationId}&areaId={areaId}&problemType={problemType} 4 params → 200400401500
GET
/subscribers/current/storedashboards/current/issuelist/areas/{areaId}/problemcodes
Get Problem codes
GETv3_subscribers_current_storedashboards_current_issuelist_areas_{areaId}_problemcodes?problemType={problemType}&equipmentType={equipmentType}&locationId={locationId}&setupId={setupId} 5 params → 200400401500
GET
/issuelist/problems
Get Problem codes
GETv3_issuelist_problems?areaId={areaId}&problemType={problemType}&equipmentType={equipmentType}&locationId={locationId}&setupId={setupId} 5 params → 200400401500
GET
/providers/current/subscribers/{subscriberId}/applicationissuelist/problems
Get Problem codes
GETv3_providers_current_subscribers_{subscriberId}_applicationissuelist_problems?areaId={areaId}&problemType={problemType}&equipmentType={equipmentType}&locationId={locationId} 5 params → 200400401500
GET
/providers/current/applicationissuelist/issueitems
GETv3_providers_current_applicationissuelist_issueitems?subscriberId={subscriberId}&locationId={locationId}&areaId={areaId}&trade={trade}&problemType={problemType} 5 params → 200
GET
/subscribers/current/storedashboards/current/issuelist/field
GETv3_subscribers_current_storedashboards_current_issuelist_field?id={id}&setupId={setupId} 2 params → 200
GET
/issuelist/field
GETv3_issuelist_field?id={id}&setupId={setupId} 2 params → 200
GET
/api/subscribers/{subscriberId}/storedashboards/issuelist/items
The get.
GETv3_api_subscribers_{subscriberId}_storedashboards_issuelist_items?equipmentType={equipmentType}&assetTypeId={assetTypeId}&locationId={locationId}&setupId={setupId} 5 params → 200
GET
/providers/current/subscribers/{subscriberId}/issuelist
Retrieves the issue list for a FTM provider
GETv3_providers_current_subscribers_{subscriberId}_issuelist?assetId={assetId}&locationId={locationId} 3 params → 200
GET
/issuelist/issuechoiceinfo/{trackingNumber}
The get issue choice info.
GETv3_issuelist_issuechoiceinfo_{trackingNumber} 1 param → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ServiceChannel.Services.Messaging.IssueLists.GetIssueChoiceRequest (7 properties), ServiceChannel.Services.Messaging.ErrorResponse (4 properties), ServiceChannel.Services.Messaging.IssueLists.PostIssueListRequest (4 properties), ServiceChannel.Services.Messaging.IssueLists.SetIssueListForDashboardRequest (4 properties). Each schema is shown below with its type and property counts.

ServiceChannel.Services.Messaging.ErrorResponse
object
The error response object
4 properties
ServiceChannel.Services.Messaging.IssueLists.GetProblemsFilteredByAreaTypeAndLocationResponse
object
1 property
ServiceChannel.Services.Messaging.IssueLists.SetIssueListForDashboardRequest
object
4 properties
ServiceChannel.Services.Messaging.IssueLists.GetIssueChoiceRequest
object
Get Issue Choice request
7 properties
ServiceChannel.Services.Messaging.IssueLists.GetProblemTypesResponse
object
1 property
System.Object
object
ServiceChannel.Services.Messaging.IssueLists.IssueArea
object
The issue area.
2 properties
ServiceChannel.Services.Messaging.IssueLists.PostIssueListRequest
object
4 properties
ServiceChannel.Services.Messaging.IssueLists.GetIssueEquipmentTypesResponse
object
1 property
ServiceChannel.Services.Messaging.IssueLists.GetIssueAreasResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

servicechannel-issuelist-api-openapi.yml Raw ↑

Other APIs ServiceChannel publishes across the network.

ServiceChannel AfterHours API
ServiceChannel AIAgents API
ServiceChannel Announcements API
ServiceChannel ApplicationAccess API
ServiceChannel Assets API
ServiceChannel AssetTaskResponse API
ServiceChannel AssetTypes API
ServiceChannel Attachments API
ServiceChannel BatchRfp API
ServiceChannel Branding API
ServiceChannel Categories API
ServiceChannel CheckLists API
Where this information came from

This is an independent, third-party profile of ServiceChannel IssueList API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.