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
ScanSource

ScanSource Orders API

Sales order creation and management

Documentation Provider Profile APIs.io OpenAPI GitHub

ScanSource Orders API is one of 7 APIs that ScanSource publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 7 operations across 7 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://services.scansource.com/api.

7 operations 7 paths 6 schemas 1 DELETE3 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://services.scansource.com/api
Authentication
API Key
Contact
ScanSource Partner Support
Resource Areas
1

Authentication & Security 1

ScanSource Orders API declares 1 security scheme for authenticating requests. An API key is passed in the header as Ocp-Apim-Subscription-Key (ApiKeyAuth).

  • ApiKeyAuth — Azure API Management subscription key from ScanSource partner portal

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Orders 7

Sales order creation and management

POST
/salesorder/create
Create Sales Order
createSalesOrder 2 params body → 200400401
POST
/salesorder/createAsync
Create Sales Order Async
createSalesOrderAsync body → 202400401
POST
/salesorder/vrd
Create VRD Order
createVrdOrder 1 param body → 200400401
GET
/salesorder/summary/{customerNumber}
Get Sales Order Summary
getSalesOrderSummary 8 params → 200401403
GET
/salesorder/list/{customerNumber}
List Sales Orders
listSalesOrders 7 params → 200401
GET
/salesorder/detail/{customerNumber}/{salesOrderNumber}
Get Sales Order Detail
getSalesOrderDetail 2 params → 200401404
DELETE
/salesorder/cancel
Cancel Sales Order
cancelSalesOrder body → 200400401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are OrderDetail (9 properties), SalesOrderResponse (5 properties), OrderSummaryResponse (4 properties), SalesOrderRequest (4 properties). Each schema is shown below with its type and property counts.

SalesOrderRequest
object
4 properties 2 required
OrderDetail
object
9 properties
AsyncOrderResponse
object
3 properties
OrderSummaryResponse
object
4 properties
OrderListResponse
object
2 properties
SalesOrderResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scansource-orders-api-openapi.yml Raw ↑

Other APIs ScanSource publishes across the network.

ScanSource Availability API
AE Profile APIs.io
ScanSource Invoices API
AE Profile APIs.io
ScanSource Pricing API
AE Profile APIs.io
ScanSource Products API
AE Profile APIs.io
ScanSource Shipping API
AE Profile APIs.io
ScanSource Tracking API
AE Profile APIs.io
#Order
← Back to S APIs
API Details
ID
scansource:scansource-orders-api
Base URL
https://services.scansource.com/api
Docs
https://services.scansource.com/api/Help
Provider
ScanSource
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=scansource-orders-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/scansource-orders-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 ScanSource Orders 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.