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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
ServiceChannel

ServiceChannel OutgoingXml API

The OutgoingXml API from ServiceChannel — 30 operation(s) for outgoingxml.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 30 operations across 30 paths, and defines 4 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.

30 operations 30 paths 4 schemas 16 GET14 POST

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 OutgoingXml 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 30

Across 30 paths, the API surfaces 30 operations — 16 GET, 14 POST. Each is listed below with its method, path, parameters, and response codes.

OutgoingXml 30
POST
/api/notifications/v2/workorders/resend
POSTv3_api_notifications_v2_workorders_resend body → 200
POST
/notifications/v2/workorders/resend
POSTv3_notifications_v2_workorders_resend body → 200
POST
/api/notifications/v2/workorders/notes/resend
POSTv3_api_notifications_v2_workorders_notes_resend body → 200
POST
/notifications/v2/workorders/notes/resend
POSTv3_notifications_v2_workorders_notes_resend body → 200
POST
/api/notifications/v2/workorders/ivr/resend
POSTv3_api_notifications_v2_workorders_ivr_resend body → 200
POST
/notifications/v2/workorders/ivr/resend
POSTv3_notifications_v2_workorders_ivr_resend body → 200
GET
/api/notifications/v2/workorders/{id}
GETv3_api_notifications_v2_workorders_{id} 1 param → 200
GET
/notifications/v2/workorders/{id}
GETv3_notifications_v2_workorders_{id} 1 param → 200
GET
/api/notifications/v2/workorders/cxml/{id}
GETv3_api_notifications_v2_workorders_cxml_{id} 1 param → 200
GET
/notifications/v2/workorders/cxml/{id}
GETv3_notifications_v2_workorders_cxml_{id} 1 param → 200
GET
/api/notifications/v2/workorders/notes/{id}
GETv3_api_notifications_v2_workorders_notes_{id} 1 param → 200
GET
/notifications/v2/workorders/notes/{id}
GETv3_notifications_v2_workorders_notes_{id} 1 param → 200
GET
/api/notifications/v2/workorders/ivr/{id}
GETv3_api_notifications_v2_workorders_ivr_{id} 1 param → 200
GET
/notifications/v2/workorders/ivr/{id}
GETv3_notifications_v2_workorders_ivr_{id} 1 param → 200
GET
/api/notifications/v2/workorders/list
GETv3_api_notifications_v2_workorders_list?proId={proId}&start={start}&finish={finish} 3 params → 200
GET
/notifications/v2/workorders/list
GETv3_notifications_v2_workorders_list?proId={proId}&start={start}&finish={finish} 3 params → 200
GET
/api/notifications/v2/workorders/notes/list
GETv3_api_notifications_v2_workorders_notes_list?proId={proId}&start={start}&finish={finish} 3 params → 200
GET
/notifications/v2/workorders/notes/list
GETv3_notifications_v2_workorders_notes_list?proId={proId}&start={start}&finish={finish} 3 params → 200
GET
/api/notifications/v2/workorders/ivr/list
GETv3_api_notifications_v2_workorders_ivr_list?proId={proId}&start={start}&finish={finish} 3 params → 200
GET
/notifications/v2/workorders/ivr/list
GETv3_notifications_v2_workorders_ivr_list?proId={proId}&start={start}&finish={finish} 3 params → 200
POST
/api/notifications/resetnotify
POSTv3_api_notifications_resetnotify?setupName={setupName} 1 param → 200
POST
/notifications/resetnotify
POSTv3_notifications_resetnotify?setupName={setupName} 1 param → 200
POST
/webhooks/subscribe
POSTv3_webhooks_subscribe body → 200
POST
/webhooks/unsubscribe
POSTv3_webhooks_unsubscribe body → 200
GET
/webhooks
GETv3_webhooks → 200
GET
/webhooks/{id}
GETv3_webhooks_{id}?providerId={providerId} 2 params → 200
POST
/api/notifications/v4/workorders/sendnotify
POSTv3_api_notifications_v4_workorders_sendnotify?setupName={setupName} 1 param → 200
POST
/notifications/v4/workorders/sendnotify
POSTv3_notifications_v4_workorders_sendnotify?setupName={setupName} 1 param → 200
POST
/api/notifications/v4/workorders/status/sendnotify
POSTv3_api_notifications_v4_workorders_status_sendnotify?setupName={setupName} 1 param → 200
POST
/notifications/v4/workorders/status/sendnotify
POSTv3_notifications_v4_workorders_status_sendnotify?setupName={setupName} 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ServiceChannel.Api.Model.OutgoingXml.OutgoingXmlUser (12 properties), ServiceChannel.Services.WebApi.Controllers.OutgoingXmlController.ResendData_System.Int32 (2 properties), ServiceChannel.Services.WebApi.Controllers.OutgoingXmlController.ResendData_System.Int64 (2 properties). Each schema is shown below with its type and property counts.

ServiceChannel.Services.WebApi.Controllers.OutgoingXmlController.ResendData_System.Int64
object
2 properties
ServiceChannel.Services.WebApi.Controllers.OutgoingXmlController.ResendData_System.Int32
object
2 properties
System.Object
object
ServiceChannel.Api.Model.OutgoingXml.OutgoingXmlUser
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

servicechannel-outgoingxml-api-openapi.yml Raw ↑

Other APIs ServiceChannel publishes across the network.

ServiceChannel AfterHours API
AE Profile APIs.io
ServiceChannel AIAgents API
AE Profile APIs.io
ServiceChannel Announcements API
AE Profile APIs.io
ServiceChannel ApplicationAccess API
AE Profile APIs.io
ServiceChannel Assets API
AE Profile APIs.io
ServiceChannel AssetTaskResponse API
AE Profile APIs.io
ServiceChannel AssetTypes API
AE Profile APIs.io
ServiceChannel Attachments API
AE Profile APIs.io
ServiceChannel BatchRfp API
AE Profile APIs.io
ServiceChannel Branding API
AE Profile APIs.io
ServiceChannel Categories API
AE Profile APIs.io
ServiceChannel CheckLists API
AE Profile APIs.io
#OutgoingXml
← Back to S APIs
API Details
ID
servicechannel:servicechannel-outgoingxml-api
Base URL
https://api.servicechannel.com/v3
Docs
https://developer.servicechannel.com/swagger/ui/index?version=3
Provider
ServiceChannel
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=servicechannel-outgoingxml-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/servicechannel-outgoingxml-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of ServiceChannel OutgoingXml 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.