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
Ordoro

Ordoro Shipper API

A shipper or carrier account can be created and used to get quotes and generate labels for orders.

Documentation Provider Profile APIs.io OpenAPI GitHub

Ordoro Shipper API is one of 27 APIs that Ordoro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Shipper. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 9 operations across 5 paths, and defines 97 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

9 operations 5 paths 97 schemas 1 DELETE3 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.ordoro.com/
Resource Areas
1

Paths & Operations 9

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

Shipper 9

A shipper or carrier account can be created and used to get quotes and generate labels for orders.

GET
/shipper/
Get a list of Shippers
Shipper_GET 5 params → 200
POST
/shipper/
Create a Shipper
Shipper_POST body → 201
DELETE
/shipper/{shipper_id}/
Archive a Shipper
ShipperByShipperId_DELETE 1 param
GET
/shipper/{shipper_id}/
Get a Shipper by Id
ShipperByShipperId_GET 1 param → 200404
PUT
/shipper/{shipper_id}/
Update Shipper
ShipperByShipperId_PUT 1 param body → 200
GET
/v3/shipper/{shipper_id}/balance
Get balance for shipper's postage
V3ShipperByIDBalance_GET 1 param → 200
POST
/v3/shipper/{shipper_id}/balance
Add balance for shipper's postage
1 param body → 200
POST
/v3/pickup/ups
Schedule a UPS pickup
PickupUPS_POST body → 200
POST
/v3/pickup/fedex
Schedule a FedEx pickup
PickupUPS_POST body → 200

Schemas 97

The contract defines 97 schemas that model the data the API accepts and returns. The most detailed are post_fedex_schedule_pickup (15 properties), update_address (13 properties), shipper_ups_vendor_config (11 properties), pickup (9 properties). Each schema is shown below with its type and property counts.

shipper_fedex_definitions-required_in_response
shipper_pitney_vendor_config_definitions-required_to_create
1 required
shipper_pitney_merchant-2
shipper_ups_definitions-required_in_response
shipper_canada_post
object
one_of_shipper_type
shipper_ups_vendor_config_definitions-required_in_response
11 required
shipper_pitney_vendor_config_definitions-required_in_response
2 required
shipper_dhl
object
post_shipper_ups
object
shipper_fedex_vendor_config_definitions-required_in_response
5 required
post_shipper_dhl
object
shipper_endicia
object
shipper_amazon_vendor_config_definitions-required_to_create
shipper_sendle_vendor_config_definitions-required_in_response
post_fedex_schedule_pickup
object
15 properties 5 required
endicia_account_balance
object
2 properties 2 required
shipper_base_definitions-required_in_response
9 required
shipper_pitney_presort_vendor_config_definitions-required_in_response
put_shipper_ups
object
shipper_canada_post_definitions-required_in_response
shipper_ups
object
shipper_australia_post_definitions-required_in_response
shipper_pitney_merchant_vendor_config_definitions-required_in_response
pickup
object
9 properties 2 required
shipper_fedex-2
shipper_pitney_presort_definitions-required_in_response
shipper_australia_post
object
shipper_pitney_presort-2
shipper_australia_post-2
post_shipper_endicia
object
put_shipper_dhl
object
shipper_dhl_definitions-required_in_response
shipper_fedex_vendor_config
object
Fedex Shipper configuration information
6 properties
shipper_australia_post_vendor_config
object
Australia Post Shipper configuration information
5 properties
shipper_pitney-2
shipper_amazon_vendor_config
object
Amazon Shipper configuration information
2 properties
shipper_ups_vendor_config
object
UPS Shipper configuration information
11 properties
shipper_amazon
object
shipper_base
object
7 properties
shipper_sendle-2
shipper_sendle
object
shipper_fedex
object
update_address
object
13 properties
shipper_pitney_merchant_definitions-required_in_response
put_shipper_endicia
object
post_ups_schedule_pickup
object
8 properties 6 required
put_shipper_xdelivery
object
shipper_dhl_vendor_config
object
DHL Shipper configuration information
2 properties
shipper_canada_post-2
post_shipper_amazon
object
shipper_pitney
object
shipper_sendle_vendor_config
object
put_shipper_australia_post
object
post_shipper_base
object
3 properties 1 required
shipper_pitney_merchant
object
shipper_amazon-2
shipper_pitney_presort
object
shipper_canada_post_vendor_config
object
Canada Post Shipper configuration information
5 properties
put_shipper_newgistics
object
shipper_ups-2
post_shipper_pitney
object
shipper_canada_post_vendor_config_definitions-required_to_create
3 required
shipper_ups_vendor_config_definitions-required_to_create
5 required
post_shipper_australia_post
object
shipper_australia_post_vendor_config_definitions-required_to_create
3 required
shipper_pitney_definitions-required_in_response
shipper_sendle_definitions-required_in_response
shipper_australia_post_vendor_config_definitions-required_in_response
5 required
shipper_pitney_merchant_vendor_config
object
shipper_canada_post_vendor_config_definitions-required_in_response
5 required
shipper_amazon_definitions-required_in_response
ShipperResponse
put_shipper_pitney
object
shipper_dhl_vendor_config_definitions-required_to_create
2 required
post_shipper_canada_post
object
shipper_pitney_vendor_config
object
Pitney Shipper configuration information
2 properties
shipper_endicia_vendor_config_definitions-required_to_create
2 required
shipper_list
object
4 properties 4 required
post_shipper_balance
object
1 property 1 required
shipper_endicia-2
any_of_shipper_type
shipper_fedex_vendor_config_definitions-required_to_create
3 required
shipper_endicia_definitions-required_in_response
shipper_xdelivery_vendor_config
object
X Delivery formerly Onelive X Shipper configuration information
2 properties
shipper_endicia_vendor_config_definitions-required_in_response
6 required
put_shipper_fedex
object
shipper_endicia_vendor_config
object
Endicia Shipper configuration information
7 properties
shipper_newgistics_vendor_config
object
Newgistics Shipper configuration information
4 properties
shipper_dhl-2
shipper_amazon_vendor_config_definitions-required_in_response
2 required
put_shipper_base
object
2 properties
post_shipper_fedex
object
put_shipper_amazon
object
shipper_dhl_vendor_config_definitions-required_in_response
2 required
put_shipper_canada_post
object
shipper_pitney_presort_vendor_config
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ordoro-shipper-api-openapi.yml Raw ↑

Other APIs Ordoro publishes across the network.

Ordoro Address API
AE Profile APIs.io
Ordoro Api Key API
AE Profile APIs.io
Ordoro Authenticated API
AE Profile APIs.io
Ordoro Cart API
AE Profile APIs.io
Ordoro Company API
AE Profile APIs.io
Ordoro Goods Receipt API
AE Profile APIs.io
Ordoro Integration API
AE Profile APIs.io
Ordoro Label API
AE Profile APIs.io
Ordoro Manufacturing Order API
AE Profile APIs.io
Ordoro Order API
AE Profile APIs.io
Ordoro Packing List API
AE Profile APIs.io
Ordoro Postage Account API
AE Profile APIs.io
#Shipper
← Back to O APIs
API Details
ID
ordoro:ordoro-shipper-api
Base URL
https://api.ordoro.com/
Docs
https://docs.ordoro.com/
Provider
Ordoro
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=ordoro-shipper-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ordoro-shipper-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 Ordoro Shipper 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.