Office Order Service Transaction Guide Sep 2020

FedEx Web Service for Office and Print
FedEx Office Order Service

Transaction Guide
September 2020
Confidential and Proprietary
The information contained in this Transaction Guide is confidential and proprietary to FedEx
Corporate Services, Inc. and its affiliates (collectively "FedEx"). No part of this Transaction
Guide may be distributed or disclosed in any form to any third party without written permission
of FedEx. This Transaction Guide is provided to you under, and its use is subject to, the terms
and conditions of the Developer Resource Center License Agreement and the FedEx Web
Services End User License Agreement. The information in this document may be changed at
any time without notice. Any conflict between this Transaction Guide, the Developer Resource
Center License Agreement, and the FedEx Web Services End User License Agreement shall be
governed by the FedEx Web Services End User License Agreement and the Developer
Resource Center License Agreement, in that order.
© 2020 FedEx. FedEx and the FedEx logo are registered service marks. All rights reserved.
Unpublished.
i
About the Guide
This guide serves as a supplement to the FedEx Web Service for Office and Print Developer
Guide and describes how to work with the Office Order Web Service transaction set.
It is written for the application developer who uses web services to design and deploy
applications enabled by FedEx. The guide includes element descriptions, samples, and error
codes. Request elements are designated as required (R), optional (O), or conditional (C).
Resources
The following may also be useful for the FedEx Web Service for Office and Print developer:
• FedEx Developer Resource Center for FedEx Office:
http://www.fedex.com/us/developer/web- services/office/index.html
• FedEx Office Print Online: printonline.fedex.com
• Web Services Interoperability: www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html
• Web Services Description Language (WSDL) explained: msdn.microsoft.com/en-

us/library/ms996486.aspx
• O’Reilly XML.com: xml.com
Support
Integration Consultants
A FedEx Office Web Integration Solutions Consultation team member can assist you in the pre-
production stages of integration. Contact your FedEx Office account executive or email
officewebservices@fedex.com to request a consultation.
A consultant will contact you within 3 business days.
Email Support
Email OfficeWSProdSupport@fedex.com, and we’ll send your request to our internal team of
FedEx Office Web Services specialists for print services. They will address your questions as
quickly as possible.
ii
Revision History
The following table provides the reader with a history of the significant additions, deletions, and
corrections made to this document.
Version Revision
September 2009 Initial document. Contents correspond to functionality associated with first
release of FedEx Office Order Web Service.
January 2010 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service in January 2010.
New features:
• File type support extended
Office Order Service now accepts the upload of documents saved in
the following formats: text, rich text, Adobe® PDF, Adobe
PostScript®, Microsoft® Word, Microsoft Excel® and Microsoft
PowerPoint®.
• Special instructions
As a supplement to the direct selection of print, finishing and fulfillment
options via Office Order Service, free-form instructions can now also
be submitted to FedEx Office when an order is placed.
• Payment via major credit card
Acceptable forms of payment now also include the following major
credit cards: American Express®, Diners Club®, Discover®,
MasterCard® and Visa®.
Miscellaneous revisions:
• Notification Codes updated
• Media Categories and Descriptions updated to reflect new/revised
options
• Finishing Thresholds corrected for Comb Binding
July 2010 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service in July 2010.
New features:
• Multi-file support
Office Order Service now supports the upload and association of
multiple digital files with an order.
• Multi-document support
Office Order Service has been enhanced to support the order of
multiple items on a single order
• Multi-section support
iii
Office Order Service now provides customers with the flexibility to
declare print and finishing options (where applicable) on a section by
section basis within their print order.
Miscellaneous revisions
• Center ID is no longer limited to use with only pickup delivery group.
When an order is to be shipped, you can now set the Center ID where
you would like it produced. Previously, the production center was
automatically selected based upon the recipient’s address.
June 2011 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service in June 2011.
New features:
• Promotion codes accepted
Office Order Service now accepts promotion codes so that customers
can take advantage of special FedEx Office discount offers (where
applicable).
• Lamination functionality added
Office Order Service now accepts the lamination finishing option.
May 2013 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service.
New features:
• Corporate Catalog Integration
Office Order Service now allows customers to request catalog
documents in an order.
• Direct Mail
Direct mail is now available as a delivery method. Note: Prior
approval is required.
• Simplified Paper Options
Removed media types and sizes that are no longer supported.
• Additional Customer Reference Type
Supports an additional customer reference type for populating a P.O.
number reference on the order’s corresponding shipping label.
October 2013 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service.
New features:
• FedEx Office Local Delivery
Local delivery (by the FedEx Office location producing the order) is
now available as a delivery method.
• Phone Number Extension
A phone number extension may now be populated for the order
contact and order recipient.
iv
September 2014 Corrected FEDEX_2DAY to FEDEX_2_DAY in ServiceType enumerated lists
to align with Office Order WSDL
September 2015 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service:
Tabs and Inserts can now be added to a document’s print options.
February 2016 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service.
New features:
• Color printing on color paper is now available.
Prepare for Payment Service Updates:
• The credit card processor will only accept alphanumeric characters in
the P.O. number and customer reference fields. If special characters
are entered, they may be removed before transaction is sent to credit
card processor, in which case the integrator would receive a
notification that the special characters may be removed.
• Postal code will be required to support credit card validation.
July 2016 Document updated to reflect new functionality incorporated into FedEx Office
Order Web Service:
Media Category table has been updated to include more options and SKU
numbers for cross reference purposes.
New features:
• FedEx Office Account number and FedEx Shipping Account number
will now be referred to as FedEx Account number.
• Payment Service Update
With the change of the payment service used for credit card authorization
and processing, the following improvements will now be in effect that
further increase the quality of this service:
i. CVV (Card Verification Value) field has been added. To reduce
fraud, it is recommended to capture CVV for validation for online
transactions.
ii. Zip Code Validation will be performed by the credit card processor.
If billing zip code does not match zip code tied to the credit card,
the card will not authorize.
iii. New error codes have been added to help identify why accounts
or credit cards are rejected whether used for tender or discount.
• Address Validation
We recommend performing an address validation on recipient addresses
using the FedEx validation API before submitting a local delivery order.
January 2017 Updated with new Branding
v
March 2018 Additional error codes have been added to support payment service and direct
mail.
Updated sample notification code to correct the URLs.
September 2020 Updated with new Branding
vi
Contents
Introduction ................................................................................................ 1
Office Order Service .................................................................................. 3
Upload Location......................................................................................... 7
Operation Details ...................................................................................... 7
Coding Details .......................................................................................... 7
Upload Location Request Elements .......................................................... 9
Upload Location Reply Elements ............................................................ 11
Upload Document File ............................................................................. 13
Operation Details .................................................................................... 13
Coding Details ........................................................................................ 13
Upload Document File Request Elements............................................... 15
Upload Document File Reply Elements ................................................... 16
Rate Office Order ..................................................................................... 17
Coding Details ........................................................................................ 18
Rate Order Request Elements ................................................................ 20
Rate Order Reply Elements .................................................................... 48
Create Office Order .................................................................................. 63
Coding Details ........................................................................................ 65
Create Order Request Elements ............................................................. 68
Create Order Reply Elements ................................................................. 99
Appendix ................................................................................................ 114
Examples ............................................................................................. 116
Upload Location Request................................................................... 119
Upload Location Reply ....................................................................... 120
Upload Document File ....................................................................... 121
Upload Multiple Document Files ........................................................ 122
vii
Rate Office Order Request ................................................................ 123
Rate Office Order Reply..................................................................... 127
Create Office Order Request ............................................................. 130
Create Office Order Reply ................................................................. 155
Email Confirmations ........................................................................... 180
Order Confirmation Sent to Order Contact ......................................... 182
Special Instructions Next Steps Sent to Order Contact....................... 183
Order Confirmation Sent to Recipient ................................................. 184
Order Completion Notice Sent to Order Contact................................. 185
Order Completion Notice Sent to Recipient ........................................ 186
Notification Messages and Codes ..................................................... 188
Severity Descriptions ......................................................................... 188
Notification Codes.............................................................................. 190
Media Categories and Descriptions .................................................. 216
Finishing Terms Reference ................................................................ 220
Finishing Thresholds .......................................................................... 224
viii
Introduction
FedEx Office Web Service for Print is a portfolio of transaction interfaces to digital printing
functionality hosted by FedEx Office. These transactions are used by customers to create
custom, highly efficient solutions that enable them to directly manage the creation,
configuration, and submission of FedEx Office digital print orders.
FedEx Web Services for Office and Print provides the following web service:
• Office Order Service
The Office Order Service enables the client application to directly manage the entire
order transaction workflow. The client is responsible for capturing the order intent and
content (printing/finishing instructions, contact/recipient, payment data, etc.) and
transmitting via the defined transaction set. The client application is also responsible for
receiving and responding to reply transactions returned by the web service.
Customers who choose to take advantage of FedEx Web Service for Office and Print will begin
by registering on the FedEx Developer Resource Center website in the FedEx Office Web
Services section located at fedex.com/us/developer/web-services/office. There you will find
technical documentation, sample software code, and support material designed to help you
build your custom solution. Once development is complete, FedEx will certify that your software
integration is ready for use.
This Transaction Guide is designed to facilitate the development of Office Order Service
implementations.
FedEx Confidential and Proprietary 1

This page intentionally left blank.

Office Order Service
Use the Office Order Service WSDL (Web Service Description Language) to request the
appropriate location to post a document for FedEx Office processing, request a rate quote for
your planned print order, and formally place a FedEx Office print order. Implementation detail
associated with these uses can be found within this document in the following sections: Upload
Location, Rate Office Order, and Create Office Order.
Operating Scenario
There are two scenarios for FedEx Office print orders:
1. Customer uses Office Order Service-enabled application to select a file that he/she
would like printed by FedEx Office. The client application will connect to FedEx to
request an upload location for the file. After the client is authenticated, FedEx replies
with the requested information and the client subsequently uploads the file.
Next, the client application is responsible for obtaining from the customer the desired
print and finishing options for the document. These documents are known as ad hoc
documents.
2. The customer has a corporate catalog and wishes to order from that catalog rather than
creating a customized document(s) for each order. FedEx Office establishes a catalog
to the customer’s specifications and provides the document identifiers to the developer
of the client application. These are known as catalog documents.
Each catalog document has static print and finishing options, as well as pre-determined
pricing. Static document content is supported, but a catalog document may be
configured to allow dynamic content as well.
If the customer is ordering a catalog document with dynamic content, the customer will
use the client application to select the content file. The client application will connect to
FedEx to request an upload location for the file. After the client is authenticated, FedEx
replies with the requested information and the client subsequently uploads the file.
(Please note that orders are not limited to one scenario or the other. A single order may include
both ad hoc documents and catalog documents.)
From that point forward, both scenarios follow the same steps. The client application is
responsible for obtaining from the customer all the information required to successfully place a
print order with FedEx Office, including customer contact information, payment information, and
delivery/pickup preferences. If delivery via direct mail is requested, the client application must
upload an additional file containing the list of addressees. Once the customer has provided the
client application with this information, the customer may request a rate quote for ad hoc
documents using the Rate Office Order service. Rate request is not required when using
Catalog-only workflow.
The client application will request the quote by passing a rate request to FedEx along with all
the information that the customer has provided. FedEx will reply with a detailed rate quote that
includes not only the cost of the order, but also information regarding where the order will be

processed if formally submitted and when it would be expected to be ready for pickup (if order
pickup is requested). The client application is responsible for displaying this information to the
customer. After reviewing the cost information and confirming that the order will be produced in
time to meet his/her needs, the customer uses the client application to formally place their order.
This time, the client application passes the customer’s order information to FedEx and requests
that the order be processed using the Create Office Order service. The client application
receives a confirmation reply from FedEx and the customer receives an email (if requested)
from FedEx Office a short while later confirming the receipt of their order and providing the
customer with a Global Tracking Number that they can use to monitor the production and
fulfillment progress associated with their order.

Features of Service
The following features are available to customers using client software that has successfully
implemented the Office Order Service:
• Connect securely to FedEx Office systems
• Order ad hoc documents:
- Upload file(s) of the following types:
Text, Rich Text, Adobe® PDF, Adobe PostScript®, Microsoft® Word, Microsoft
Excel® and Microsoft PowerPoint®
Note: Additional file types can be uploaded on an exception basis. In these cases,
special instructions must be provided by the customer to FedEx Office at order
submission detailing how the document should be printed.
- Request the following page sizes:

Letter (8.5” x 11“), Legal (8.5“ x 14“), and Tabloid (11“ x 17“)
Note: All pages within a printed document must be of the same size. Upon customer
request, document page size can be normalized. Large format and custom-sized
print requests can be processed on an exception basis. In these cases, special
instructions (included in the “Document Options Requested” section of the Create
Office Order Elelment definition) must be provided by the customer to FedEx
Office at order submission detailing how the document should be printed.
- Request desired print and finishing options

• Order pre-configured documents from a FedEx Office corporate catalog:
- Define print and finishing options in the catalog
- Either store document content in the catalog or configure to allow dynamic
content
- If ordering a catalog document with dynamic content, upload Adobe® PDF file(s)
to specify the document content
• Rate print orders
• Submit print orders using the following payment types:
- FedEx Account
- Major credit card
• Receive email order confirmation
• Pick up orders, have them shipped via FedEx Ground or FedEx Express, have them
delivered locally by FedEx Office, or have them sent via direct mail using the U.S. Postal
Service

Limitations
Implementations of the Office Order Service are subject to the following limitations:
• Online payment and rate quote not available for orders containing special instructions
• Online Preview / Proof functionality is not available
• US Domestic fulfillment and shipping only

Upload Location
Use this operation to obtain the file upload location from FedEx. Information identifying the
integrator, user, and client software is passed to FedEx. This information is validated by FedEx
and the appropriate reply is issued. Upon success, an Upload URL and an Upload Session ID
are returned to the client.
Operation Details
The getUploadLocation operation is used to pass an OfficeOrderUploadLocationRequest
message and subsequently receive an OfficeOrderUploadLocationReply message.
The following details apply:
• Web Authentication Detail, Client Detail, and Version information are required in request.
• Transaction Detail is optional in requests and echoed within reply.
• The file token with the Upload URL and Upload Session ID elements included in
OfficeOrderUploadLocationReply are required for later operations associated with
current document.
• See Upload Location Request Elements and Upload Location Reply Elements.
• See Notification Messages and Codes.
Coding Details
When uploading a file to FedEx Office:
• A call to getUploadLocation is required prior to uploading a file to FedEx Office.
• Client application is responsible for uploading the target file to the FedEx-designated
Upload Location. File upload functionality is not part of the Office Order Service.
File Upload Input: Protocol=HTTPS; Action=UploadUrl;
Enctype=“multipart/form- data”; Method=“POST”; content-
length (entity header required); Type=”file”;
Name=”file1”
File Upload Output: resultCode=SUCCESS or FAILED; fileAuthToken; errorMessage;
Format: Key1=value1(URL encoded)&key2=value2(URL encoded)
Character set: ASCII
Example: resultCode=SUCCESS&fileAuthToken=101010101010101010
• See Examples


Upload Location Request Elements
Element R/O/C Description
Office Order Upload Location Request

Web Authentication Detail R Descriptive data to be used in authentication of the sender's
identity and right to use FedEx Web Services.
Client Detail R Descriptive data used to identify the client application.
Transaction Detail O Client-provided descriptive data used by the client to identify a

transaction call.
Version R Descriptive data used to identify the web service that the client
application intends to call.
Web Authentication Detail

User Key R Unique identifier assigned to each customer as part of their
authentication credentials.
User Password R Second part of the authentication credential which has a direct
relationship with the credential key.
Client Detail
Client Product ID R Data assigned by FedEx used to identify product.
Client Product Version R Data assigned by FedEx used to identify product version.
Integrator ID R Data assigned by FedEx used to identify integrator.
Localization O Defines the desired translation for localizedMessage text in

the reply’s Notification object. (Note: Translation is currently
not supported, so any values in this object will be ignored.)
Transaction Detail
Customer Transaction ID O Client-provided descriptive data used by the client to identify a
transaction call.
Localization O Defines the desired translation for data payload values in the
reply. (Note: Translation is currently not supported, so any
values in this object will be ignored.)

Element R/O/C Description
Version
Service ID R Data used by FedEx to identify the system or sub-system
which will perform the requested operation.
Value:
• oord
Major R Data used by FedEx to identify the service business level.
Intermediate R Data used by FedEx to identify the service interface level.
Minor R Data used by FedEx to identify the service code level.

Upload Location Reply Elements
Element Description
Office Order Upload Location Reply

Highest Severity Identifies the highest severity encountered when executing the request.
Values (in order from high to low):
• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS
Notifications Descriptive data detailing the status of a submitted transaction.
Transaction Detail Client-provided descriptive data used by the client to identify a

transaction call. The Transaction Detail from the request is echoed
back to the caller in the corresponding reply.
Version Descriptive data used to identify the web service that executed the
request.
Upload URL Location provided to the client for uploading the file.
Upload Session ID Unique identifier associated with the file upload authorization.
Notifications
Severity Identifies the severity of the notification.
• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS
Source Identifies the FedEx system, sub-system, or component that generated

the notification. Combined with Code, it uniquely identifies this
message. (See Appendix.)
Code Identifies the code corresponding to this notification. Combined with

Source, it uniquely identifies this message. (See Appendix.)

Element Description
Message Contains text that explains this notification. (See Appendix.)
Note: See Notification Messages and Codes
Localized Message Translates the message to the localization requested. (Note:

Translation is currently not supported.)
Message Parameters Used internally by FedEx systems for message translation.
Message Parameters
ID Identifies the type of the data in the Value element.
Value Identifies the value that was used as the replacement parameter.
Transaction Detail
Customer Transaction ID Client-provided descriptive data used by the client to identify a
transaction call.
Version
Service ID Data used by FedEx to identify the system or sub-system that executed
the requested operation.
Value:
• oord
Major Data used by FedEx to identify the service business level.
Intermediate Data used by FedEx to identify the service interface level.
Minor Data used by FedEx to identify the service code level.

Upload Document File
Use this operation to upload a document file to FedEx Office Order Service.
Operation Details
The Upload Document File operation is used to upload a document file to the FedEx
designated file upload location (Upload URL) returned within the Upload Location Reply
message. The Upload Document File operation is not a native component of the Office Order
Service and must be coded within the client software by the developer.
• Protocol: HTTPS
• Method: POST
• File upload location (Upload URL) element is returned within the Upload Location Reply.
• File name must be passed as “file1”. Multiple file uploads are supported. In case of
multiple file upload the file names are “file1”, “file2”, file3”... “fileN”, where N is the number
of files that is used in the Office Order Request.
• Reply message will return the following: resultCode, fileAuthToken, errorMessage. In

case of multiple file uploads, the fileAuthToken contains a coma separated list of tokens.
The token sequence corresponds to the sequence of the files.
Coding Details
When uploading a file to FedEx Office:
• Via HTTPS, execute a “multipart/form-data”-encoded POST of the document file to the
FedEx designated file upload location (Upload URL) using “file1” as the file name.
• See Examples


Upload Document File Request Elements
Element Description
Protocol: HTTPS
Request
Action Value = “UploadUrl”
See Upload Location Reply
Enctype Value = “multipart/form-data”
Method Value = “POST”
content-length Content-length entity header required.
Type Value =”file”
Name Value =”file1”
File name must be “file1”.
In case of multiple file uploads the Name Value must be file1 for
the first file, file2 for the second file, and so on.

Upload Document File Reply Elements
Element Description
Upload Document File Character set: ASCII
Reply
Format:
Key1=value1(URL encoded)&key2=value2(URL encoded)
Example:
resultCode=SUCCESS&fileAuthToken=10101010101010101010
10101010101010101010
In case of multiple file upload, fileAuthToken is a list of comma

separated tokens.
resultCode Identifies the severity of the request.
• FAILED
• SUCCESS
fileAuthToken Server assigned token associated with file.
errorMessage Unpopulated. Client debugging.

Rate Office Order
Use this operation to request a rate quote for a planned FedEx Office print order. Information
identifying the integrator, user, and client software is passed to FedEx along with specific
information regarding the print order to be rated. The order information submitted as part of the
transaction includes customer contact information, payment and delivery/pickup preferences, as
well as print and finishing options.
If successful, FedEx will reply with a detailed rate quote that includes not only the cost of the
order, but also information regarding where the order will be processed if formally submitted and
when it would be expected to be ready for pickup (if order pickup is requested).
Operation Details
The rateOfficeOrder operation is used to pass a RateOfficeOrderRequest message and
subsequently receive a RateOfficeOrderReply message.
• Requests containing Custom Media Sizes or Special Instructions are not supported.
Note: Special Instructions will suppress online tender. A center will be in touch with order
contact to complete the order.
• Transaction Detail is optional in requests and echoed within reply.
• FedEx Account Number enabled for Print or major credit card is required.
• Requests may contain multiple line items. Each line item must contain either an ad hoc
document or a catalog document but may not contain both.
• Ad hoc documents and catalog documents may be combined in a single delivery group.
• Ad hoc documents and catalog documents may contain multiple sections.
• Data returned within RateOfficeOrderReply is calculated AS IF a print order had actually
been placed.
• Detailed estimated cost and discount data (where applicable) is returned in the
RateOfficeOrderReply. This data represents an estimate and may differ from the actual
invoiced amount.
• For pickup delivery groups, the location nearest to the address designated in the
RateOfficeOrderRequest message is assigned to produce the delivery group, unless a
different location is specified in the Center ID element or the customer configuration
profile stipulates a particular location.
• For local delivery delivery groups, the locations near the recipient address that can
complete the delivery by the specified date/window are identified, and the delivery group
is assigned to the closest one, unless a different location is specified in the Center ID
element or the customer configuration profile stipulates a particular location. If a Center
ID is specified, that location must be within a 30-mile radius of the recipient address in
most circumstances.

• For delivery groups shipped via FedEx, shipping charges may be optionally charged to
the customer’s FedEx account for shipping only to apply appropriate shipping discounts
and billed separately.
• For direct mail delivery groups, delivery of the print product(s) to multiple recipients will
be handled via the U.S. Postal Service.
• Due Date and Time returned within RateOfficeOrderReply are reflected in the
processing center’s local time.
• RateOfficeOrderRequests will fail if the selected document(s), print preferences,
finishing options, and/or media selections are incompatible with one or more of the other
parameters.
• See Rate Order Request Elements and Rate Order Reply Elements.
• See Media Categories and Descriptions; Finishing Terms Reference; Notification
Messages and Codes.
Coding Details
When requesting a rate quote for a print order:

• The file(s) associated with the RateOfficeOrderRequest must already be uploaded.
• Each section of a document (whether ad hoc or catalog) is associated with a file in its
entirety. Sections cannot be defined based on a subset of a file. Therefore, to define and
submit a print order containing a multi-section document, you must upload a separate
file for each section of the document that you wish to define.
• RateOfficeOrderRequests must include the File Token(s) and Upload Session ID(s)
associated with the previously uploaded file(s).
• For ad hoc documents, non-PDF customer files uploaded to FedEx Office for use in
association with the Office Order Service are automatically converted to PDF. Care
should be taken to ensure that the user is aware of the document layout and formatting
risks inherent in this conversion process. RateOfficeOrderRequests provide an
estimated rate quote based on the assumption that the customer’s intent is for the file to
be printed “as is” (following conversion to PDF, if required).
• If a file(s) is uploaded to customize the content of a catalog document, that file must
have a type of PDF.
• The Office Order Service does not currently support “Online Preview” or “Soft Proof”
functionality. Therefore, it is critical that any document uploaded to FedEx Office is
considered “print ready” by the customer prior to issuing a RateOfficeOrderRequest.
If the transaction includes an ad hoc document based on a non-PDF file, you must
explicitly decline the proof (Proof Type = “DECLINED”) for that document within your
RateOfficeOrderRequest or an error will be returned in response to the request.
• If the file associated with a section of your document has a presentation file type (e.g.,
Microsoft PowerPoint), presentation output details must be included within your request
transaction for the section.

• Where applicable, when prompting the user for print, finishing, payment, and fulfillment
options, ensure that clear descriptions and/or illustrations of the available options are
presented to the user.
• Where compatible, multiple finishing options may be associated with a single ad hoc
document. If incompatible options are selected, the RateOfficeOrderReply transaction
will reply with a message intended to help identify and correct the issue. Where
possible, use the information in this guide to proactively identify/constrain the entry of
incompatible parameters prior to transaction submission.
• Where applicable, display user-friendly error messages via the client application.
• See Rate Order Request Elements and Rate Order Reply Elements.
Messages and Codes.
• See Examples

Rate Order Request Elements
Required/
Element Optional/ Description
Conditional
Rate Office Order Request

User Detail C Descriptive data used to identify the user of a customer

configuration profile.
Note: This element is required if a value is populated for

Customer Configuration Profile Name.

transaction call.
Requested Office Order R Descriptive data needed from a web service client to rate a
FedEx Office order.

Client Detail

User Detail

Required/
Conditional
User ID R Specifies the FedEx Office user ID.
Password R Specifies the password corresponding to the FedEx Office

user ID.
Transaction Detail
transaction call.
Version
Value:
• oord
Requested Office Order

Customer Configuration O Specifies the name of the profile (i.e., site) that contains the
Profile Name customer's configuration settings (e.g., catalog).
Order Contact R Descriptive data identifying the individual placing the FedEx
Office order.

Required/
Conditional
Delivery Groups R Descriptive data establishing the discrete delivery methods for
the items in the order and identifying which items to convey
through each delivery method.
Note: Between one and two delivery groups are allowed per
order. The following combinations are supported:
• One with Delivery Type = PICKUP

• One with Delivery Type = SHIPMENT
• One with Delivery Type = LOCAL_DELIVERY
• One with Delivery Type = DIRECT_MAIL
• One with Delivery Type = PICKUP and another with
Delivery Type = DIRECT_MAIL
• One with Delivery Type = LOCAL_DELIVERY and
another with Delivery Type = DIRECT_MAIL
• One with Delivery Type = SHIPMENT and another
with Delivery Type = DIRECT_MAIL
Office Order Charges R Descriptive data for the means of payment for any charges
Payment assessed by FedEx Office.
Order Confirmation Email O Indicates whether or not email messages should be sent to
Requested the order contact and recipient confirming that the order was
received.
Values:
• TRUE
• FALSE
Order Completion Email O Indicates whether or not email messages should be sent to
Requested the order contact and recipient confirming that the order has
been completed.
Values:
• TRUE
• FALSE
Order Notification CC Email O Identifies other email addresses to include as CC recipients of

Addresses the order confirmation and completion emails.
Note: Total length of the system generated address line

comprised of the concatenation of all CC addresses
and delimiters must not exceed 1000 characters.

Required/
Conditional
Order Notification BCC Email O Identifies other email addresses to include as BCC recipients
Addresses of the order confirmation and completion emails.

comprised of the concatenation of all BCC addresses
Customer References O The reference information to associate with the order.
Note: Up to two customer references are supported. A

P_O_NUMBER reference is required when paying via
some FedEx accounts and is optional when paying
via credit card. If the request includes a Customer
Configuration Profile Name value, a
CUSTOMER_REFERENCE value is used to populate
a P.O. Number reference on the label of the FedEx
shipment used to deliver the order (if that option is
enabled in the profile). The credit card processor will
only accept alphanumeric characters in the P.O.
Number and customer reference fields. If special
characters are entered, they may be removed before
transaction is sent to credit card processor and the
integrator will receive a notification that the special
characters may be removed.
See Notification Messages and Codes
Discount Code O Identifies the FedEx account number to use in calculating print
discounts for the order.
Note: This element may only be populated when Office

Order Charges Payment Type is not ACCOUNT.
Promotion Code O Identifies the promotion code to use in calculating discounts

for the order.
Order Contact
Contact R Identifies the contact person’s contact information.
Address R Identifies the contact person’s physical address.
Order Contact > Contact

Person Name R Identifies the contact person’s name.
Company Name O Identifies the contact person's company name.
Phone Number R Identifies the contact person's phone number.

Required/
Conditional
Phone Extension O Identifies the contact person’s phone extension.
Fax Number O Identifies the contact person's fax machine phone number.
Email Address R Identifies the contact person's email address.
Order Contact > Contact > Person Name

First Name R Identifies the contact person's first name.
Last Name R Identifies the contact person's last name.
Order Contact > Address

Street Lines R Identifies the contact person’s street address.
Combination of number, street name, etc.
Note: At least one line is required for a valid physical

address; empty lines should not be included.
City R Identifies the contact person’s city.
State or Province Code R Identifies the contact person’s state.
Abbreviation for US state.
Postal Code R Identifies the contact person’s postal code.
Country Code R Identifies the contact person’s country.
Values:
• US
Delivery Group
Name O Identifies the delivery group. The Name from the request is
echoed back to the caller in the corresponding reply.
Description O Provides additional descriptive information about the delivery

group. The Description from the request is echoed back to the
caller in the corresponding reply.
Print Line Items R Descriptive data about the contents of this delivery group.
Multiple line items are allowed per delivery group.
Delivery Method R Descriptive data about the method of delivery.

Required/
Conditional
Print Line Items

Number of Copies R Identifies the number of copies of the document to be printed.
Catalog Document O Descriptive data about the catalog document to be printed.
Note: Each print line item must contain either a catalog

document or an ad hoc document but may not contain
both.
Document O Descriptive data about the ad hoc document to be printed.

both.
Catalog Document
Document Number C Specifies the unique identifier for the document within this
order. Each order's documents must be numbered
sequentially starting with 1.
Note: This element is required when the order is populated

with more than one document (either catalog or ad
hoc).
Type R Specifies the type of catalog that contains the document being
ordered.
Values:
• GLOBAL
• PERSONAL
Note: Orders for documents from personal catalogs are not

currently supported.
Folder Path R Specifies the catalog folder path where the document can be
found.
Document Name R Specifies the name of the document as stored in the catalog.
Customized Sections O The descriptive data about the individual sections of the
catalog document being customized, if any.

Required/
Conditional
Proof Type O Indicates whether/how the customer intends to review a

document proof prior to its production.
Values:
• DECLINED
Customized Sections
Section Number C Specifies the unique identifier for the section within this
document.
Note: This element is required when the catalog document

contains more than one section.
Upload Session ID R Specifies the unique identifier of the file upload authorization
that was used to upload the file. Combined with File Token, it
uniquely identifies the file to be used to create the section.
File Token R Specifies the identifier generated for the file by FedEx Office
when it was uploaded. Combined with Upload Session ID, it
Document
order. Each order’s documents must be numbered

hoc).
Name O Identifies the document. The Name from the request is echoed
Note: This element is required when the document is

populated with more than one section.
Finishing Options Requested O Descriptive data about the document finishing that is
requested for the printed document.
Sections R Descriptive data about the individual sections that make up

the document.
Document Options O Descriptive data about the options requested for the
Requested document.

Required/
Conditional
Proof Type C Indicates whether/how the customer intends to review a

Values:
• DECLINED
Note: When a RateOfficeOrderRequest is based on a non-

PDF file, the proof must be explicitly declined (Proof
Type = “DECLINED”).
Finishing Options Requested

Finishing Option Types O Identifies each document finishing option requested by the
customer.
Values:
• UNCOLLATED
• STAPLING
• DRILLING
• CUTTING
• FIRST_PAGE_IN_COLOR
• FIRST_PAGE_AS_COVER
• FRONT_COVER
• BACK_COVER
• FOLDING
• BINDING
• BINDER
• LAMINATION
• INSERTS
Stapling Detail C The descriptive data required for a document to be stapled.
Note: This element is required when STAPLING is present

in the Finishing Option Types collection.
Drilling Detail C The descriptive data required for a document to be drilled (i.e.,
hole-punched).
Note: This element is required when DRILLING is present in

the Finishing Option Types collection.
Cutting Detail C The descriptive data required for a document to be cut.
Note: This element is required when CUTTING is present in


Required/
Conditional
Front Cover Media Detail C The descriptive data required for a document's front cover.
Note: This element is required when FRONT_COVER is

present in the Finishing Option Types collection.
Currently, this element is only accepted when
BINDING is also present in the Finishing Option
Types collection.
Back Cover Media Detail C The descriptive data required for a document's back cover.
Note: This element is required when BACK_COVER is

Types collection.
Folding Detail C The descriptive data required for a document to be folded.
Note: This element is required when FOLDING is present in

Binding Detail C The descriptive data required for a document to be bound.
Note: This element is required when BINDING is present in

Binder Detail C The descriptive data required for a document to be inserted in

a binder.
Note: This element is required when BINDER is present in

Lamination Detail O The descriptive data related to document lamination.
Note: This element is only accepted when LAMINATION is

Insert Detail O Specifies details derived from one or more requested

document inserts.
Note: This element is only accepted when INSERT is present

Tab Detail O Specifies the detail of a document tab.
Note: This element is a subset of the inserts detail when tabs

are requested. Only accepted when INSERT DETAIL is used.
Stapling Detail

Required/
Conditional
Stapling Type R Identifies the type of stapling.
Values:
• LEFT_UPPER
• TWO_ON_LONG_SIDE
Drilling Detail
Drilling Type R Identifies the type of drilling.
Values:
• THREE_HOLE_SIDE
• TWO_HOLE_TOP
Cutting Detail
Cutting Type R Identifies the type of cutting.
Values:
• HALF_CUT_PORTRAIT
• HALF_CUT_LANDSCAPE
• THIRD_CUT_PORTRAIT
• THIRD_CUT_LANDSCAPE
• QUARTER_CUT_PORTRAIT
• QUARTER_CUT_LANDSCAPE
Front Cover Media Detail

Media Category R Indicates the media category used for Front Cover. Combined
with Media Description, it uniquely identifies the media.
Values:
• CARDSTOCK
• COVER
• RESUME_CARDSTOCK
Note: See Media Categories and Descriptions

Required/
Conditional
Media Description R Indicates the media description used for Front Cover.
Combined with Media Category, it uniquely identifies the
media.
Values for CARDSTOCK:
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• ULTRA_BRIGHT_WHITE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• BLACK_VINYL_COVER
• BLUE_VINYL_COVER
• FROSTED_COVER
• CLEAR_COVER
Values for RESUME_CARDSTOCK:
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Back Cover Media Detail

Media Category R Indicates the media category used for Back Cover. Combined
Values:
• CARDSTOCK
• COVER

Required/
Conditional
Media Description R Indicates the media description used for Back Cover.
media.
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• FROSTED_COVER
• CLEAR_COVER
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Folding Detail
Text Position C Identifies whether the text on the page should be on the inside
or outside of the document after it is folded. Only applies to
single-folding and single-page double-folding.
Values:
• IN
• OUT

Required/
Conditional
Folding Type R Identifies the type of folding.
Values:
• SINGLE
• DOUBLE
• Z
Binding Detail
Binding Type R Identifies the type of binding.
Values:
• COIL
• COMB
Binder Detail
Binder Color R Identifies the color of the binder.
Values:
• BLACK
• WHITE
Binder Size R Identifies the size of the binder.
Values:
• ONE_HALF_INCH
• ONE_INCH
• ONE_AND_ONE_HALF_INCH
• TWO_INCH
• THREE_INCH
First Page in Cover O Indicates whether an extra copy of the first page of the
document should be printed and inserted in the clear plastic
cover.
Values:
• TRUE
• FALSE

Required/
Conditional
Lamination Detail
Border Type O Specifies the size of the lamination border around the edge of
the document (if a border is desired).
Values:
• ONE_QUARTER_INCH
Insert Details
Sequence Number R A unique identifier for this insert within the document.
Page Number R Specifies the page numbers where Inserts must be added
(enter page number of document where the insert should
follow. If insert is to become page 5 of the document, then it
should be inserted after page 4 of the document; enter value
of 4)
When a tab is inserted after an odd numbered page for

double-sided, a blank page will be inserted for tab to be
placed properly.
Media Category O Indicates the media category used for Inserts. Combined with
Media Description, it uniquely identifies the media.
Values:
• CARDSTOCK
• COVER
• STANDARD

Required/
Conditional
Media Description R Indicates the media description used for Inserts. Combined
with Media Category, it uniquely identifies the media.
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• FROSTED_COVER
• CLEAR_COVER
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Tab Detail
Label Lines O One or more text lines that may appear on the tab of a
document insert.
Line Number R Specifies the line number of the Label on the Tab
Values:
• 1
• 2

Required/
Conditional
Content O Specifies the text content appearing on the Label Line. The
maximum character length per Label line is 30.
Font O The font details used to render the text on the tab label lines.
Name R Specifies the font name
Values:
• Arial
• Arial Narrow
• Times New Roman
Size R Specifies the size of the font
Values:
• 8
• 10
• 12
• 14
Styles R Specifies the font style
Values:
• Bold
• Italics
• Underline
Orientation O Specifies the orientation of the Label on Tab
Values:
• Portrait (Text In) – text on the tab will be facing inward

• Landscape (Text Out) – text on the tab will be facing
outward
Section
document. Each document’s sections must be numbered
Note: This element is required if the document is populated

with more than one section.

Required/
Conditional
Print Type R Identifies the print type of the document.
Values:
• BLACK_AND_WHITE
• COLOR
Number of Sides R Identifies whether the document is to be printed on one side or

both sides of the media.
Values:
• SINGLE
• DOUBLE
Section Media Detail R The descriptive data that identifies the media on which the
section is to be printed.
Section Options Requested C The descriptive data about the options requested for the
section.
Note: This element is required if the file associated with the

section has a presentation file type (e.g., Microsoft
PowerPoint).
Section Media Detail

Required/
Conditional
Media Category R Indicates the media category used for the section. Combined
Values:
• CARBONLESS_MULTI_PART
• CARDSTOCK
• COVER_GLOSS
• EXECUTIVE
• PASTEL_BRIGHTS
• RESUME
• STANDARD
• STANDARD_LASER
• TEXT_GLOSS
• TRANSPARENCY
Media Description R Indicates the media description used for the section.
media.
Values:
• ANTIQUE • RECYCLED_100_PERCENT
• ANTIQUE_GRAY • RECYCLED_30_PERCENT
• BRIGHT_BLUE • RED
• CANARY • SALMON
• FOUR_PART • SANDSTONE
• GLOSS_COVER_10_PT • SEA_SPRAY
• GLOSS_TEXT • SIGNATURE_WHITE
• INDEX_110_LB • SOFT_PINK
• IVORY • STANDARD_WHITE
• LASER_PAPER • SUN_YELLOW
• NATURAL • TAN
• ORCHID • THREE_PART
• PASTEL_BLUE • TRANSPARENCY
• PASTEL_GREEN • TWO_PART
• PURE_WHITE • ULTRA_BRIGHT_WHITE
• ULTRA_FUCHSIA
• ULTRA_LEMON
• ULTRA_LIME
• ULTRA_ORANGE
• WILLOW

Required/
Conditional
Media Size O Identifies the media's size.
Values:
• LETTER
• LEGAL
• TABLOID
Note: This element does not apply to cover media. This is

only needed when the desired media size differs from
the media size defined in the file that was uploaded.
Section Options Requested

Section Option Types C Identifies each section option requested by the customer.
Values:
• PRESENTATION_OUTPUT
Note: PRESENTATION_OUTPUT must be present in the

Section Option Types collection if the section’s
corresponding file has a presentation file type (e.g.,
Microsoft PowerPoint).
Presentation Output Detail C Descriptive data required for a section based on a

presentation file.
Note: This element is required when

PRESENTATION_OUTPUT is present the Section
Option Types collection.
Presentation Output Detail

Output Type R Indicates the type of presentation output.
Values:
• HANDOUTS
• NOTES
• SLIDES
Output Options O Identifies the presentation options requested by the customer.
Values:
• FRAME_SLIDES

Required/
Conditional
Handout Detail C Descriptive data required for handouts to be produced for a

presentation file.
Note: This element is required when HANDOUTS is

specified as the Output Type.
Handout Detail
Layout R Indicates the number of slides to be printed per page.
Values:
• ONE_SLIDE_PER_PAGE
• TWO_SLIDES_PER_PAGE
• THREE_SLIDES_PER_PAGE
• FOUR_SLIDES_PER_PAGE
• SIX_SLIDES_PER_PAGE
• NINE_SLIDES_PER_PAGE
Slide Order R Indicates whether slides should be ordered vertically before

wrapping to a new column or horizontally before wrapping to a
new row.
Values:
• HORIZONTAL
• VERTICAL
Note: When Layout specifies fewer than four slides per

page, both options result in the same output.
Delivery Method
Delivery Type R Identifies the type of delivery for the delivery group.
Values:
• DIRECT_MAIL
• LOCAL_DELIVERY
• PICKUP
• SHIPMENT
Note: DIRECT_MAIL may only be requested if a value is

populated for Customer Configuration Profile Name
and that profile has been authorized for direct mail.

Required/
Conditional
Order Recipient C Descriptive data about the recipient of the documents in the
delivery group.
Note: This element is required if the Delivery Type is

LOCAL_DELIVERY, PICKUP, or SHIPMENT. For
PICKUP delivery groups, the recipient is the person
picking up the delivery group. For
LOCAL_DELIVERY and SHIPMENT delivery groups,
the recipient is the person who will receive the
delivery group. If Delivery Type is DIRECT_MAIL,
populating this element will result in an error.
Center ID O Specifies the unique identifier of the FedEx Office location

where the recipient wishes to receive the delivery group (for a
pickup delivery group) or where the order contact wishes to
have it produced (for a local delivery, shipment, or direct mail
delivery group).
Order Direct Mail Detail C Descriptive data about the direct mail recipient list.
Note: This element is required when DIRECT_MAIL is

specified as the Delivery Type.
Order Local Delivery Detail C Descriptive data about the rqeuested local delivery.
Note: This element is required when LOCAL_DELIVERY is

Order Pickup Detail C Descriptive data about the criteria to use in selecting a FedEx
Office location for delivery group pickup.
Note: This element is required when PICKUP is specified as

the Delivery Type and no Center ID is specified.
Order Shipment Detail C Descriptive data about the FedEx billing and service details for
the delivery group shipment.
Note: This element is required when SHIPMENT is

Order Recipient
Contact R Identifies the recipient’s contact information.

Required/
Conditional
Address C Identifies the recipient’s physical address.
Note: Required if Delivery Type is LOCAL_DELIVERY or

SHIPMENT.
If Delivery Type is PICKUP, populating this element

will result in an error.
Order Recipient > Contact

Person Name R Identifies the recipient’s name.
Company Name O Identifies the recipient’s company name.
Phone Number R Identifies the recipient’s phone number.
Phone Extension O Identifies the recipient’s phone extension.
Email Address C Identifies the recipient’s email address.

PICKUP.
Order Recipient > Contact > Person Name

First Name R Identifies the recipient's first name.
Last Name R Identifies the recipient’s last name.
Order Recipient > Address

Street Lines R Identifies the recipient’s street address.
Combination of number, street name, etc. At least one line is

required for a valid physical address; empty lines should not
be included.
City R Identifies the recipient’s city.
State or Province Code R Identifies the recipient’s state.
Values: Any US state abbreviation
Postal Code R Identifies the recipient’s postal code.

Required/
Conditional
Country Code R Identifies the recipient’s country.
Values:
• US
Residential O Indicates whether this address is residential (as opposed to

commercial).
Values:
• TRUE
• FALSE
Order Direct Mail Detail

that was used to upload the recipient address file. Combined
with File Token, it uniquely identifies the file.
uniquely identifies the recipient address file.
Address Count R Specifies the number of lines in the file, where each line
corresponds to a single address. This field exists for
verification purposes.
Order Local Delivery Detail

Requested Delivery Date R Identifies the local date when the delivery group recipient
wishes to receive the delivery group.
Requested Delivery Window R Identifies the local time window when the delivery group
recipient wishes to receive the delivery group.
Values:
• MORNING
• AFTERNOON
Delivery Instructions O Contains any detailed instructions or requests that the

customer wishes to specify.

Required/
Conditional
Order Pickup Detail

Location Search Criteria O Descriptive data about the address to use in selecting a
FedEx Office location.
Note: This element is required when no Center ID is

specified.
Due Date and Time O Identifies the local date and time when the delivery group
recipient wishes to pick up the delivery group.
Format: YYYY-MM-DDTHH
Example: 2013-06-25T18
Location Search Criteria

Street Lines O Identifies street address near which recipient wishes to pick up
the delivery group.

be included.
City C Identifies city near which recipient wishes to pick up the

delivery group.
Note: Required if Postal Code not populated.
State or Province Code C Identifies state near which recipient wishes to pick up the
delivery group.
Postal Code C Identifies postal code near which recipient wishes to pick up
the delivery group.
Note: Required if both City and State or Province Code are

not populated.
Country Code R Identifies the country where the recipient wishes to pick up the
delivery group.
Values:
• US

Required/
Conditional
Order Shipment Detail

Shipping Charges Payment O Descriptive data indicating the method and means of payment
to FedEx for providing shipping services, if different from the
payment method for the FedEx Office printing charges.
Service Type R Identifies the FedEx service to use in shipping the package.
Values:
• FIRST_OVERNIGHT
• PRIORITY_OVERNIGHT
• STANDARD_OVERNIGHT
• FEDEX_2_DAY
• FEDEX_EXPRESS_SAVER
• FEDEX_GROUND
• GROUND_HOME_DELIVERY
Shipping Charges Payment

Payment Type R Identifies the method of payment for shipping services.
Values:
• RECIPIENT
• THIRD_PARTY
Payor R The descriptive data identifying the party responsible for

payment of shipping.
Shipping Charges Payment > Payor

Responsible Party R The descriptive data about the payor's FedEx shipping
account. This element is required when the shipping charges
party is specified separately from printing charges party.
Shipping Charges Payment > Payor > Responsible Party

Account Number R Identifies the FedEx account number assigned to the party.
Field requirements up to 24 characters

Required/
Conditional
Office Order Charges Payment

Payment Type R The descriptive data for the means of payment for any
charges assessed by FedEx Office.
Values:
• ACCOUNT
• CREDIT_CARD
Payor C The descriptive data identifying the party responsible for

payment of any charges assessed by FedEx Office.
Note: This element is required if Payment Type is

ACCOUNT.
Credit Card C The descriptive data required for payment via credit card.

CREDIT_CARD.
CVV O The descriptive data required for CVV (Card Verification

Value) associated to the card used for payment.
Note: While this field is optional, it is recommended to capture

CVV to decrease fraud risk.
Office Order Charges Payment > Payor

Associated Accounts R The descriptive data about a separate FedEx account number
assigned to the payor that is associated with a specific FedEx
operating company.
Office Order Charges Payment > Payor > Associated Accounts

Type R Identifies the FedEx operating company that issued the
account.
Values:
• FEDEX_OFFICE
Account Number R Identifies the FedEx account number assigned to the payor.
Office Order Charges Payment > Credit Card

Number R Identifies the credit card’s number.

Required/
Conditional
Credit Card Type R Identifies the credit card’s type.
Values:
• AMEX
• DINERS
• DISCOVER
• MASTERCARD
• VISA
Expiration Date R Identifies the credit card’s expiration date.
Note: The date must be stated in one of the following

formats: YYMM, YYYYMM, YYYYMMDD.
Credit Card Holder R Descriptive data about the credit card’s holder.
Office Order Charges Payment > Credit Card > Credit Card Holder
Contact R Identifies the credit card holder’s contact information.
Address R Identifies the credit card holder’s physical address.
Office Order Charges Payment > Credit Card > Credit Card Holder > Contact
Person Name R Identifies the credit card holder’s name.
Company Name O Identifies the credit card holder’s company name.
Phone Number R Identifies the credit card holder’s phone number.
Office Order Charges Payment > Credit Card > Credit Card Holder > Contact > Person Name
First Name R Identifies the credit card holder’s first name.
Last Name R Identifies the credit card holder’s last name.
Office Order Charges Payment > Credit Card > Credit Card Holder > Address
Street Lines R Identifies the credit card holder’s street address.

City R Identifies the credit card holder’s city.

Required/
Conditional
State or Province Code R Identifies the credit card holder’s state.
Values: Abbreviation for US state.
Postal Code R Identifies the credit card holder’s postal code.
Note: (Validated by the payment processor.)
Country Code R Identifies the credit card holder’s country.
Values:
• US
Customer References
Type R Identifies the type of customer reference.
Values:
• CUSTOMER_REFERENCE
• P_O_NUMBER
Value R Identifies the customer reference value.
Note: The credit card processor will only accept alphanumeric

characters in the P.O. Number and customer reference fields.
If special characters are entered, they may be removed before
transaction is sent to credit card processor and the integrator
will receive a notification that the special characters may be
removed.

Rate Order Reply Elements
Element Description
Rate Office Order Reply

• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS

request.
Rated Office Order The descriptive data generated by FedEx Office for the FedEx Office
order that was submitted for rating.
Notifications
• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS

message.

Source, it uniquely identifies this message.

Element Description
Message Contains text that explains this notification.

Message Parameters
Transaction Detail
transaction call.
Version
Value:
• oord
Rated Office Order

Rated Delivery Group Pricing and delivery method details generated by FedEx Office for each
Details delivery group in the order that was rated.
Pricing The aggregate pricing information for the entire FedEx Office order.
Rated Delivery Group Details

Name Identifies the delivery group. The Name from the request is echoed
Description Provides additional descriptive information about the delivery group.

The Description from the request is echoed back to the caller in the
corresponding reply.

Element Description
Rated Catalog Document Document-level details generated by FedEx Office for each catalog
Details document in the delivery group that was rated.
Rated Document Details Document-level details generated by FedEx Office for each ad hoc
document in the delivery group that was rated.
Pricing The aggregate pricing information for the entire delivery group.
Rated Order Local Delivery The descriptive data specifying which FedEx Office location would be
Detail delivering the delivery group, had the delivery group been created and
not just rated. This element only applies when LOCAL_DELIVERY is
Rated Order Pickup Detail The descriptive data specifying where and when the delivery group
would have been available for pickup, had the delivery group been
created and not just rated. This element only applies when PICKUP is
Rated Catalog Document Details

Document Number Specifies the unique identifier for the document within this order. The
document number from the request is echoed back to the caller in the
corresponding reply. If no value was supplied, 1 is returned.
Type Specifies the type of catalog that contains the document. The Type
from the request is echoed back to the caller in the corresponding reply.
Folder Path Specifies the catalog folder path where the document can be found.
The Folder Path from the request is echoed back to the caller in the
Document Name Specifies the name of the document as stored in the catalog. The
Document Name from the request is echoed back to the caller in the
Pricing The descriptive data about the pricing for the document.
Rated Catalog Document Details > Pricing

Total Cost Identifies the total amount of all elements in the collection of Costs.
Total Discount Identifies the total amount of all elements in the collection of Discounts.
Net Cost The Total Cost value less the Total Discount value.
Costs A list capturing each cost amount and its respective type.
Discounts A list capturing each discount amount and its respective type.

Element Description
Rated Catalog Document Details > Pricing > Total Cost

Currency Identifies the currency of the monetary amount.
Values:
• USD
Amount Identifies the monetary amount.
Rated Catalog Document Details > Pricing > Total Discount

Values:
• USD
Rated Catalog Document Details > Pricing > Net Cost

Values:
• USD
Rated Catalog Document Details > Pricing > Costs

Type Identifies the type of cost associated with the rated document.
Values:
• BASE_COST
• OTHER
Amount Identifies the cost amount.
Rated Catalog Document Details > Pricing > Costs > Amount
Values:
• USD

Element Description
Rated Catalog Document Details > Pricing > Discounts

Type Identifies the type of discount associated with the rated document.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Amount Identifies the discount amount.
Rated Catalog Document Details > Pricing > Discounts > Amount
Values:
• USD
Rated Document Details

Name Identifies the document. The Name from the request is echoed back to
the caller in the corresponding reply. If there is no Name value in the
request, this will be the document's filename.
Rated Document Details > Pricing


Element Description
Rated Document Details > Pricing > Total Cost

Values:
• USD
Rated Document Details > Pricing > Total Discount

Values:
• USD
Rated Document Details > Pricing > Net Cost

Values:
• USD
Rated Document Details > Pricing > Costs

Type Identifies the type of cost associated with the rated document.
Values:
• BASE_COST
• OTHER
Rated Document Details > Pricing > Costs > Amount

Values:
• USD

Element Description
Rated Document Details > Pricing > Discounts

Type Identifies the type of discount associated with the rated document.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Rated Document Details > Pricing > Discounts > Amount

Values:
• USD
Rated Delivery Group Details > Pricing

Tax The total tax amount assessed on the Net Cost value.
Net Price The Net Cost value plus the Tax value.
Costs A list capturing each cost amount and its respective type. At the
delivery group level, the list includes both group-level costs as well as
all costs associated with the delivery group’s documents.
Discounts A list capturing each discount amount and its respective type. At the
delivery group level, the list includes both group-level discounts as well
as all discounts associated with the delivery group’s documents.
Rated Delivery Group Details > Pricing > Total Cost

Values:
• USD

Element Description
Rated Delivery Group Details > Pricing > Total Discount

Values:
• USD
Rated Delivery Group Details > Pricing > Net Cost

Values:
• USD
Rated Delivery Group Details > Pricing > Tax

Values:
• USD
Rated Delivery Group Details > Pricing > Net Price

Values:
• USD

Element Description
Rated Delivery Group Details > Pricing > Costs

Type Identifies the type of cost associated with the rated delivery group.
Values:
• BASE_COST
• FILE_RENDERING
• HANDLING
• OTHER
• POSTAGE
• SHIPPING
Rated Delivery Group Details > Pricing > Costs > Amount
Values:
• USD
Rated Delivery Group Details > Pricing > Discounts

Type Identifies the type of discount associated with the rated delivery group.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Rated Delivery Group Details > Pricing > Discounts > Amount
Values:
• USD

Element Description
Rated Order Local Delivery Detail

FedEx Office Center Detail Identifies the FedEx Office location that would be delivering the delivery
group, had it been created instead of just rated.
Rated Order Local Delivery Detail > FedEx Office Center Detail
Name Identifies the name of the FedEx Office location that would be delivering
the delivery group, had it been created instead of just rated.
ID Specifies the unique identifier that FedEx Office uses to designate the
location that would be delivering the delivery group, had it been created
instead of just rated.
Address Identifies the address of the FedEx Office location that would be
delivering the delivery group, had it been created instead of just rated.
Phone Number Identifies the phone number of the FedEx Office location that would be
Email Address Identifies the email address of the FedEx Office location that would be
Rated Order Local Delivery Detail > Address

Street Lines Identifies the address of the FedEx Office location that would be
City Identifies the city of the FedEx Office location that would be delivering
State or Province Code Identifies the state of the FedEx Office location that would be delivering
Postal Code Identifies the postal code of the FedEx Office location that would be
Country Code Identifies the country of the FedEx Office location that would be
Values:
• US
Rated Order Pickup Detail

Center Name Identifies the name of the FedEx Office location where the delivery
group would have been available for pickup, had it been created

Element Description
Center ID Specifies the unique identifier that FedEx Office uses to designate the
location where the delivery group would have been available for pickup,
had it been created instead of just rated.
Center Address Identifies the address of the FedEx Office location where the delivery
Center Phone Number Identifies the phone number of the FedEx Office location where the
delivery group would have been available for pickup, had it been
created instead of just rated.
Center Email Address Identifies the email address of the FedEx Office location where the
delivery group would have been available for pickup, had it been
created instead of just rated.
Due Date and Time Indicates the local date/time when the delivery group would have been
available for pickup, had it been created instead of just rated.
Rated Order Pickup Detail > Center Address

Street Lines Identifies the address of the FedEx Office location where the delivery
instead of just rated. Combination of number, street name, etc.
City Identifies the name of the city where the delivery group would have
been available for pickup, had it been created instead of just rated.
State or Province Code Identifies the name of the state where the delivery group would have
Postal Code Identifies the postal code where the delivery group would have been
available for pickup, had it been created instead of just rated.
Country Code Identifies the name of the country where the delivery group would have
Values:
• US
Rated Office Order > Pricing


Element Description
Costs A list capturing each cost amount and its respective type. At the order
level, the list includes both order-level costs as well as all costs
associated with the order’s delivery groups and documents.
order level, the list includes both order-level discounts as well as all
discounts associated with the order’s delivery groups and documents.
Rated Office Order > Pricing > Total Cost

Values:
• USD
Rated Office Order > Pricing > Total Discount

Values:
• USD
Rated Office Order > Pricing > Net Cost

Values:
• USD
Rated Office Order > Pricing > Tax

Values:
• USD

Element Description
Rated Office Order > Pricing > Net Price

Values:
• USD
Rated Office Order > Pricing > Costs

Type Identifies the type of cost associated with the rated order.
Values:
• BASE_COST
• FILE_RENDERING
• HANDLING
• OTHER
• POSTAGE
• SHIPPING
Rated Office Order > Pricing > Costs > Amount

Values:
• USD
Rated Office Order > Pricing > Discounts

Type Identifies the type of discount associated with the rated order.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER

Element Description
Rated Office Order > Pricing > Discounts > Amount

Values:
• USD


Create Office Order
Use this operation to formally place a FedEx Office ® print order. Information identifying the
integrator, user, and client software is passed to FedEx along with specific information regarding
the print order to be fulfilled. The order information submitted as part of the transaction includes
customer contact information, payment, and delivery/pickup preferences, as well as details
about the document(s) to be printed. If successful, FedEx Office will accept the order and begin
fulfillment. Meanwhile, a reply transaction confirming receipt of the order and detailing
associated cost, fulfillment, and support information will be returned to the client application.
Operation Details
The createOfficeOrder operation is used to pass a CreateOfficeOrderRequest message and
subsequently receive a CreateOfficeOrderReply message.

• Billing information can be submitted within CreateOfficeOrderRequests containing the
SPECIAL_INSTRUCTIONS Document Option, but payment cannot be finalized online.
Additionally, pricing information will not be available in the associated reply transaction.
When an order containing special instructions is submitted, the customer must call the
FedEx Office location and confirm the order before it can be processed. The Office
Order Service will automatically send the customer an email reminding them of this
requirement after each special instructions order they submit.
• Transaction Detail is optional in requests and echoed within the reply.
• FedEx Account enabled for Print or major credit card is required (unless special
instructions are specified).
• Orders may contain multiple line items. Each line item must contain either an ad hoc
document or a catalog document but may not contain both.
• Ad hoc documents and catalog documents may be combined in a single delivery group.
• Ad hoc documents and catalog documents may contain multiple sections.
• Orders submitted via CreateOfficeOrderRequest transactions are live and processing
typically begins immediately. To attempt to cancel an order, the customer must call the
processing location as soon as possible. Charges may be incurred for orders whose
production has already initiated.
• Detailed cost and discount data (where applicable) is returned in the
CreateOfficeOrderReply.
• For pickup delivery groups, the location nearest to the address designated in the
CreateOfficeOrderRequest message is assigned to produce the delivery group, unless a
different location is specified in the Center ID element or the customer configuration
profile stipulates a particular location.

• For local delivery delivery groups, the locations near the recipient address that can
complete the delivery by the specified date/window are identified, and the delivery group
is assigned to the closest one, unless a different location is specified in the Center ID
element or the customer configuration profile stipulates a particular location. If a Center
ID is specified, that location must be within a 30-mile radius of the recipient address in
most circumstances.
• For delivery groups shipped via FedEx, shipping charges may be optionally charged to
the customer’s FedEx account to apply appropriate shipping discounts and billed
separately.
• For direct mail delivery groups, delivery of the printed product(s) to multiple recipients
will be handled via the U.S. Postal Service:
o Each recipient in the order shall receive the same document(s) within an
envelope.
o The size of the envelope shall vary according to the size of the printed
document(s).
o The recipient address shall be printed on the envelope but may not be
incorporated into the content of the printed document(s).
o The order contact details shall be printed as the return address on the envelope.
o The total weight of the printed document(s) to be sent to each recipient may not
exceed 13 ounces.
• Due Date and Time returned within CreateOfficeOrderReply are reflected in the
processing center’s local time.
• CreateOfficeOrderRequests will fail if the selected document(s), print preferences,
finishing options, and/or media selections are incompatible with one or more of the other
parameters.
• Order status may be tracked using the Track Web Service. Detailed information about
that web service is available in the FedEx Web Services for Shipping section in the
Developer Resource Center on fedex.com. Note: Tracking results for FedEx Office
orders include identification of the delivery method. For local delivery delivery groups,
the Track Web Service considers local delivery a form of shipment and thus returns
SHIPMENT as the delivery method.
• See Create Order Request Elements and Create Order Reply Elements.
Messages and Codes.

Coding Details
When creating a print order:
• The file(s) associated with the CreateOfficeOrderRequest must already be uploaded.

• Each section of a document (whether ad hoc or catalog) is associated with a file in its
entirety. Sections cannot be defined based on a subset of a file. Therefore, to define and
submit a print order containing a multi-section document, you must upload a separate
file for each section of the document that you wish to define.
• CreateOfficeOrderRequests must include the File Token(s) and Upload Session ID(s)
associated with the previously uploaded file(s).
• For ad hoc documents, non-PDF customer files uploaded to FedEx Office for use in
association with the Office Order Service are automatically converted to PDF. Care
should be taken to ensure that the user is aware of the document layout and formatting
risks inherent in this conversion process. CreateOfficeOrderRequests are fulfilled based
on the assumption that the customer’s intent is for the file to be printed “as is” (following
conversion to PDF, if required).
• If a file(s) is uploaded to customize the content of a catalog document, that file must
have a type of PDF.
• The Office Order Service does not currently support “Online Preview” or “Soft Proof”
functionality. Therefore, it is critical that any document uploaded to FedEx Office is
considered “print ready” by the customer prior to issuing a CreateOfficeOrderRequest.
If the transaction includes an ad hoc document based on a non-PDF file or specifies a
media size that differs from the dimensions native to the document, you must explicitly
decline the proof (Proof Type = “DECLINED”) for that document within your
CreateOfficeOrderRequest or an error will be returned in response to the request.
• If the file associated with a section of your document has a presentation file type (e.g.,
Microsoft PowerPoint), presentation output details must be included within your request
transaction for the section.
• The Office Order Service does not contain “Order Cancel” functionality. As such, client
applications should confirm the customer’s desire to submit an order prior to processing
the transaction.
• Where applicable, when prompting the user for print, finishing, payment, and fulfillment
options, ensure that clear descriptions and/or illustrations of the available options are
presented to the user.
• Where compatible, multiple finishing options may be associated with a single ad hoc
document. If incompatible options are selected, the CreateOfficeOrderReply transaction
will reply with a message intended to help identify and correct the issue. Where
possible, use the information in this guide to proactively identify/constrain the entry of
incompatible parameters prior to transaction submission.
• Where applicable, display user-friendly error messages via the client application.
• See Create Order Request Elements and Create Order Reply Elements.

Messages and Codes.
• See Examples


Create Order Request Elements
Required/
Conditional
Create Office Order Request

User Detail C Descriptive data used to identify the user of a customer

Note: This element is required if a value is populated for

Customer Configuration Profile Name.

transaction call.
Requested Office Order R Descriptive data needed from a web service client to create a
FedEx Office order.

Client Detail

User Detail

Required/
Conditional
User ID R Specifies the FedEx Office user ID.
Password R Specifies the password corresponding to the FedEx Office

user ID.
Transaction Detail
transaction call.
Version
Value:
• oord
Requested Office Order

Customer Configuration O Specifies the name of the profile (i.e., site) that contains the
Profile Name customer's configuration settings (e.g., catalog).
Order Contact R Descriptive data identifying the individual placing the FedEx
Office order.

Required/
Conditional
Delivery Groups R Descriptive data establishing the discrete delivery methods for
the items in the order and identifying which items to convey
through each delivery method.
Note: Between one and two delivery groups are allowed per
order. The following combinations are supported:
• One with Delivery Type = PICKUP

• One with Delivery Type = SHIPMENT
• One with Delivery Type = DIRECT_MAIL
• One with Delivery Type = PICKUP and another
with Delivery Type = DIRECT_MAIL
and another with Delivery Type =
DIRECT_MAIL
• One with Delivery Type = SHIPMENT and
another with Delivery Type = DIRECT_MAIL
Office Order Charges C Descriptive data for the means of payment for any charges
Payment assessed by FedEx Office.
Note: This element is not required if

SPECIAL_INSTRUCTIONS is present in the
Document Option Types collection for any Document
in the order.
Order Confirmation Email C Indicates whether or not email messages should be sent to
Requested the order contact and recipient confirming that the order was
received.
Values:
• TRUE
• FALSE
Note: This element must equal TRUE if

Document Option Types collection for any Document
in the order.
Order Completion Email O Indicates whether or not email messages should be sent to
Requested the order contact and recipient confirming that the order has
been completed.
Values:
• TRUE
• FALSE

Required/
Conditional
Order Notification CC Email O Identifies other email addresses to include as CC recipients of

Addresses the order confirmation and completion emails.

comprised of the concatenation of all CC addresses
Order Notification BCC Email O Identifies other email addresses to include as BCC recipients
Addresses of the order confirmation and completion emails.

comprised of the concatenation of all BCC addresses
Customer References O The reference information to associate with the order.
Note: Up to two customer references are supported. A

P_O_NUMBER reference is required when paying via
some FedEx accounts and is optional when paying via
credit card. If the request includes a Customer
Configuration Profile Name value, a
CUSTOMER_REFERENCE reference is used to
populate a P.O. Number reference on the label of the
FedEx shipment used to deliver the order (if that option
is enabled in the profile). The credit card processor will
only accept alphanumeric characters in the P.O.
Number and customer reference fields. If special
characters are entered, they may be removed before
transaction is sent to credit card processor and the
integrator will receive a notification that the special
characters may be removed.
Discount Code O Identifies the FedEx account number enabled for print to use
in calculating print discounts for the order.
Note: This element may only be populated when the

account is a non-invoiced account eligible for print
discount.
Promotion Code O Identifies the promotion code to use in calculating discounts

for the order.
Order Contact
Contact R Identifies the contact person’s contact information.
Address R Identifies the contact person’s physical address.

Required/
Conditional
Order Contact > Contact

Person Name R Identifies the contact person’s name.
Company Name O Identifies the contact person's company name.
Phone Number R Identifies the contact person's phone number.
Phone Extension O Identifies the contact person’s phone extension.
Fax Number O Identifies the contact person's fax machine phone number.
Email Address R Identifies the contact person's email address.
Order Contact > Contact > Person Name

First Name R Identifies the contact person's first name.
Last Name R Identifies the contact person's last name.
Order Contact > Address

Street Lines R Identifies the contact person’s street address.

City R Identifies the contact person’s city.
State or Province Code R Identifies the contact person’s state.
Abbreviation for US state.
Postal Code R Identifies the contact person’s postal code.
Country Code R Identifies the contact person’s country.
Values:
• US
Delivery Group
Name O Identifies the delivery group. The Name from the request is
echoed back to the caller in the corresponding reply.

Required/
Conditional
Description O Provides additional descriptive information about the delivery

group. The Description from the request is echoed back to the
caller in the corresponding reply.
Print Line Items R Descriptive data about the contents of this delivery group.
Multiple line items are allowed per delivery group.
Delivery Method R Descriptive data about the method of delivery.
Print Line Item

Number of Copies R Identifies the number of copies of the document to be printed.
Catalog Document O Descriptive data about the catalog document to be printed.

both.
Document R Descriptive data about the ad hoc document to be printed.

both.
Catalog Document
order. Each order's documents must be numbered

hoc).
Type R Specifies the type of catalog that contains the document being
ordered.
Values:
• GLOBAL
• PERSONAL
Note: Orders for documents from personal catalogs are not

currently supported.
Folder Path R Specifies the catalog folder path where the document can be
found.

Required/
Conditional
Document Name R Specifies the name of the document as stored in the catalog.
Customized Sections O The descriptive data about the individual sections of the
catalog document being customized, if any.
Proof Type O Indicates whether/how the customer intends to review a

Values:
• DECLINED
Customized Sections
document.
Note: This element is required when the catalog document

contains more than one section.
that was used to upload the file. Combined with FileToken, it
when it was uploaded. Combined with UploadSessionId, it
Document
order. Each order’s documents must be numbered

hoc).
Name O Identifies the document. The Name from the request is echoed
Note: This element is required when the document is

populated with more than one section.
Finishing Options Requested O Descriptive data about the document finishing that is
requested for the printed document.
Sections R Descriptive data about the individual sections that make up

the document.

Required/
Conditional
Document Options O Descriptive data about the options requested for the
Requested document.
Proof Type C Indicates whether/how the customer intends to review a

Values:
• DECLINED
Note: When a transaction is based on a non-PDF file or

specifies a media size that differs from the
dimensions native to the document, the proof must be
explicitly declined (Proof Type = “DECLINED”).
Finishing Options Requested

Finishing Option Types O Identifies each document finishing option requested by the
customer.
Values:
• UNCOLLATED
• STAPLING
• DRILLING
• CUTTING
• FIRST_PAGE_IN_COLOR
• FIRST_PAGE_AS_COVER
• FRONT_COVER
• BACK_COVER
• FOLDING
• BINDING
• BINDER
• LAMINATION
• INSERT
Stapling Detail C The descriptive data required for a document to be stapled.
Note: This element is required when STAPLING is present

Drilling Detail C The descriptive data required for a document to be drilled (i.e.,
hole-punched).
Note: This element is required when DRILLING is present in


Required/
Conditional
Cutting Detail C The descriptive data required for a document to be cut.
Note: This element is required when CUTTING is present in

Front Cover Media Detail C The descriptive data required for a document's front cover.
Note: This element is required when FRONT_COVER is

Types collection.
Back Cover Media Detail C The descriptive data required for a document's back cover.
Note: This element is required when BACK_COVER is

Types collection.
Folding Detail C The descriptive data required for a document to be folded.
Note: This element is required when FOLDING is present in

Binding Detail C The descriptive data required for a document to be bound.
Note: This element is required when BINDING is present in

Binder Detail C The descriptive data required for a document to be inserted in

a binder.
Note: This element is required when BINDER is present in

Lamination Detail O The descriptive data related to document lamination.
Note: This element is only accepted when LAMINATION is

Insert Detail O Specifies details derived from one or more requested

document inserts.
Note: This element is only accepted when INSERT is present

in the Finishing Option Types collection

Required/
Conditional
Tab Detail O Specifies the detail of a document tab.
Note: This element is a subset of the Inserts detail when tabs

are requested. Only accepted when INSERT DETAIL is used
Stapling Detail
Stapling Type R Identifies the type of stapling.
Values:
• LEFT_UPPER
• TWO_ON_LONG_SIDE
Drilling Detail
Drilling Type R Identifies the type of drilling.
Values:
• THREE_HOLE_SIDE
• TWO_HOLE_TOP
Cutting Detail
Cutting Type R Identifies the type of cutting.
Values:
• HALF_CUT_PORTRAIT
• HALF_CUT_LANDSCAPE
• THIRD_CUT_PORTRAIT
• THIRD_CUT_LANDSCAPE
• QUARTER_CUT_PORTRAIT
• QUARTER_CUT_LANDSCAPE
Front Cover Media Detail

Media Category R Indicates the media category used for Front Cover. Combined
Values:
• CARDSTOCK
• COVER

Required/
Conditional
Media Description R Indicates the media description used for Front Cover.
media.
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• FROSTED_COVER
• CLEAR_COVER
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Back Cover Media Detail

Media Category R Indicates the media category used for Back Cover. Combined
Values:
• CARDSTOCK
• COVER

Required/
Conditional
Media Description R Indicates the media description used for Back Cover.
media.
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• FROSTED_COVER
• CLEAR_COVER
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Folding Detail
Text Position C Identifies whether the text on the page should be on the inside
or outside of the document after it is folded. Only applies to
single-folding and single-page double-folding.
Values:
• IN
• OUT

Required/
Conditional
Folding Type R Identifies the type of folding.
Values:
• SINGLE
• DOUBLE
• Z
Binding Detail
Binding Type R Identifies the type of binding.
Values:
• COIL
• COMB
Binder Detail
Binder Color R Identifies the color of the binder.
Values:
• BLACK
• WHITE
Binder Size R Identifies the size of the binder.
Values:
• ONE_HALF_INCH
• ONE_INCH
• ONE_AND_ONE_HALF_INCH
• TWO_INCH
• THREE_INCH
First Page in Cover O Indicates whether an extra copy of the first page of the
document should be printed and inserted in the clear plastic
cover.
Values:
• TRUE
• FALSE

Required/
Conditional
Lamination Detail
Border Type O Specifies the size of the lamination border around the edge of
the document (if a border is desired).
Values:
• ONE_QUARTER_INCH
Insert Details
Sequence Number R A unique identifier for this insert within the document.
Page Number R Specifies the page numbers where Inserts must be added
(enter page number of document where the insert should
follow. If insert is to become page 5 of the document, then it
should be inserted after page 4 of the document; enter value
of 4)
When a tab is inserted after an odd numbered page for

double-sided, a blank page will be inserted for tab to be
placed properly.
Media Category O Indicates the media category used for Inserts. Combined with
Media Description, it uniquely identifies the media.
Values:
• CARDSTOCK
• COVER
• STANDARD

Required/
Conditional
Media Description R Indicates the media description used for Inserts. Combined
with Media Category, it uniquely identifies the media.
• ULTRA_LIME
• SUN_YELLOW
• ULTRA_ORANGE
• RED
• ULTRA_FUCHSIA
• BRIGHT_BLUE
• NATURAL
• IVORY
• CANARY
• PASTEL_BLUE
• PASTEL_GREEN
• INDEX_110_LB
Values for COVER:
• FROSTED_COVER
• CLEAR_COVER
• SOFT_PINK
• SANDSTONE
• SEA_SPRAY
• ANTIQUE_GRAY
Tab Detail
Label Lines O One or more text lines that may appear on the tab of a
document insert.
Line Number R Specifies the line number of the Label on the Tab
Values:
• 1
• 2

Required/
Conditional
Content O Specifies the text content appearing on the Label Line. The
maximum character length per Label line is 30.
Font O The font details used to render the text on the tab label lines.
Name R Specifies the font name
Values:
• Arial
• Arial Narrow
• Times New Roman
Size R Specifies the size of the font
Values:
• 8
• 10
• 12
• 14
Styles R Specifies the font style
Values:
• Bold
• Italics
• Underline
Orientation O Specifies the orientation of the Label on Tab
Values:
• Portrait (Text In) – text on the tab will be facing inward

• Landscape (Text Out) – text on the tab will be facing
outward
Section
document. Each document’s sections must be numbered
Note: This element is required if the document is populated

with more than one section.

Required/
Conditional
Print Type C Identifies the print type of the document.
Values:
• BLACK_AND_WHITE
• COLOR

Document Option Types collection for this Document.
Number of Sides C Identifies whether the document is to be printed on one side or

both sides of the media.
Values:
• SINGLE
• DOUBLE

Section Media Detail C The descriptive data that identifies the media on which the
section is to be printed.

Section Options Requested C The descriptive data about the options requested for the
section.
Note: This element is required if the file associated with the

section has a presentation file type (e.g., Microsoft
PowerPoint).
Section Media Detail

Required/
Conditional
Media Category R Indicates the media category used for the section. Combined
Values:
• CARBONLESS_MULTI_PART
• CARDSTOCK
• COVER_GLOSS
• EXECUTIVE
• PASTEL_BRIGHTS
• RESUME
• STANDARD
• STANDARD_LASER
• TEXT_GLOSS
• TRANSPARENCY
Media Description R Indicates the media description used for the section.
media.
Values:
• ANTIQUE • RECYCLED_100_PERCENT
• ANTIQUE_GRAY • RECYCLED_30_PERCENT
• BRIGHT_BLUE • RED
• CANARY • SALMON
• FOUR_PART • SANDSTONE
• GLOSS_COVER_10_PT • SEA_SPRAY
• GLOSS_TEXT • SIGNATURE_WHITE
• INDEX_110_LB • SOFT_PINK
• IVORY • STANDARD_WHITE
• LASER_PAPER • SUN_YELLOW
• NATURAL • TAN
• ORCHID • THREE_PART
• PASTEL_BLUE • TRANSPARENCY
• PASTEL_GREEN • TWO_PART
• PURE_WHITE • ULTRA_BRIGHT_WHITE
• ULTRA_FUCHSIA
• ULTRA_LEMON
• ULTRA_LIME
• ULTRA_ORANGE
• WILLOW

Required/
Conditional
Media Size O Identifies the media's size.
Values:
• LETTER
• LEGAL
• TABLOID
• CUSTOM
Note: This element does not apply to cover media. This is

only needed when the desired media size differs from
the media size defined in the file that was uploaded.
Media Dimensions C Descriptive data specifying the exact dimensions of the media.
Note: This element only applies when CUSTOM is specified

as the Media Size. This element does not apply to
cover media.
Media Dimensions
Length R Indicates the length of the media, in the unit of measure stated
in the Units element.
Note: Value must be between 0.01 and 120.
Width R Indicates the width of the media, in the unit of measure stated
in the Units element.
Note: Value must be between 0.01 and 120.
Units R Indicates the unit of measure in which the length and width
values are stated.
Values:
• IN
Section Options Requested

Required/
Conditional
Section Option Types C Identifies each section option requested by the customer.
Values:
• PRESENTATION_OUTPUT
Note: PRESENTATION_OUTPUT must be present in the

Section Option Types collection if the section’s
corresponding file has a presentation file type (e.g.,
Microsoft PowerPoint).
Presentation Output Detail C Descriptive data required for a section based on a

presentation file.

PRESENTATION_OUTPUT is present the Section
Option Types collection.
Presentation Output Detail

Output Type R Indicates the type of presentation output.
Values:
• HANDOUTS
• NOTES
• SLIDES

Required/
Conditional
Output Options O Identifies the presentation options requested by the customer.
Values:
• FRAME_SLIDES
Handout Detail C Descriptive data required for handouts to be produced for a

presentation file.
Note: This element is required when HANDOUTS is

specified as the Output Type.
Handout Detail
Layout R Indicates the number of slides to be printed per page.
Values:
• ONE_SLIDE_PER_PAGE
• TWO_SLIDES_PER_PAGE
• THREE_SLIDES_PER_PAGE
• FOUR_SLIDES_PER_PAGE
• SIX_SLIDES_PER_PAGE
• NINE_SLIDES_PER_PAGE
Slide Order R Indicates whether slides should be ordered vertically before

wrapping to a new column or horizontally before wrapping to a
new row.
Values:
• HORIZONTAL
• VERTICAL
Note: When Layout specifies fewer than four slides per

page, both options result in the same output.

Required/
Conditional
Document Options Requested

Document Option Types O Identifies each document option requested by the customer.
Values:
• SPECIAL_INSTRUCTIONS
Special Instructions Details C Descriptive data about the special instructions specified by the
customer for the document.

Document Option Types collection.
Special Instructions Details

Special Instructions Type R Identifies the type of special instructions specified by the
customer.
Values:
• OTHER
Instructions C Identifies the customer’s special instructions for the document.
Note: This element is required if Special Instructions Type is

OTHER.
Delivery Method
Delivery Type R Identifies the type of delivery for the delivery group.
Values:
• DIRECT_MAIL
• LOCAL_DELIVERY
• PICKUP
• SHIPMENT
Note: DIRECT_MAIL may only be requested if a value is

populated for Customer Configuration Profile Name
and that profile has been authorized for direct mail.

Required/
Conditional
Order Recipient C Descriptive data about the recipient of the documents in the
delivery group.
Note: This element is required if the Delivery Type is

LOCAL_DELIVERY, PICKUP, or SHIPMENT. For
PICKUP delivery groups, the recipient is the person
picking up the delivery group. For
LOCAL_DELIVERY and SHIPMENT delivery groups,
the recipient is the person who will receive the
delivery group. If Delivery Type is DIRECT_MAIL,
populating this element will result in an error.
Center ID O Specifies the unique identifier of the FedEx Office location

where the recipient wishes to receive the delivery group (for a
pickup delivery group) or where the order contact wishes to
have it produced (for a local delivery, shipment, or direct mail
delivery group).
Order Direct Mail Detail C Descriptive data about the direct mail recipient list.
Note: This element is required when DIRECT_MAIL is

Order Local Delivery Detail C Descriptive data about the requested local delivery.
Note: This element is required when LOCAL_DELIVERY is

Order Pickup Detail C Descriptive data about the criteria to use in selecting a FedEx
Office location for delivery group pickup.
Note: This element is required when PICKUP is specified as

the Delivery Type and no Center ID is specified.
Order Shipment Detail C Descriptive data about the FedEx billing and service details for
the delivery group shipment.
Note: This element is required when SHIPMENT is

Order Recipient
Contact R Identifies the recipient’s contact information.
Address C Identifies the recipient’s physical address.

SHIPMENT.
If Delivery Type is PICKUP, populating this element

will result in an error.

Required/
Conditional
Order Recipient > Contact

Person Name R Identifies the recipient’s name.
Company Name O Identifies the recipient’s company name.
Phone Number R Identifies the recipient’s phone number.
Phone Extension O Identifies the recipient’s phone extension.
Email Address C Identifies the recipient’s email address.

PICKUP.
Order Recipient > Contact > Person Name

First Name R Identifies the recipient's first name.
Last Name R Identifies the recipient’s last name.
Order Recipient > Address

Street Lines R Identifies the recipient’s street address.

be included.
City R Identifies the recipient’s city.
State or Province Code R Identifies the recipient’s state.
Postal Code R Identifies the recipient’s postal code.
Country Code R Identifies the recipient’s country.
Values:
• US

Required/
Conditional
Residential O Indicates whether this address is residential (as opposed to

commercial).
Values:
• TRUE
• FALSE
Order Direct Mail Detail

that was used to upload the recipient address file. Combined
with File Token, it uniquely identifies the file.
uniquely identifies the recipient address file.
Address Count R Specifies the number of lines in the file, where each line
corresponds to a single address. This field exists for
verification purposes.
Order Local Delivery Detail

Requested Delivery Date R Identifies the local date when the delivery group recipient
wishes to receive the delivery group.
Requested Delivery Window R Identifies the local time window when the delivery group
recipient wishes to receive the delivery group.
Values:
• MORNING
• AFTERNOON
Delivery Instructions O Contains any detailed instructions or requests that the

customer wishes to specify.
Order Pickup Detail

Location Search Criteria O Descriptive data about the address to use in selecting a
FedEx Office location.
Note: This element is required when no Center ID is

specified.

Required/
Conditional
Due Date and Time O Identifies the local date and time when the delivery group
recipient wishes to pick up the delivery group.
Format: YYYY-MM-DDTHH
Example: 2013-06-25T18
Location Search Criteria

Street Lines O Identifies street address near which recipient wishes to pick up
the delivery group.

be included.
City C Identifies city near which recipient wishes to pick up the

delivery group.
State or Province Code C Identifies state near which recipient wishes to pick up the
delivery group.
Postal Code C Identifies postal code near which recipient wishes to pick up
the delivery group.
Note: Required if both City and State or Province Code are

not populated.
Country Code R Identifies the country where the recipient wishes to pick up the
delivery group.
Values:
• US
Order Shipment Detail

Shipping Charges Payment O Descriptive data indicating the method and means of payment
to FedEx for providing shipping services, if different from the
payment method for the FedEx Office printing charges.

Required/
Conditional
Service Type R Identifies the FedEx service to use in shipping the package.
Values:
• FIRST_OVERNIGHT
• PRIORITY_OVERNIGHT
• STANDARD_OVERNIGHT
• FEDEX_2_DAY
• FEDEX_EXPRESS_SAVER
• FEDEX_GROUND
• GROUND_HOME_DELIVERY
Shipping Charges Payment

Payment Type R Identifies the method of payment for shipping services.
Values:
• RECIPIENT
• THIRD_PARTY
Payor R The descriptive data identifying the party responsible for

payment of shipping.
Shipping Charges Payment > Payor

Responsible Party R The descriptive data about the payor's FedEx account to be
used for the shipping portion of the order. This element is
required when the shipping charges party is specified
separately from printing charges party.
Shipping Charges Payment > Payor > Responsible Party

Account Number R Identifies the FedEx account number used for shipping.
Note: This will produce a separate invoice from Print.
Office Order Charges Payment

Payment Type R The descriptive data for the means of payment for any
charges assessed by FedEx Office.
Values:
• ACCOUNT
• CREDIT_CARD

Required/
Conditional
Payor C The descriptive data identifying the party responsible for

payment of any charges assessed by FedEx Office.

ACCOUNT.
Credit Card C The descriptive data required for payment via credit card.

CREDIT_CARD.
CVV O Identifies the credit card’s CVV number
Note: CVV is 3 digit numeric code for VISA, MasterCard and

Discover, Diners Club. CVV is 4 digit numeric code for
American Express.
Office Order Charges Payment > Payor

Associated Accounts R The descriptive data about a separate FedEx account number
assigned to the payor that is associated with a specific FedEx
operating company.
Office Order Charges Payment > Payor > Associated Accounts

Type R Identifies the FedEx operating company that issued the
account.
Values:
• FEDEX_OFFICE
Account Number R Identifies the FedEx account number assigned to the payor.
Office Order Charges Payment > Credit Card

Number R Identifies the credit card’s number.
Credit Card Type R Identifies the credit card’s type.
Values:
• AMEX
• DINERS
• DISCOVER
• MASTERCARD
• VISA

Required/
Conditional
Expiration Date R Identifies the credit card’s expiration date.
Note: The date must be stated in one of the following

formats: YYMM, YYYYMM, YYYYMMDD.
Credit Card Holder R Descriptive data about the credit card’s holder.
Office Order Charges Payment > Credit Card > Credit Card Holder
Contact R Identifies the credit card holder’s contact information.
Address R Identifies the credit card holder’s physical address.
Office Order Charges Payment > Credit Card > Credit Card Holder > Contact
Person Name R Identifies the credit card holder’s name.
Company Name O Identifies the credit card holder’s company name.
Phone Number R Identifies the credit card holder’s phone number.
Office Order Charges Payment > Credit Card > Credit Card Holder > Contact > Person Name
First Name R Identifies the credit card holder’s first name.
Last Name R Identifies the credit card holder’s last name.
Office Order Charges Payment > Credit Card > Credit Card Holder > Address
Street Lines R Identifies the credit card holder’s street address.

City R Identifies the credit card holder’s city.
State or Province Code R Identifies the credit card holder’s state.
Values: Abbreviation for US state.
Postal Code R Identifies the credit card holder’s postal code. (Validated by
the payment processor.)

Required/
Conditional
Country Code R Identifies the credit card holder’s country.
Values:
• US
Customer References
Type R Identifies the type of customer reference.
Values:
• CUSTOMER_REFERENCE
• P_O_NUMBER
Value R Identifies the customer reference value.
Note: The credit card processor will only accept alphanumeric

characters in the P.O. Number and customer reference
fields. If special characters are entered, they may be
removed before transaction is sent to credit card
processor and the integrator will receive a notification
that the special characters may be removed.


Create Order Reply Elements
Element Description
Create Office Order Reply

• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS

request.
Completed Office Order The descriptive data generated by FedEx Office for the order that was
submitted for creation.
Notifications
• FAILURE
• ERROR
• WARNING
• NOTE
• SUCCESS

message.

Element Description

Source, it uniquely identifies this message.
Message Contains text that explains this notification.

Message Parameters
Transaction Detail
transaction call.
Version
Value:
• oord
Completed Office Order

Order Global Tracking Specifies the unique identifier of the FedEx Office order that was
Number created.
Completed Delivery Group Pricing and delivery method details generated by FedEx Office for each
Details delivery group in the order that was created.
Pricing The aggregate pricing information for the entire FedEx Office order.

Element Description
Completed Delivery Group Details

Name Identifies the delivery group. The Name from the request is echoed
Description Provides additional descriptive information about the delivery group.

The Description from the request is echoed back to the caller in the
Completed Catalog Document-level details generated by FedEx Office for each catalog
Document Details document in the delivery group that was created.
Completed Document Document-level details generated by FedEx Office for each ad hoc
Details document in the delivery group that was created.
Pricing The aggregate pricing information for the entire delivery group.
Completed Order Local The descriptive data specifying which FedEx Office location will be
Delivery Detail delivering the delivery group. This element only applies when
LOCAL_DELIVERY is specified as the Delivery Type.
Completed Order Pickup The descriptive data specifying where and when the delivery group will
Detail be available for pickup. This element only applies when PICKUP is
Completed Catalog Document Details

Type Specifies the type of catalog that contains the document. The Type
from the request is echoed back to the caller in the corresponding reply.
Folder Path Specifies the catalog folder path where the document can be found.
The Folder Path from the request is echoed back to the caller in the
Document Name Specifies the name of the document as stored in the catalog. The
Document Name from the request is echoed back to the caller in the
Completed Catalog Document Details > Pricing


Element Description
Completed Catalog Document Details > Pricing > Total Cost

Values:
• USD
Completed Catalog Document Details > Pricing > Total Discount

Values:
• USD
Completed Catalog Document Details > Pricing > Net Cost

Values:
• USD
Completed Catalog Document Details > Pricing > Costs

Type Identifies the type of cost associated with the completed document.
Values:
• BASE_COST
• OTHER

Element Description
Completed Catalog Document Details > Pricing > Costs > Amount
Values:
• USD
Completed Catalog Document Details > Pricing > Discounts

Type Identifies the type of discount associated with the completed document.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Completed Catalog Document Details > Pricing > Discounts > Amount
Values:
• USD
Completed Document Details

Name Identifies the document. The Name from the request is echoed back to
the caller in the corresponding reply. If there is no Name value in the
request, this will be the document's filename.
Completed Document Details > Pricing


Element Description
Completed Document Details > Pricing > Total Cost

Values:
• USD
Completed Document Details > Pricing > Total Discount

Values:
• USD
Completed Document Details > Pricing > Net Cost

Values:
• USD
Completed Document Details > Pricing > Costs

Type Identifies the type of cost associated with the completed document.
Values:
• BASE_COST
• OTHER

Element Description
Completed Document Details > Pricing > Costs > Amount

Values:
• USD
Completed Document Details > Pricing > Discounts

Type Identifies the type of discount associated with the completed document.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Completed Document Details > Pricing > Discounts > Amount

Values:
• USD
Completed Delivery Group Details > Pricing

Costs A list capturing each cost amount and its respective type. At the
delivery group level, the list includes both group-level costs as well as
all costs associated with the delivery group’s documents.

Element Description
delivery group level, the list includes both group-level discounts as well
as all discounts associated with the delivery group’s documents.
Completed Delivery Group Details > Pricing > Total Cost

Values:
• USD
Completed Delivery Group Details > Pricing > Total Discount

Values:
• USD
Completed Delivery Group Details > Pricing > Net Cost

Values:
• USD
Completed Delivery Group Details > Pricing > Tax

Values:
• USD

Element Description
Completed Delivery Group Details > Pricing > Net Price

Values:
• USD
Completed Delivery Group Details > Pricing > Costs

Type Identifies the type of cost associated with the completed delivery group.
Values:
• BASE_COST
• FILE_RENDERING
• HANDLING
• OTHER
• POSTAGE
• SHIPPING
Completed Delivery Group Details > Pricing > Costs > Amount
Values:
• USD
Completed Delivery Group Details > Pricing > Discounts

Type Identifies the type of discount associated with the completed delivery
group.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER

Element Description
Completed Delivery Group Details > Pricing > Discounts > Amount
Values:
• USD
Completed Order Local Delivery Detail

FedEx Office Center Detail Identifies the FedEx Office location that will be delivering the delivery
group.
Completed Order Local Delivery Detail > FedEx Office Center Detail
Name Identifies the name of the FedEx Office location that will be delivering
the delivery group.
ID Specifies the unique identifier that FedEx Office uses to designate the
location that will be delivering the delivery group.
Address Identifies the address of the FedEx Office location that will be delivering
the delivery group.
Phone Number Identifies the phone number of the FedEx Office location that will be
delivering the delivery group.
Email Address Identifies the email address of the FedEx Office location that will be
Completed Order Local Delivery Detail > Address

Street Lines Identifies the address of the FedEx Office location that will be delivering
the delivery group.
City Identifies the city of the FedEx Office location that will be delivering the
delivery group.
State or Province Code Identifies the state of the FedEx Office location that will be delivering
the delivery group.
Postal Code Identifies the postal code of the FedEx Office location that will be

Element Description
Country Code Identifies the country of the FedEx Office location that will be delivering
the delivery group.
Values:
• US
Completed Order Pickup Detail

Center Name Identifies the name of the FedEx Office location where the delivery
group will be available for pickup.
Center ID Specifies the unique identifier that FedEx Office uses to designate the
location where the delivery group will be available for pickup.
Center Address Identifies the address of the FedEx Office location where the delivery
Center Phone Number Identifies the phone number of the FedEx Office location where the
delivery group will be available for pickup.
Center Email Address Identifies the email address of the FedEx Office location where the
delivery group will be available for pickup.
Due Date and Time Indicates the local date/time when the delivery group will be available
for pickup.
Completed Order Pickup Detail > Center Address

Street Lines Identifies the address of the FedEx Office location where the delivery
City Identifies the name of the city where the delivery group will be available
for pickup.
State or Province Code Identifies the name of the state where the delivery group will be
available for pickup.
Postal Code Identifies the postal code where the delivery group will be available for
pickup.
Country Code Identifies the name of the country where the delivery group will be
available for pickup.
Values:
• US

Element Description
Completed Office Order > Pricing

Costs A list capturing each cost amount and its respective type. At the order
level, the list includes both order-level costs as well as all costs
associated with the order’s delivery groups and documents.
order level, the list includes both order-level discounts as well as all
discounts associated with the order’s delivery groups and documents.
Completed Office Order > Pricing > Total Cost

Values:
• USD
Completed Office Order > Pricing > Total Discount

Values:
• USD
Completed Office Order > Pricing > Net Cost

Values:
• USD

Element Description
Completed Office Order > Pricing > Tax

Values:
• USD
Completed Office Order > Pricing > Net Price

Values:
• USD
Completed Office Order > Pricing > Costs

Type Identifies the type of cost associated with the completed order.
Values:
• BASE_COST
• FILE_RENDERING
• HANDLING
• OTHER
• POSTAGE
• SHIPPING
Completed Office Order > Pricing > Costs > Amount

Values:
• USD

Element Description
Completed Office Order > Pricing > Discounts

Type Identifies the type of discount associated with the completed order.
Values:
• VOLUME
• ACCOUNT
• PROMOTION
• OTHER
Completed Office Order > Pricing > Discounts > Amount

Values:
• USD


Appendix


Examples
This section of the guide provides example SOAP messages for the Office Order Web
Service (OORD).
Request and reply transactions are provided for each of the below functions:
• Upload Location
Example: Get Upload Location request with correct credentials
Service Request: Click Here
Service Reply: Click Here
Upload Document File: Click Here
Upload Multiple Document Files: Click Here
• Rate Office Order

Example: 25 copies of a single-sided, black and white document
• Create Office Order

Example 1: Five copies of a single-sided, double-folded ad hoc document
printed in color and picked up by the customer
Example 2: 399 copies of a coil-bound, double-sided, black and white ad

hoc document with a black vinyl back cover that will be
delivered to the customer via FedEx Priority Overnight®.

Example 3: Ten copies of a double-sided, color ad hoc document (ex. Flyers).
28 copies of a 100-page, single-sided, black and white ad hoc
document, stapled.
Both documents will be delivered via FedEx
Ground®. Paid with a credit card using CVV
Example 4: 30 copies of a multi-section ad hoc document composed of 3 separate

digital files. File 1 is a one-page, single-sided, black and white cover
page. File 2 is 100 pages, double-sided, and color. File 3 is ten pages,
single-sided, and black and white. All the sections are stapled together
and picked up by the customer.
Example 5: 1 copy of a catalog document with a single customized section plus

one copy of an ad hoc document, to be sent via direct mail to 250
addressees.
Example 6: Ten copies of a double-sided, color ad hoc document (ex. Flyers).

28 copies of a 100-page, single-sided, black and white ad hoc
document, Drilled with Tab insert.
Paid with a credit card using CVV


Upload Location Request
Example
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:v2="http://fedex.com/ws/officeorder/v2">
<soapenv:Header/>
<soapenv:Body>
<v2:OfficeOrderUploadLocationRequest>
<v2:WebAuthenticationDetail>
<v2:UserCredential>
<v2:Key>xxxxxxxxxxxxxxxx</v2:Key>
<v2:Password>xxxxxxxxxxxxxxxxxxxxxxxxx</v2:Password>
</v2:UserCredential>
</v2:WebAuthenticationDetail>
<v2:ClientDetail>
<v2:ClientProductId>XXXX</v2:ClientProductId>
<v2:ClientProductVersion>0000</v2:ClientProductVersion>
<v2:IntegratorId>00000</v2:IntegratorId>
</v2:ClientDetail>
<v2:TransactionDetail>
<v2:CustomerTransactionId>sampleTransaction</v2:CustomerTransactionId>
</v2:TransactionDetail>
<v2:Version>
<v2:ServiceId>oord</v2:ServiceId>
<v2:Major>3</v2:Major>
<v2:Intermediate>1</v2:Intermediate>
<v2:Minor>0</v2:Minor>
</v2:Version>
</v2:OfficeOrderUploadLocationRequest>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples

Upload Location Reply
Example
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<OfficeOrderUploadLocationReply
xmlns="http://fedex.com/ws/officeorder/v2">
<HighestSeverity>SUCCESS</HighestSeverity>
<Notifications>
<Severity>SUCCESS</Severity>
<Source>oord</Source>
<Code>0000</Code>
<Message>Request was successful.</Message>
<LocalizedMessage>Request was successful.</LocalizedMessage>
</Notifications>
<TransactionDetail>
<CustomerTransactionId>sampleTransaction</CustomerTransactionId>
</TransactionDetail>
<Version>
<ServiceId>oord</ServiceId>
<Major>3</Major>
<Intermediate>1</Intermediate>
<Minor>0</Minor>
</Version>
<UploadUrl>https://printonline.fedex.com/partnerUpload.process?authToken=11111
11111111111111111111111111111111111&partnerId=1111111111</UploadUrl>
<UploadSessionId>11111111111111111111111111111111111111111111111111</Upload Ses
sionId>
</OfficeOrderUploadLocationReply>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Back to Examples

Note: The below example is written in Java. It is provided for illustrative purposes only and
is not intended for production application nor guaranteed to work for all programming
languages, applications, and host systems.
public static String uploadFile(String filepath, String uploadUrl) {

String fileToken = null;
try {
PostMethod filePost = null;
HttpClient client = new
HttpClient();
// client.getHostConfiguration().setProxy("your proxy url", your
proxy port number);
File f = new File(filepath);
// Create the file part of the Multipart request - name must be"file1"
Part[] parts = { new FilePart("file1", f) };
filePost = new PostMethod(uploadUrl);
filePost.setRequestEntity(new MultipartRequestEntity(parts,
filePost.getParams()));
int status = client.executeMethod(filePost);
if (status == HttpStatus.SC_OK) {
System.out.println(filePost.getResponseBodyAsString());
fileToken = filePost.getResponseBodyAsString().substring(
filePost.getResponseBodyAsString().indexOf("fileAuthToken=") +
"fileAuthToken=".length());
} else {
System.out.println("Upload failed, response=" +
HttpStatus.getStatusText(status));
}
} catch (Exception ex) {
ex.printStackTrace();
}
return fileToken;
}
Back to Examples

Upload Multiple Document Files
Note: The below example is written in Java. It is provided for illustrative purposes only and
is not intended for production application nor guaranteed to work for all programming
languages, applications, and host systems.
public static String[] uploadFiles(String[] filepath, String uploadUrl) {

String[] fileTokens = null;
try {
PostMethod filePost = null;
HttpClient client = new HttpClient();
// client.getHostConfiguration().setProxy(proxy, port);
Part[] parts = new FilePart[filepath.length];
for (int i = 0; i < filepath.length; i++) {
File f = new File(filepath[i]);
String filename = "file" + (i + 1);
System.out.println("filename=" + filename);
FilePart fp = new FilePart(filename, f);
parts[i] = fp;
}
filePost = new PostMethod(uploadUrl);
filePost.setRequestEntity(new MultipartRequestEntity(parts,
filePost.getParams()));
int status = client.executeMethod(filePost);
if (status == HttpStatus.SC_OK) {
String response =
java.net.URLDecoder.decode(filePost.getResponseBodyAsString(),
"UTF-8");
System.out.println(response);
fileTokens = getFileTokens(response);
} else {
System.out.println("Upload failed, response=" +
HttpStatus.getStatusText(status));
}
} catch (Exception ex) {
ex.printStackTrace();
}
return fileTokens;
}
public static String[] getFileTokens(String input) {
String fileTokenStr = input.substring(input.indexOf("fileAuthToken=") +
"fileAuthToken=".length());
String[] fileTokens = fileTokenStr.split(",", -1);
return fileTokens;
}
Back to Examples

Rate Office Order Request
Example
<soapenv:Header />
<soapenv:Body>
<v2:RateOfficeOrderRequest>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>


<v2:CustomerTransactionId>0001</v2:CustomerTransactionId>
<v2:Version>
</v2:Version>
<v2:RequestedOfficeOrder>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
<v2:FirstName>John</v2:FirstName>
<v2:LastName>Doe</v2:LastName>
</v2:PersonName>

<v2:CompanyName>ABC Company</v2:CompanyName>
<v2:PhoneNumber>9015555555</v2:PhoneNumber>

<v2:FaxNumber>9015555556</v2:FaxNumber>

<v2:EMailAddress>john.doe@abccompany.com</v2:EMailAddress>
</v2:Contact>

<v2:Address>


<v2:StreetLines>100 Main Street</v2:StreetLines>
<v2:StreetLines>2nd Floor</v2:StreetLines>
<v2:City>Collierville</v2:City>
<v2:StateOrProvinceCode>TN</v2:StateOrProvinceCode>
<v2:PostalCode>38017</v2:PostalCode>
<v2:CountryCode>US</v2:CountryCode>

<v2:Residential>false</v2:Residential>
</v2:Address>
</v2:OrderContact>
<v2:DeliveryGroups>
<v2:DeliveryMethod>
<v2:DeliveryType>PICKUP</v2:DeliveryType>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
</v2:OrderRecipient>
<v2:OrderPickupDetail>
<v2:LocationSearchCriteria>
<v2:StreetLines />
<v2:City />
<v2:StateOrProvinceCode
/>
</v2:LocationSearchCriteria>
</v2:OrderPickupDetail>
</v2:DeliveryMethod>
<v2:PrintLineItems>
<v2:NumberOfCopies>25</v2:NumberOfCopies>
<v2:Document>
<v2:Sections>
<v2:UploadSessionId>11111111111111111111111111111111111111111111111111111111111
1</v2:UploadSessionId>
<v2:FileToken>11111111111111111111111111111111111111111</v2:FileToken>
<v2:PrintType>BLACK_AND_WHITE</v2:PrintType>
<v2:NumberOfSides>SINGLE</v2:NumberOfSides>
<v2:SectionMediaDetail>
<v2:MediaCategory>STANDARD</v2:MediaCategory>
<v2:MediaDescription>RECYCLED_100_PERCENT</v2:MediaDescription>
</v2:SectionMediaDetail>
</v2:Sections>

</v2:Document>
</v2:PrintLineItems>
</v2:DeliveryGroups>
<v2:OfficeOrderChargesPayment>
<v2:PaymentType>ACCOUNT</v2:PaymentType>
<v2:Payor>

<v2:AssociatedAccounts>
<v2:Type>FEDEX_OFFICE</v2:Type>
<v2:AccountNumber>00000000000000</v2:AccountNumber>
</v2:AssociatedAccounts>
</v2:Payor>
</v2:OfficeOrderChargesPayment>
</v2:RequestedOfficeOrder>
</v2:RateOfficeOrderRequest>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Rate Office Order Reply
Example
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<RateOfficeOrderReply xmlns="http://fedex.com/ws/officeorder/v2">
<Notifications>
<Code>0000</Code>
</Notifications>
<TransactionDetail>
<CustomerTransactionId>0001</CustomerTransactionId>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<RatedOfficeOrder>
<RatedDeliveryGroupDetails>
<RatedDocumentDetails>
<Name>testDocument.pdf</Name>
<Pricing>
<TotalCost>
<Currency>USD</Currency>
<Amount>3.25</Amount>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Type>BASE_COST</Type>
<Amount>
</Amount>

</Costs>
</Pricing>
<DocumentNumber>1</DocumentNumber>
</RatedDocumentDetails>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
<RatedOrderPickupDetail>
<CenterName>Collierville TN West Poplar</CenterName>
<CenterId>4548</CenterId>
<CenterAddress>
<StreetLines>1016 W Poplar Ave</StreetLines>
<StreetLines>1016 W Poplar Ave</StreetLines>
<City>Collierville</City>
<StateOrProvinceCode>TN</StateOrProvinceCode>
<PostalCode>38017</PostalCode>
<CountryCode>US</CountryCode>
<Residential>false</Residential>
</CenterAddress>
<CenterPhone>9018533799</CenterPhone>
<CenterEMailAddress>usa4548@fedex.com</CenterEMailAddress>
<DueDateTime>02/28/2018 04:00 PM</DueDateTime>
</RatedOrderPickupDetail>

</RatedDeliveryGroupDetails>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
</RatedOfficeOrder>
</RateOfficeOrderReply>
</SOAP-ENV:Body>
Back to Examples

Create Office Order Request
Example 1
<soapenv:Header/>
<soapenv:Body>
<v2:CreateOfficeOrderRequest>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:CustomerTransactionId/> </v2:TransactionDetail>
<v2:Version>
</v2:Version>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
<v2:EMailAddress>John.Doe@abccompany.com</v2:EMailAddress>
</v2:Contact>
<v2:Address>
<v2:StreetLines>2nd Floor </v2:StreetLines>


</v2:Address>
</v2:OrderContact>
<v2:DeliveryGroups>
<v2:DeliveryMethod>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:StreetLines/>
<v2:City/>
<v2:StateOrProvinceCode/>
<v2:PrintLineItems>
<v2:Document>

<v2:FinishingOptionsRequested>
<v2:FinishingOptionTypes>FOLDING</v2:FinishingOptionTypes>
<v2:FoldingDetail>
<v2:TextPosition>IN</v2:TextPosition>
<v2:FoldingType>DOUBLE</v2:FoldingType>
</v2:FoldingDetail>
</v2:FinishingOptionsRequested>
<v2:Sections>
</v2:UploadSessionId>
<v2:PrintType>COLOR</v2:PrintType>
<v2:MediaCategory>STANDARD_LASER</v2:MediaCategory>
<v2:MediaDescription>LASER_PAPER</v2:MediaDescription>
</v2:Sections>
</v2:Document>

<v2:Payor>

</v2:Payor>

<v2:OrderConfirmationEmailRequested>true
</v2:OrderConfirmationEmailRequested>

<v2:OrderCompletionEmailRequested>true
</v2:OrderCompletionEmailRequested>

<v2:OrderNotificationCCEmailAddresses>Sara.Smith@abccompany.com</v2:OrderNotif
icationCCEmailAddresses>

<v2:CustomerReferences>
<v2:CustomerReferenceType>P_O_NUMBER</v2:CustomerReferenceType>
<v2:Value>999</v2:Value>
</v2:CustomerReferences>
</v2:CreateOfficeOrderRequest>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Example 2
<soapenv:Header/>
<soapenv:Body>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:CustomerTransactionId/> </v2:TransactionDetail>
<v2:Version>
</v2:Version>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
<v2:StreetLines>555 Fairfield Lane</v2:StreetLines>
<v2:StreetLines>Apt #505</v2:StreetLines>
<v2:City>Memphis</v2:City>

<v2:Residential>true</v2:Residential>
</v2:Address>
</v2:OrderContact>
<v2:DeliveryGroups>
<v2:DeliveryMethod>

<v2:DeliveryType>SHIPMENT</v2:DeliveryType>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
<v2:FirstName>Jane</v2:FirstName>
<v2:LastName>Smith</v2:LastName>
</v2:PersonName>
<v2:EMailAddress>jane.smith@abccompany.com</v2:EMailAddress>
</v2:Contact>
<v2:Address>

</v2:Address>
<v2:OrderShipmentDetail>

<v2:ShippingChargesPayment>
<v2:PaymentType>RECIPIENT</v2:PaymentType>
<v2:Payor>
<v2:ResponsibleParty>
</v2:ResponsibleParty>
</v2:Payor>
</v2:ShippingChargesPayment>
<v2:ServiceType>PRIORITY_OVERNIGHT</v2:ServiceType>
</v2:OrderShipmentDetail>
<v2:PrintLineItems>
<v2:Document>
<v2:FinishingOptionTypes>BACK_COVER</v2:FinishingOptionTypes>
<v2:FinishingOptionTypes>BINDING</v2:FinishingOptionTypes>
<v2:BackCoverDetail>
<v2:MediaCategory>COVER</v2:MediaCategory>
<v2:MediaDescription>BLACK_VINYL_COVER</v2:MediaDescription>
</v2:BackCoverDetail>
<v2:BindingDetail>
<v2:BindingType>COIL</v2:BindingType>
</v2:BindingDetail>

<v2:Sections>
<v2:NumberOfSides>DOUBLE</v2:NumberOfSides>
</v2:Sections>
</v2:Document>
<v2:Payor>

</v2:Payor>

<v2:OrderConfirmationEmailRequested>true
</v2:OrderConfirmationEmailRequested>

<v2:OrderCompletionEmailRequested>true
</v2:OrderCompletionEmailRequested>

</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Example 3
<soapenv:Header />
<soapenv:Body>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:CustomerTransactionId>SystemRef</v2:CustomerTransactionId>
<v2:Version>
</v2:Version>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
<v2:PhoneNumber>901-555-5555</v2:PhoneNumber>
</v2:Contact>
<v2:Address>
</v2:Address>
</v2:OrderContact>
<v2:DeliveryGroups>

<v2:DeliveryMethod>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
</v2:Address>
<v2:Payor>
</v2:Payor>
<v2:ServiceType>FEDEX_GROUND</v2:ServiceType>
<v2:PrintLineItems>
<v2:Document>
<v2:DocumentNumber>1</v2:DocumentNumber>
<v2:Name>Sample Flyer</v2:Name>
<v2:Sections>
<v2:SectionNumber>1</v2:SectionNumber>

</v2:Sections>
</v2:Document>
<v2:PrintLineItems>
<v2:Document>
<v2:Name>Sample 2</v2:Name>
<v2:FinishingOptionTypes>STAPLING</v2:FinishingOptionTypes>
<v2:StaplingDetail>
<v2:StaplingType>LEFT_UPPER</v2:StaplingType>
</v2:StaplingDetail>
<v2:Sections>
<v2:MediaDescription>STANDARD_WHITE</v2:MediaDescription>
</v2:Sections>
</v2:Document>
<v2:PaymentType>CREDIT_CARD</v2:PaymentType>
<v2:CreditCard>
<v2:Number>111111111111111</v2:Number>
<v2:CreditCardType>AMEX</v2:CreditCardType>
<v2:ExpirationDate>2012</v2:ExpirationDate>
<v2:CreditCardHolder>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
<v2:City>COLLIERVILLE</v2:City>

</v2:Address>
</v2:CreditCardHolder>
<v2:VerificationCode>1012</v2:VerificationCode>
</v2:CreditCard>
<v2:OrderConfirmationEmailRequested>true</v2:OrderConfirmationEmailRequested>
<v2:OrderCompletionEmailRequested>true</v2:OrderCompletionEmailRequested>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Example 4
<soapenv:Header/>
<soapenv:Body>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:CustomerTransactionId>X0</v2:CustomerTransactionId>
<v2:Version>
</v2:Version>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
</v2:Address>
</v2:OrderContact>
<v2:DeliveryGroups>

<v2:DeliveryMethod>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
<v2:LastName>Smith</v2:LastName>
</v2:PersonName>
</v2:Contact>
<v2:PrintLineItems>
<v2:Document>
<v2:Name>My Document</v2:Name>
<v2:FinishingOptionTypes>STAPLING</v2:FinishingOptionTypes>
<v2:StaplingDetail>
<v2:StaplingType>LEFT_UPPER</v2:StaplingType>
</v2:StaplingDetail>
<v2:Sections>
<v2:MediaCategory>EXECUTIVE</v2:MediaCategory>
<v2:MediaDescription>SIGNATURE_WHITE</v2:MediaDescription>
</v2:Sections>
<v2:Sections>

</v2:Sections>
<v2:Sections>
</v2:Sections>
</v2:Document>
<v2:Payor>
</v2:Payor>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Example 5
<soapenv:Header/>
<soapenv:Body>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:UserDetail>
<v2:UserId>sample_user</v2:UserId>
<v2:Password>sample_password</v2:Password>
</v2:UserDetail>
<v2:Version>
</v2:Version>
<v2:CustomerConfigurationProfileName>Sample
Profile</v2:CustomerConfigurationProfileName>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
<v2:CompanyName>ABC Corporation</v2:CompanyName>
<v2:FaxNumber>4445558889</v2:FaxNumber>
</v2:Contact>
<v2:Address>
<v2:StreetLines>123 Main St.</v2:StreetLines>
<v2:City>Irving</v2:City>
<v2:StateOrProvinceCode>TX</v2:StateOrProvinceCode>
</v2:Address>

</v2:OrderContact>
<v2:DeliveryGroups>
<v2:DeliveryMethod>
<v2:DeliveryType>DIRECT_MAIL</v2:DeliveryType>
<v2:CenterId>0000</v2:CenterId>
<v2:OrderDirectMailDetail>
<v2:AddressCount>250</v2:AddressCount>
</v2:OrderDirectMailDetail>
<v2:PrintLineItems>
<v2:CatalogDocument>
<v2:Type>GLOBAL</v2:Type>
<v2:FolderPath>/ALL FOLDERS/abc</v2:FolderPath>
<v2:DocumentName>Sample Document</v2:DocumentName>
<v2:CustomizedSections>
</v2:CustomizedSections>
<v2:ProofType>DECLINED</v2:ProofType>
</v2:CatalogDocument>
<v2:Payor>
</v2:Payor>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples

Example 6
<soapenv:Header/>
<soapenv:Body>
<v2:UserCredential>
<v2:ClientDetail>
</v2:ClientDetail>
<v2:CustomerTransactionId>SystemRef</v2:CustomerTransactionId>
<v2:Version>
</v2:Version>
<v2:OrderContact>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
</v2:Address>
</v2:OrderContact>

<v2:DeliveryGroups>
<v2:DeliveryMethod>
<v2:OrderRecipient>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
</v2:Address>
<v2:Payor>
</v2:Payor>
<v2:ServiceType>FEDEX_GROUND</v2:ServiceType>
<v2:PrintLineItems>
<v2:Document>
<v2:Name>Sample Flyer</v2:Name>
<v2:Sections>

</v2:Sections>
</v2:Document>
<v2:PrintLineItems>
<v2:Document>
<v2:Name>Sample 2</v2:Name>
<v2:FinishingOptionTypes>DRILLING</v2:FinishingOptionTypes>
<v2:FinishingOptionTypes>INSERT</v2:FinishingOptionTypes>
<v2:DrillingDetail>
<v2:DrillingType>THREE_HOLE_SIDE</v2:DrillingType>
</v2:DrillingDetail>
<v2:InsertDetails>
<v2:SequenceNumber>1</v2:SequenceNumber>
<v2:PageNumber>2</v2:PageNumber>
<v2:MediaDescription>BRIGHT_BLUE</v2:MediaDescription>
<v2:TabDetail>
<v2:LabelLines>
<v2:LineNumber>1</v2:LineNumber>
<v2:Content>Tab Label line 1</v2:Content>
</v2:LabelLines>
<v2:Font>
<v2:Name>Arial</v2:Name>
<v2:Size>8</v2:Size>
<v2:Styles>BOLD</v2:Styles>
</v2:Font>
<v2:Orientation>LANDSCAPE</v2:Orientation>
</v2:TabDetail>
</v2:InsertDetails>
<v2:Sections>
<v2:MediaDescription>STANDARD_WHITE</v2:MediaDescription>
</v2:Sections>
</v2:Document>

<v2:PaymentType>CREDIT_CARD</v2:PaymentType>
<v2:CreditCard>
<v2:Number>111111111111111</v2:Number>
<v2:CreditCardType>AMEX</v2:CreditCardType>
<v2:ExpirationDate>2012</v2:ExpirationDate>
<v2:CreditCardHolder>
<v2:Contact>
<v2:PersonName>
</v2:PersonName>
</v2:Contact>
<v2:Address>
<v2:City>COLLIERVILLE</v2:City>
</v2:Address>
</v2:CreditCardHolder>
<v2:VerificationCode>2012</v2:VerificationCode>
</v2:CreditCard>
</soapenv:Body>
</soapenv:Envelope>
Back to Examples


Create Office Order Reply
Example 1
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<CreateOfficeOrderReply xmlns="http://fedex.com/ws/officeorder/v2">
<Notifications>
<Code>0000</Code>
</Notifications>
<TransactionDetail>

</CustomerTransactionId>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<CompletedOfficeOrder>
<OrderGlobalTrackingNumber>1111111111111111</OrderGlobalTrackingNumber>
<CompletedDeliveryGroupDetails>
<CompletedDocumentDetails>
<Name>Single Page Test Document.pdf</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>

</Amount>
</Costs>
<Discounts>
<Type>ACCOUNT</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
</CompletedDocumentDetails>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Amount>
</Amount>
</Discounts>
</Pricing>
<CompletedOrderPickupDetail>

<CenterName>Memphis TN Winchester Wincross
</CenterName>
<CenterAddress>
<StreetLines>7801 WINCHESTER RD</StreetLines>
<StreetLines>7801 WINCHESTER RD</StreetLines>
<City>Memphis</City>
<StateOrProvinceCode>TN </StateOrProvinceCode>
</CenterAddress>
<CenterPhone>(901) 755-6261</CenterPhone>
<CenterEmailAddress>usa1390@fedexoffice.com</CenterEMailAddress>
<DueDateTime>05/13/2009 11:00 AM</DueDateTime>
</CompletedOrderPickupDetail>
</CompletedDeliveryGroupDetails>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Amount>

</Amount>
</Discounts>
</Pricing>
</CompletedOfficeOrder>
</CreateOfficeOrderReply>
</SOAP-ENV:Body>
Back to Examples

Example 2
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<Notifications>
<Code>0000</Code>
</Notifications>
<TransactionDetail>

</CustomerTransactionId>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<Name>Test File.pdf</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>

<Amount>
</Amount>
</Discounts>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Type>HANDLING</Type>
<Amount>
</Amount>

</Costs>
<Costs>
<Type>SHIPPING</Type>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
<Discounts>
<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>

</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
<Discounts>
<Amount>
</Amount>
</Discounts>
</Pricing>
</SOAP-ENV:Body>
Back to Examples

Example 3
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<Notifications>
<Code>0000</Code>
</Notifications>
<TransactionDetail>
<CustomerTransactionId>SystemRef</CustomerTransactionId>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<Name>Sample Flyer</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>

<Name>Sample 2</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>

<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>

</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
</SOAP-ENV:Body>
Back to Examples

Example 4
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<Notifications>
<Code>0000</Code>
</Notifications>
<TransactionDetail>
<CustomerTransactionId>X0</CustomerTransactionId>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<Name>My Document</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>

<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>
</Pricing>
<CompletedOrderPickupDetail>
<CenterName>Germantown TN Poplar
Ave</CenterName>
<CenterAddress>
<StreetLines>9077 Poplar Ave</StreetLines>

<StreetLines>9077 Poplar Ave</StreetLines>
<City>Germantown</City>
<StateOrProvinceCode>TN</StateOrProvinceCode>
</CenterAddress>
<CenterPhone>(901) 755-0525</CenterPhone>
<CenterEmailAddress>
usa1641@fedex.com
</CenterEMailAddress>
<DueDateTime>05/14/2010 01:00
PM</DueDateTime>
</CompletedOrderPickupDetail>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>
<Type>VOLUME</Type>
<Amount>
</Amount>
</Discounts>

</Pricing>
</SOAP-ENV:Body>
Back to Examples

Example 5
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<Notifications>
<Code>0000</Code>
</Notifications>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<CompletedCatalogDocumentDetails>
<Type>GLOBAL</Type>
<FolderPath>/ALL FOLDERS/abc</FolderPath>
<DocumentName>Sample Document</DocumentName>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
<Discounts>

<Amount>
</Amount>
</Discounts>
</Pricing>
</CompletedCatalogDocumentDetails>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Type>POSTAGE</Type>
<Amount>
</Amount>
</Costs>
<Discounts>

<Amount>
</Amount>
</Discounts>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Type>POSTAGE</Type>
<Amount>
</Amount>
</Costs>

<Discounts>
<Amount>
</Amount>
</Discounts>
</Pricing>
</SOAP-ENV:Body>
Back to Examples

Example 6
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<Notifications>
<Code>0000</Code>
</Notifications>
<Version>
<Major>3</Major>
<Minor>0</Minor>
</Version>
<Name>Sample Flyer</Name>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
<Name>Sample 2</Name>

<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>

</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
<Pricing>
<TotalCost>
</TotalCost>
<TotalDiscount>
</TotalDiscount>
<NetCost>
</NetCost>
<Tax>
</Tax>
<NetPrice>
</NetPrice>
<Costs>
<Amount>
</Amount>
</Costs>
<Costs>
<Amount>

</Amount>
</Costs>
<Costs>
<Amount>
</Amount>
</Costs>
</Pricing>
</SOAP-ENV:Body>
Back to Examples


Email Confirmations
This section of the guide provides example email confirmation messages that are
generated by Office Order Service. These messages are sent to the email addresses in the
“Order Contact Email Address” and “Recipient Email Address” fields. Email notifications
can be deactivated using the “Order Confirmation Email Requested” field in the Requested
Office Order section in the Rate and Create Office Order service.
Example email text is provided for each of the following confirmation types:
• Order Confirmation Sent to Order Contact
Example: John Doe, an Instructional Design Specialist at ABC Company’s

central office in San Francisco, CA placed an order with FedEx Office
for multiple, bound copies of a training presentation he developed. As
part of his order, he requested that the order be produced at a FedEx
Office location in Cordova, TN so that the order could be picked up by
the course instructor, Jane Smith, once she arrived in town to conduct
training for Tennessee-based employees. This email serves as his
confirmation that the order has been received by FedEx Office.
• Special Instructions Next Steps Sent to Order Contact
Example: Jim Smith, a student at the local community college, submitted an

order to FedEx Office requesting that two copies of his research
project results be printed and placed in a binder. Jim included free-
form special instructions in his order explaining where he would like
a hard bound book cover instead of a regular binder to be added to
his order.
Immediately after placing the print order, Jim receives this email
reminding him that he must call the FedEx Office location that will be
producing his document to clarify and confirm his order before it can
be fulfilled. Special Instructions are used when requesting something
special to the order where code does not support the request. Once
special instructions are used, the order must be paid at time of
pickup.
• Order Confirmation Sent to Recipient
Example: Jane Smith, course instructor for ABC Company, is in route to

Cordova, TN to conduct training for Tennessee-based employees.
This email serves to advise her that her peer, John Doe, has placed
an order with FedEx Office to produce the training materials that she
will be using. This email tells Ms. Smith where to pick up the order
and when the order will be ready.

• Order Completion Notice Sent to Order Contact
Example: George Washington and his team in Philadelphia completed an important

document and placed an order with FedEx Office to have several copies
of the document produced and shipped FedEx Priority Overnight to a
remote team in Massachusetts headed by John Adams. This email
serves to advise Mr. Washington that the FedEx Office order has been
completed and shipped to Mr. Adams at his home in Braintree.
• Order Completion Notice Sent to Recipient
Example: John Adams, an important member of a document development

taskforce, is currently on a retreat with a number of his peers in Braintree,
MA. It is his understanding that the latest draft of a document that he has
been collaborating on with a team in Philadelphia has been sent to FedEx
Office for duplication. This email serves to advise Mr. Adams that the
order George Washington placed is complete and has been shipped to
Mr. Adams.

Order Confirmation Sent to Order Contact
From: no-reply.ecommerce@fedex.com
To: John Doe
Subject: FedEx Office order confirmation(GTN 1111111111111111)
## This is an automated response, please do not reply to this email ##
Dear John Doe,
Thank you for choosing FedEx Office. This email confirms that we have received your order. Please
retain this email for your records.
You are welcome to follow up with the center if you have any questions.
If you need to cancel this order, you must immediately call FedEx Office customer relations at
1.800.GoFedEx 1.800.463.3339. You can reference your order by Order Number 1111111111111111. Most
jobs go into production within 15 minutes of receipt. Orders cancelled after going into
production may be subject to a charge.
All jobs produced for customers will be retained for 30 days after the order ready by date on the
receipt at which time you will be charged for the completed job if you have not picked up the
order. FedEx Office is not responsible for retaining any work not picked up by customer after
such 30 day period and is entitled to collect and retain payment for all work performed on the
customer's behalf.
ORDER -- SUMMARY DETAILS
Order GTN number: 1111111111111111
Order Price
Subtotal: $xxx.xx
Shipping: $--
Tax: $xx.xx
Total: $xxxx.xx
Payment by: FedEx Account
See order details for each recipient below
ORDER_DETAIL -- Part 1
Job GTN number: 2222222222222222
FedEx Office center producing order:

1130 N Germantown Pkwy
CORDOVA, TN 38016-5893
UNITED STATES
Phone: (901) 752-0200
Email: usa0839@fedex.com
Order Completion Date: May 13, 2009 at 11:00 PM CDT
Documents:
Mid-South Sales Training Presentation.pdf (xx)
Mid-South Sales Training Presentation.pdf
Recipient: Smith, Jane
To be picked up at FedEx Office center (see above)
Price: $xxx.xx
Shipping Cost: $--
Tax: $xx.xx

Special Instructions Next Steps Sent to Order Contact
To: Jim Smith
Subject: Urgent - Next Steps to Complete your FedEx Office Order Number 1111111111111111)
Dear FedEx Office Customer,
Since your order contains special instructions, you will need to call the FedEx Office center
listed below to review your order, determine final pricing, and provide payment information
before it can be completed.
Here are the special instructions that you entered with your order:
Please add a black hard bound book cover instead of a regular binder to my document.
Please allow at least 30 minutes for the center to receive your order.
Memphis TN Germantown
6641 POPLAR AVE

GERMANTOWN, TN 38138
UNITED STATES
(901) 756-7603
Thank you,
FedEx Office

Order Confirmation Sent to Recipient
To: Jane Smith
Subject: FedEx Office order confirmation (GTN 2222222222222222)
Dear Jane Smith,
John Doe has sent a FedEx Office document order to you.
This order is made up of:

Mid-South Sales Training Presentation.pdf (xx)
Mid-South Sales Training Presentation.pdf
Job GTN number: 2222222222222222
The order will be ready for you to pick up on May 13, 2009 at 11:00 PM CDT
Please pick up the order at FedEx Office center located at:

1130 N Germantown Pkwy
CORDOVA, TN 38016-5893
UNITED STATES
Phone: (901) 752-0200
If you have questions concerning your order, please call the FedEx Office center and ask for the
Project Coordinator. You can reference your order by Job number 2222222222222222.
If you have any other questions, comments, or concerns regarding FedEx Office, please contact the
FedEx Office customer relations at 1.800.GoFedEx 1.800.463.3339.

Order Completion Notice Sent to Order Contact
To: George Washington
Subject: FedEx Office order completion(GTN 5555555555555555)
Dear George Washington,
Thank you for choosing FedEx Office. This mail confirms that we have completed your order and
delivered it based on your instructions.
If you have questions concerning your order, please call the FedEx Office center producing the
order and ask for the Project Coordinator. You can reference your order by Order number
5555555555555555.
If you have questions about this order or other comments or concerns regarding FedEx Office,
please contact FedEx Office customer relations at 1.800.GoFedEx 1.800.463.3339. You can reference
your order by Order number 5555555555555555.
ORDER -- SUMMARY DETAILS
Order GTN number: 5555555555555555
Order Price
Subtotal: $xxx.xx
Shipping: $xx.xx
Tax: $xx.xx
Total: $xxxx.xx
Payment by: FedEx Account
See order details for each recipient below
ORDER_DETAIL -- Part 1
Job GTN number: 6666666666666666
FedEx Office center producing order:

924 Chestnut St, Suite 32
PHILADELPHIA, PA 19107
UNITED STATES
Phone: (215) 925-2472
Order Completion Date: May 21, 2009 at 02:00 PM CDT

Documents:
Declaration of Independence Draft.pdf (xx)
Declaration of Independence Draft.pdf
Recipient: Adams, John
Shipping address:
123 Lost Lane Retreat
Third Floor
BRAINTREE, MA 02185
UNITED STATES
Delivery Method FedEx Priority Overnight
Price: $xxx.xx
Shipping Cost: $xx.xx *
Tax: $xx.xx
* Reflects Packing Fee only. Shipping will be billed separately to your FedEx account enabled
for Shipping.

Order Completion Notice Sent to Recipient
To: John Adams
Subject: FedEx Office order completion (GTN 6666666666666666)
Dear John Adams,
George Washington has sent a FedEx Office document order to you.
This order is made up of:

Declaration of Independence Draft.pdf (xx)
Declaration of Independence Draft.pdf
Job GTN number: 6666666666666666
FedEx Office shipped the order to you by FedEx Priority Overnight on May 21, 2009 at 02:00 PM CDT
If you have any questions about this order or other comments or concerns regarding FedEx Office,
please contact FedEx Office customer relations at 1.800.GoFedEx 1.800.463.3339.
You can reference your order by Job number 6666666666666666.


Notification Messages and Codes
This section details the possible reply notification messages and associated error codes.
Notification objects include severity, source, code, and message elements.
Severity Descriptions
There is a possibility of multiple Notification objects for a single request. The response
notification severity values of ERROR, FAILURE, and SUCCESS will never be combined in a
single response.
Value Definition
FAILURE Code/message explains that your request could not be handled at this time;
please do not resubmit right now.
ERROR Code/message identifies a problem with your request data; you may fix the
request data and try again. See Notification Codes.
WARNING Your request was successful. However, the code/message explains what had to
be done to fulfill your request; you may need to determine whether that is what
you intended, you may need to do this differently next time, or you may need to
prepare for a future change. Request was completed.
NOTE Your request was successful. However, the code/message contains additional
information about how your request was fulfilled; you do not need to take any
special action.
SUCCESS Your request was successful.


Notification Codes
Error conditions and the resulting Notification element values are noted below.
Code Source Severity Message

0000 oord SUCCESS Request was successful.
3001 oord NOTE Since your order contains special instructions, you will
need to call the FedEx Office {NAME} Center at
{PHONE} to finalize your order.
3002 oord NOTE Special character(s) was identified in
CUSTOMER_REFERENCE or P_O_NUMBER value.
The Special character(s) may be removed and there are
no changes to your transaction.
4001 oord ERROR Client product ID is required.
4002 oord ERROR Client product version is required.
4003 oord ERROR Integrator ID is required.
4007 oord ERROR Application ID is required.
4013 oord ERROR Authorization failed.
4014 oord ERROR Integration has been de-activated for this client and
integrator.
4019 oord ERROR The Integrator ID value is not recognized.
4020 oord ERROR Order contact first name is required.
4021 oord ERROR Order contact first name may be no longer than 40
characters.
4022 oord ERROR Order contact last name is required.
4023 oord ERROR Order contact last name may be no longer than 40
characters.
4024 oord ERROR Order contact company name may be no longer than 80
characters.
4025 oord ERROR Order contact address line is required.
4026 oord ERROR Order contact address line may be no longer than 80
characters.
4027 oord ERROR Order contact city is required.
4028 oord ERROR Order contact city may be no longer than 40 characters.
4029 oord ERROR Order contact state/province is required.
4030 oord ERROR Order contact state/province is not recognized.
4031 oord ERROR Order contact postal code is required.
4032 oord ERROR Order contact postal code may be no longer than 15
characters.
4033 oord ERROR Order contact country is required.
4034 oord ERROR Order contact country is not recognized.
4035 oord ERROR Order contact phone number is required.
4036 oord ERROR Order contact phone number must contain 10 digits.
4037 oord ERROR Order contact email address is required.
4038 oord ERROR Order contact email address may be no longer than 80
characters.

4039 oord ERROR Number of copies for Document {DOC_NUMBER} must
be between 1 and 999999.
4041 oord ERROR Document name for Document {DOC_NUMBER} may
be no longer than 500 characters.
4042 oord ERROR Finishing option type value for Document
{DOC_NUMBER} is not recognized.
4043 oord ERROR Printing charges payment type is required.
4044 oord ERROR Document {DOC_NUMBER} includes stapling
information but stapling was not requested.
4045 oord ERROR Document {DOC_NUMBER} includes drilling
information but drilling was not requested.
4046 oord ERROR Document {DOC_NUMBER} includes cutting
information but cutting was not requested.
4047 oord ERROR Folding text position for Document {DOC_NUMBER} is
not recognized.
4048 oord ERROR Folding type for Document {DOC_NUMBER} is not
recognized.
4049 oord ERROR Stapling type is required for Document
{DOC_NUMBER} since stapling is requested.
4050 oord ERROR Stapling type for Document {DOC_NUMBER} is not
recognized.
4051 oord ERROR Drilling type is required for Document {DOC_NUMBER}
since drilling is requested.
4052 oord ERROR Drilling type for Document {DOC_NUMBER} is not
recognized.
4053 oord ERROR Document {DOC_NUMBER} includes binding
information but binding was not requested.
4054 oord ERROR Cutting type is required for Document {DOC_NUMBER}
since cutting is requested.
4055 oord ERROR Document {DOC_NUMBER} includes binder information
but binder was not requested.
4056 oord ERROR Binding type is required for Document {DOC_NUMBER}
since binding is requested.
4057 oord ERROR Binding type for Document {DOC_NUMBER} is not
recognized.
4058 oord ERROR First page as cover can only be supported for
Document {DOC_NUMBER} with binding.
4059 oord ERROR Front cover can only be supported for Document
{DOC_NUMBER} with binding.
4060 oord ERROR Back cover can only be supported for Document
{DOC_NUMBER} with binding.
4061 oord ERROR Document {DOC_NUMBER} includes front cover
information but front cover was not requested.
4062 oord ERROR Document {DOC_NUMBER} includes back cover
information but back cover was not requested.
4063 oord ERROR Cutting type for Document {DOC_NUMBER} is not
recognized.

4064 oord ERROR Binder color is required for Document {DOC_NUMBER}
since binder is requested.
4065 oord ERROR Binder color for Document {DOC_NUMBER} is not
recognized.
4066 oord ERROR Binder size is required for Document {DOC_NUMBER}
4067 oord ERROR Binder size for Document {DOC_NUMBER} is not
recognized.
4068 oord ERROR Selected media category for Document
{DOC_NUMBER} requires a {MIN_COPIES}-copy
minimum.
4069 oord ERROR {ARRAY_NAME} has a limit of {LIMIT} elements.
4070 oord ERROR Upload session ID is required for Section
{SECTION_NUMBER} of Document {DOC_NUMBER}.
4071 oord ERROR File token for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} is required.
4073 oord ERROR Print type for Section {SECTION_NUMBER} of
4074 oord ERROR Number of sides for Section {SECTION_NUMBER} of
4075 oord ERROR Pickup delivery group includes shipping information.
4076 oord ERROR Shipment delivery group includes pickup information.
4077 oord ERROR Delivery type is required for all delivery groups.
4078 oord ERROR Delivery type value is not recognized.
4079 oord ERROR Either center ID or location search criteria are required
for the pickup delivery group.
4080 oord ERROR City must be specified with state in the location search
criteria in the pickup delivery group.
4081 oord ERROR Location search criteria are not allowed in the pickup
delivery group since center ID is specified.
4082 oord ERROR Order contact fax number must contain 10 digits.
4083 oord ERROR Order contact email address is not valid.
4084 oord ERROR At least one order notification CC email address is not
valid.
4085 oord ERROR At least one order notification BCC email address is not
valid.
4086 oord ERROR Type is required when specifying a customer reference.
4087 oord ERROR Customer reference type is not recognized.
4088 oord ERROR Value is required when specifying a customer
reference.
4089 oord ERROR Customer reference value may be no longer than 30
characters.
4090 oord ERROR State/province in location search criteria for the pickup
delivery group is not recognized.
4091 oord ERROR Country in location search criteria for the pickup
delivery group is not recognized.

4092 oord ERROR Country must be specified in location search criteria for
the pickup delivery group.
4093 oord ERROR Location search criteria for the pickup delivery group
may specify postal code or city/state but not both.
4095 oord ERROR Due date and time for the pickup delivery group have
already passed.
4096 oord ERROR Due date and time for the pickup delivery group is more
than 10 days in the future.
4097 oord ERROR Due date and time for the pickup delivery group is not
valid.
4098 oord ERROR Rate cannot be provided for the order since Document
{DOC_NUMBER} contains special instructions.
4099 oord ERROR FedEx account number for the shipment delivery group
is not recognized.
4101 oord ERROR Service type is required for the shipment delivery group.
4102 oord ERROR Service type for the shipment delivery group is not
recognized.
4103 oord ERROR Recipient first name is required for a pickup or shipment
delivery group.
4104 oord ERROR Recipient first name may be no longer than 40
characters for a pickup or shipment delivery group.
4105 oord ERROR Recipient last name is required for a pickup or shipment
delivery group.
4106 oord ERROR Recipient last name may be no longer than 40
4107 oord ERROR Recipient company name may be no longer than 80
4108 oord ERROR Recipient address line is required for the shipment
delivery group.
4109 oord ERROR Recipient address line for the shipment delivery group
may be no longer than 80 characters.
4110 oord ERROR Recipient city is required for the shipment delivery
group.
4111 oord ERROR Recipient city for the shipment delivery group may be
no longer than 40 characters.
4112 oord ERROR Recipient state/province is required for the shipment
delivery group.
4113 oord ERROR Recipient state/province for the shipment delivery group
is not recognized.
4114 oord ERROR Recipient postal code is required for the shipment
delivery group.
4115 oord ERROR Recipient postal code for the shipment delivery group
4116 oord ERROR Recipient country is required for the shipment delivery
group.

4117 oord ERROR Recipient country for the shipment delivery group is not
recognized.
4118 oord ERROR Recipient phone number is required for a pickup or
shipment delivery group.
4119 oord ERROR Recipient phone number must contain 10 digits for a
pickup or shipment delivery group.
4120 oord ERROR Recipient email address may be no longer than 80
4121 oord ERROR Upload session ID for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} may be no longer than 256
characters.
4122 oord ERROR File token for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} may be no longer than 256
characters.
4123 oord ERROR FedEx account number is required.
4124 oord ERROR FedEx account number is not recognized.
4125 oord ERROR FedEx account number is not valid.
4126 oord ERROR Printing charges payment type is not recognized.
4127 oord ERROR Front cover media category must be specified with front
cover media description for Document
{DOC_NUMBER}.
4128 oord ERROR Front cover media category for Document
4129 oord ERROR Front cover media description for Document
4130 oord ERROR Back cover media category must be specified with back
cover media description for Document
{DOC_NUMBER}.
4131 oord ERROR Back cover media category for Document
4132 oord ERROR Back cover media description for Document
4133 oord ERROR Media category for Section {SECTION_NUMBER} of
4134 oord ERROR Media category for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} is not recognized.
4135 oord ERROR Media description for Section {SECTION_NUMBER} of
4136 oord ERROR Media description for Section {SECTION_NUMBER} of
4137 oord ERROR Account type is required for printing charges payment.
4138 oord ERROR Document {DOC_NUMBER} includes folding
information but folding was not requested.
4139 oord ERROR Folding type is required for Document {DOC_NUMBER}
since folding is requested.
4140 oord ERROR File type for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} is not supported.

4141 oord ERROR File in Section {SECTION_NUMBER} of Document
{DOC_NUMBER} does not exist or has expired.
4142 oord ERROR File format for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} is not valid.
4143 oord ERROR The length of all CC email addresses (when combined
into a single comma-separated string) may not exceed
1000 characters.
4145 oord ERROR The length of all BCC email addresses (when combined
into a single comma-separated string) may not exceed
1000 characters.
4146 oord ERROR Three-hole drilling must be specified for Document
{DOC_NUMBER} since binder option is selected.
4147 oord ERROR Collation is required for Document {DOC_NUMBER} to
be in a binder.
4149 oord ERROR Binder is not available for the Section
{SECTION_NUMBER} media category in Document
{DOC_NUMBER}.
4150 oord ERROR Binder is not available for Document {DOC_NUMBER}
since it is a single-page document.
4151 oord ERROR Binder and binding are not both allowed on Document
{DOC_NUMBER}.
4152 oord ERROR Presentation instructions detail is required for Section
{SECTION_NUMBER} of Document {DOC_NUMBER}
since section is based on a presentation file.
4153 oord ERROR Binder and folding are not both allowed on Document
{DOC_NUMBER}.
4154 oord ERROR Binder and lamination are not both allowed on
Document {DOC_NUMBER}.
4155 oord ERROR Binder and stapling are not both allowed on Document
{DOC_NUMBER}.
4156 oord ERROR Binder is not available for the Section
{SECTION_NUMBER} media size in Document
{DOC_NUMBER}.
be bound.
4160 oord ERROR Number of sides is required for Section
4161 oord ERROR Binding is not available for the Section
{DOC_NUMBER}.
4162 oord ERROR Binding is not available for Document {DOC_NUMBER}
since cutting is requested.

4164 oord ERROR Quarter cutting is not available for the Section
{DOC_NUMBER}.
4165 oord ERROR Binding and drilling are not both allowed on Document
{DOC_NUMBER}.
4166 oord ERROR Binding and folding are not both allowed on Document
{DOC_NUMBER}.
4167 oord ERROR Binding and lamination are not both allowed on
4168 oord ERROR Binding and stapling are not both allowed on Document
{DOC_NUMBER}.
4169 oord ERROR Binding is not available for the Section
{DOC_NUMBER}.
4170 oord ERROR Binder and cutting are not both allowed on Document
{DOC_NUMBER}.
4171 oord ERROR Binding and cutting are not both allowed on Document
{DOC_NUMBER}.
4172 oord ERROR Cutting and drilling are not both allowed on Document
{DOC_NUMBER}.
4173 oord ERROR Cutting and folding are not both allowed on Document
{DOC_NUMBER}.
4174 oord ERROR Cutting and lamination are not both allowed on
4175 oord ERROR Cutting and stapling are not both allowed on Document
{DOC_NUMBER}.
4176 oord ERROR Cutting and tabs are not both allowed on Document
{DOC_NUMBER}.
4177 oord ERROR Cutting is not available for the Section
{DOC_NUMBER}.
{DOC_NUMBER}.
{SECTION_NUMBER} media type in Document
{DOC_NUMBER}.
4180 oord ERROR Cutting is not available for Document {DOC_NUMBER}
since it is a multiple-page document.
4181 oord ERROR Drilling is not available for the Section
{DOC_NUMBER}.
4182 oord ERROR Three-hole drilling is not available for the Section
{DOC_NUMBER}.
4183 oord ERROR Two-hole drilling is not available for Document
{DOC_NUMBER} since no sections have a letter or
legal media size.

4185 oord ERROR Drilling and folding are not both allowed on Document
{DOC_NUMBER}.
4186 oord ERROR Drilling and lamination are not both allowed on
4187 oord ERROR Drilling and stapling are not both allowed on Document
{DOC_NUMBER}.
4191 oord ERROR Folding cannot be supported for Document
{DOC_NUMBER} since it has more than
{THRESHOLD} pages.
4192 oord ERROR Folding text position is not applicable to Document
{DOC_NUMBER} since Z-folding was requested.
4193 oord ERROR Folding is not available for the Section
{DOC_NUMBER}.
4195 oord ERROR Proof type for Document {DOC_NUMBER} is not
recognized.
4196 oord ERROR Folding text position is not applicable to Document
{DOC_NUMBER} since it has multiple pages and
double-folding was requested.
4197 oord ERROR Third cutting is not available for the Section
{DOC_NUMBER}.
4198 oord ERROR Media size must be specified for Section
since it contains pages of different sizes.
4199 oord ERROR Folding and lamination are not both allowed on
4200 oord ERROR Folding and stapling are not both allowed on Document
{DOC_NUMBER}.
4201 oord ERROR Folding and tabs are not both allowed on Document
{DOC_NUMBER}.
4202 oord ERROR Inserts are not available for the Section
{DOC_NUMBER}.
4203 oord ERROR Inserts are not available for the Section
{DOC_NUMBER}.
4204 oord ERROR COVER is not a valid media category for Section
4205 oord ERROR Lamination is not available for the Section
{DOC_NUMBER}.
4212 oord ERROR Lamination and tabs are not both allowed on Document
{DOC_NUMBER}.
4213 oord ERROR Double-sided printing is not available for the Section
{DOC_NUMBER}.

4214 oord ERROR Double-sided printing is not available for Section
since it only has one page.
4215 oord ERROR Tab position in Section {SECTION_NUMBER} of
Document {DOC_NUMBER} is invalid with double-sided
printing.
be stapled.
4217 oord ERROR Stapling cannot be supported for Document
{DOC_NUMBER} since it has more than
{THRESHOLD} pages.
4218 oord ERROR Stapling is not available for the Section
{DOC_NUMBER}.
4219 oord ERROR Stapling is not available for Document {DOC_NUMBER}
4220 oord ERROR Stapling and tabs are not both allowed on Document
{DOC_NUMBER}.
4221 oord ERROR Multiple-page documents are not allowed for the
Section {SECTION_NUMBER} media category in
4222 oord ERROR Lamination and stapling are not both allowed on
4223 oord ERROR The binder size for Document {DOC_NUMBER} is not
available in the selected binder color.
4224 oord ERROR Document {DOC_NUMBER} has more pages than the
binder's capacity ({THRESHOLD} pages).
4225 oord ERROR Document {DOC_NUMBER} has more pages than the
binding's capacity ({THRESHOLD} pages).
4226 oord ERROR {MISSING_OBJECT} is required.
4227 oord ERROR Two-hole drilling and tabs are not both allowed on
4228 oord ERROR Either binding or three-hole drilling are required for
Document {DOC_NUMBER} since it contains tabs.
4229 oord ERROR Collation is required for Document {DOC_NUMBER}
since it contains tabs.
4234 oord ERROR Tabs are not available for the Section
{DOC_NUMBER}.
4235 oord ERROR Order contact postal code is not valid.
4236 oord ERROR Daily limit for certification transactions has been
reached.
4237 oord ERROR Center ID {CENTER_ID} is not a retail location.
4238 oord ERROR Center ID {CENTER_ID} is unable to accept this order.
4242 oord ERROR Center ID {CENTER_ID} is not recognized.

4243 oord ERROR No print centers were found near the location for the
pickup delivery group.
4244 oord ERROR Tabs are not available for the Section
{DOC_NUMBER}.
4245 oord ERROR No print centers are available to produce the order near
the location for the pickup delivery group.
4246 oord ERROR Center ID {CENTER_ID} is not a United States location.
4247 oord ERROR Discounts are only allowed with the specified FedEx
account when it is used as the payment method.
4248 oord ERROR Discount code could not be authenticated.
4249 oord ERROR Items in the pickup delivery group cannot be completed
until {EARLIEST_DATE}.
4250 oord ERROR The specified FedEx account may only be used for print
discount purposes and not for payment.
4251 oord ERROR FedEx account number is invalid.
4252 oord ERROR Discount code is not valid.
4253 oord ERROR Discount code is not recognized.
4254 oord ERROR A separate discount code is not allowed when paying by
FedEx account number.
4255 oord ERROR Location search criteria address line for the pickup
delivery group may be no longer than 70 characters.
4256 oord ERROR Location search criteria city for the pickup delivery
group may be no longer than 30 characters.
4257 oord ERROR Location search criteria postal code for the pickup
delivery group may be no longer than 15 characters.
4258 oord ERROR FedEx account number could not be authenticated.
4259 oord ERROR A PO number is required for this FedEx account
number.
4260 oord ERROR The FedEx account number is not valid.
4261 oord ERROR The FedEx service type cannot be used for the
destination address provided.
4262 oord ERROR Unable to create a FedEx shipment for this order.
4264 oord ERROR The Section {SECTION_NUMBER} media
category/description in Document {DOC_NUMBER} is
not available in this size.
4265 oord ERROR Black and white printing is not available for the Section
{DOC_NUMBER}.
4266 oord ERROR Color printing is not available for the Section
{DOC_NUMBER}.
4269 oord ERROR Printing charges payment account type is not
recognized.
4270 oord ERROR Print type for Section {SECTION_NUMBER} of

4271 oord ERROR Number of sides for Section {SECTION_NUMBER} of
4274 oord ERROR Recipient email address is not valid.
4275 oord ERROR Media size for Section {SECTION_NUMBER} of
4280 oord ERROR Delivery group name may be no longer than 500
characters.
4281 oord ERROR Delivery group description may be no longer than 500
characters.
4282 oord ERROR Recipient email address is required for the pickup
delivery group.
4283 oord ERROR Center ID may not be longer than four characters for
any delivery group.
4284 oord ERROR Center ID may only consist of numeric characters.
4285 oord ERROR Payment type for the shipment delivery group is
required when specifying shipping payment information.
4286 oord ERROR Payment type for the shipment delivery group is not
recognized.
4287 oord ERROR FedEx account number is required for the shipment
delivery group when specifying shipping payment
information.
4288 oord ERROR Recipient postal code for the shipment delivery group is
not valid.
4289 oord ERROR Postal code in location search criteria for the pickup
delivery group is not valid.
4290 oord ERROR The Section {SECTION_NUMBER} media description in
Document {DOC_NUMBER} is invalid for its media
category.
4291 oord ERROR The front cover media description for Document
{DOC_NUMBER} is invalid for its media category.
4292 oord ERROR The back cover media description for Document
{DOC_NUMBER} is invalid for its media category.
4293 oord ERROR The front cover media category for Document
{DOC_NUMBER} is not valid.
4294 oord ERROR The back cover media category for Document
{DOC_NUMBER} is not valid.
4295 oord ERROR First page as cover is not supported for the front cover
media category in Document {DOC_NUMBER}.
4296 oord ERROR First page as cover can only be supported for
Document {DOC_NUMBER} with front cover.
4297 oord ERROR Folding text position is required for Document
{DOC_NUMBER} since single-folding was requested.
4298 oord ERROR Folding text position is required for Document
{DOC_NUMBER} since it has a single page and double-
folding was requested.
4299 oord ERROR Document {DOC_NUMBER} contains a special
instructions value longer than 2000 characters.

4300 oord ERROR Document {DOC_NUMBER} includes special
instructions information but special instructions were not
requested as a document option.
4301 oord ERROR Special instructions are required for Document
{DOC_NUMBER} since special instructions type is
{TYPE}.
4302 oord ERROR Length for Section {SECTION_NUMBER} of Document
{DOC_NUMBER} must be between 0.01 and 120.
4303 oord ERROR At least one CC email address was specified but order
confirmation and completion emails were not requested.
4304 oord ERROR At least one BCC email address was specified but order
confirmation and completion emails were not requested.
4305 oord ERROR Width for Section {SECTION_NUMBER} of Document
{DOC_NUMBER} must be between 0.01 and 72.
4306 oord ERROR Order confirmation email must be requested when
special instructions are requested as a document
option.
4307 oord ERROR Presentation output option value for Section
is not recognized.
4308 oord ERROR Unit of measure is required for Section
since custom media dimensions are requested.
4309 oord ERROR Unit of measure for Section {SECTION_NUMBER} of
4310 oord ERROR Section {SECTION_NUMBER} of Document
{DOC_NUMBER} includes custom media dimensions
but custom media size was not requested.
4311 oord ERROR Special instructions must be requested as a document
option for Document {DOC_NUMBER} since a custom
media size is requested for Section
{SECTION_NUMBER}.
4312 oord ERROR Credit card number is required.
4313 oord ERROR Credit card number is not recognized.
4314 oord ERROR Credit card number is not valid.
4315 oord ERROR Credit card type is required.
4316 oord ERROR Credit card type is not recognized.
4317 oord ERROR Credit card expiration date is required.
4318 oord ERROR Credit card expiration date is not recognized.
4319 oord ERROR Credit card expiration date must be in the format
YYMM, YYYYMM, or YYYYMMDD.
4320 oord ERROR Credit card expiration date is not a valid date.
4323 oord ERROR Credit card holder first name is required.
4324 oord ERROR Credit card holder first name may be no longer than 40
characters.

4325 oord ERROR Credit card holder last name is required.
4326 oord ERROR Credit card holder last name may be no longer than 40
characters.
4327 oord ERROR Credit card holder phone number is required.
4328 oord ERROR Credit card holder phone number must contain 10
digits.
4329 oord ERROR Credit card holder address line is required.
4330 oord ERROR Credit card holder address line may be no longer than
80 characters.
4331 oord ERROR Credit card holder city is required.
4332 oord ERROR Credit card holder city may be no longer than 40
characters.
4333 oord ERROR Credit card holder state/province is required.
4334 oord ERROR Credit card holder state/province is not recognized.
4335 oord ERROR Credit card holder postal code is required.
4336 oord ERROR Credit card holder postal code may be no longer than
15 characters.
4337 oord ERROR Credit card holder postal code is not valid.
4338 oord ERROR Credit card holder country is required.
4339 oord ERROR Credit card holder country is not recognized.
4340 oord ERROR Order includes FedEx account information but it was not
specified as the payment type.
4341 oord ERROR Order includes credit card information but it was not
4342 oord ERROR Document proof must be declined for Document
{DOC_NUMBER} since it contains the file type in
Section {SECTION_NUMBER}.
4343 oord ERROR Credit card holder company name may be no longer
than 80 characters.
option for Document {DOC_NUMBER} since the
document includes the file type in Section
{SECTION_NUMBER}.
{DOC_NUMBER} since it contains the file type in
Section {SECTION_NUMBER}.
option for Document {DOC_NUMBER} since a custom
media size is requested for Section
{SECTION_NUMBER}.
{DOC_NUMBER} since the media size requested for
Section {SECTION_NUMBER} is different from the
source file's.
source file's.

source file's.
4350 oord ERROR Documents {DOC_NUMBER_1} and
{DOC_NUMBER_2} are identical and part of the same
delivery group. Please increase the number of copies
and delete the duplicate document.
source file's.
4352 oord ERROR Media category and media description are required for
Section {SECTION_NUMBER} of Document
{DOC_NUMBER} since binder is requested.
since binding is requested.
{DOC_NUMBER} since binding is requested.
{DOC_NUMBER} since print type is specified.
4356 oord ERROR Media size is required for Section
since print type is specified.
4357 oord ERROR Standard media dimensions (letter, legal, or tabloid)
may not be requested as a custom media size for
{DOC_NUMBER}.
since print type is specified.
4359 oord ERROR First page as cover is not supported for the front cover
media category in Document {DOC_NUMBER} since
color printing is requested.
Section {SECTION_NUMBER} of {DOC_NUMBER}
since folding is requested.
{SECTION_NUMBER} of {DOC_NUMBER} since
folding is requested.
{DOC_NUMBER} since number of sides is specified.

4363 oord ERROR Media size is required for Section
since number of sides is specified.
{DOC_NUMBER} includes presentation information but
section is not based on a presentation file.
4365 oord ERROR Print type is required for Section {SECTION_NUMBER}
of Document {DOC_NUMBER} since number of sides is
specified.
since stapling is requested.
4368 oord ERROR Print type is required for Section {SECTION_NUMBER}
of Document {DOC_NUMBER} since stapling is
requested.
4369 oord ERROR Either center ID or location search criteria are required
for the pickup delivery group.
4370 oord ERROR Shipment detail is required for the shipment delivery
group.
4371 oord ERROR Document option type value for Document
4372 oord ERROR Special instructions detail is required for Document
{DOC_NUMBER} since special instructions are
4373 oord ERROR Special instructions type is required for Document
{DOC_NUMBER} since special instructions are
4374 oord ERROR Special instructions type for Document
4375 oord ERROR FedEx account information is required when FedEx
account is specified as the payment type.
4376 oord ERROR Credit card information is required when credit card is
4377 oord ERROR Document section option type value for Section
is not recognized.
4378 oord ERROR Presentation instructions detail is required for Section
since presentation output is requested as a document
section option.
{DOC_NUMBER} includes presentation information but
presentation output was not requested as a document
section option.

4380 oord ERROR Presentation output type is required for Section
section option.
4381 oord ERROR Presentation output type for Section
is not recognized.
4382 oord ERROR Handout detail is required for Section
since the presentation output type is handouts.
{DOC_NUMBER} includes presentation handout
information but the presentation output type is not
handouts.
4384 oord ERROR Layout is required for Section {SECTION_NUMBER} of
Document {DOC_NUMBER} since presentation output
is requested as a document section option.
4385 oord ERROR Layout for Section {SECTION_NUMBER} of Document
4386 oord ERROR Slide order is required for Section
section option.
4387 oord ERROR Slide order for Section {SECTION_NUMBER} of
4389 oord ERROR Stapling detail is required for Document
4390 oord ERROR Drilling detail is required for Document
{DOC_NUMBER} since drilling is requested.
4391 oord ERROR Cutting detail is required for Document
{DOC_NUMBER} since cutting is requested.
4392 oord ERROR Folding detail is required for Document
{DOC_NUMBER} since folding is requested.
4393 oord ERROR Binding detail is required for Document
{DOC_NUMBER} since binding is requested.
4394 oord ERROR Front cover media detail is required for Document
{DOC_NUMBER} since front cover is requested.
4395 oord ERROR Back cover media detail is required for Document
{DOC_NUMBER} since back cover is requested.
4396 oord ERROR Binder detail is required for Document {DOC_NUMBER}
4398 oord ERROR Section media detail is required for Section
since special instructions are not requested as a
document option.
4400 oord ERROR Finishing option type values for Document
{DOC_NUMBER} are repeated.

4401 oord ERROR Recipient address is required for the shipment delivery
group.
4402 oord ERROR Media size may not be specified for front cover in
4403 oord ERROR Media dimensions may not be specified for front cover
in Document {DOC_NUMBER}.
4404 oord ERROR Media size may not be specified for back cover in
4405 oord ERROR Media dimensions may not be specified for back cover
in Document {DOC_NUMBER}.
4406 oord ERROR Credit card could not be authorized.
4407 oord ERROR Document name is required for Document
{DOC_NUMBER} since it contains more than one
section.
4408 oord ERROR Section numbers are required in Document
section.
4409 oord ERROR Section numbers in Document {DOC_NUMBER} must
be sequential and start at 1.
4410 oord ERROR Media dimensions are required for Section
since a custom media size was requested.
4411 oord ERROR Document numbers are required since the order
contains more than one document.
4412 oord ERROR Document numbers may not be repeated.
4413 oord ERROR Document numbers must be sequential and start at 1.
4414 oord ERROR Document {DOC_NUMBER} has the same document
name as another document.
4415 oord ERROR Document name is required for each requested
document since the order contains more than one.
4416 oord ERROR Section numbers may not be repeated within Document
{DOC_NUMBER}.
4424 oord ERROR Recipient address information may not be specified for
the pickup delivery group.
{DOC_NUMBER} includes a file whose name is longer
than 100 characters.
4426 oord ERROR Document {DOC_NUMBER} includes lamination
information but lamination was not requested.
4427 oord ERROR Lamination border for Document {DOC_NUMBER} is
not recognized.
4428 oord ERROR Lamination is not available for Document
{DOC_NUMBER} since it is a multiple-page document.
4429 oord ERROR Promotion code is invalid.
4430 oord ERROR Promotion code is invalid.
4431 oord ERROR Promotional discount exceeds total order cost.
4432 oord ERROR Total order cost does not qualify for promotion.

4433 oord ERROR The Section {SECTION_NUMBER} media description in
Document {DOC_NUMBER} is no longer available.
4434 oord ERROR The Section {SECTION_NUMBER} media.
category/description in Document {DOC_NUMBER} is
no longer available.
4435 oord ERROR The front cover media description for Document
{DOC_NUMBER} is no longer available.
4436 oord ERROR The back cover media description for Document
{DOC_NUMBER} is no longer available.
4437 oord ERROR User ID is required when user detail is specified.
4438 oord ERROR Customer configuration profile name is required when
user detail is specified.
4440 oord ERROR Customer configuration profile name is required for
catalog documents.
4441 oord ERROR Only one direct mail delivery group is allowed per order.
4442 oord ERROR Only one pickup delivery group is allowed per order.
4443 oord ERROR Only one shipment delivery group is allowed per order.
4444 oord ERROR Pickup and shipment are not supported within the same
order.
4448 oord ERROR Each print line item must contain either a requested
document or a requested catalog document.
4449 oord ERROR One print line item may not contain both a requested
document and a requested catalog document.
4450 oord ERROR Customer configuration profile name is required when
direct mail is requested.
4451 oord ERROR Direct mail detail is required for the direct mail delivery
group.
4452 oord ERROR Direct mail delivery group includes pickup information.
4453 oord ERROR Direct mail delivery group includes shipment
information.
4454 oord ERROR Recipient information may not be specified for the direct
mail delivery group.
4455 oord ERROR Upload session ID is required for the direct mail
recipient address file in the direct mail delivery group.
4456 oord ERROR Upload session ID for the direct mail recipient address
file in the direct mail delivery group may be no longer
than 256 characters.
4457 oord ERROR File token is required for the direct mail recipient
address file in the direct mail delivery group.
4458 oord ERROR File token for the direct mail recipient address file in the
direct mail delivery group may be no longer than 256
characters.

4459 oord ERROR Address count is required for the direct mail delivery
group.
4460 oord ERROR Pickup delivery group includes direct mail information.
4461 oord ERROR Shipment delivery group includes direct mail
information.
4462 oord ERROR Recipient information is required for the pickup delivery
group.
4463 oord ERROR Recipient information is required for the shipment
delivery group.
4465 oord ERROR Type is required for Document {DOC_NUMBER}.
4466 oord ERROR Type for Document {DOC_NUMBER} is not recognized.
4467 oord ERROR Folder path is required for Document {DOC_NUMBER}.
4468 oord ERROR Document name is required for Document
{DOC_NUMBER}.
4470 oord ERROR Customized section numbers are required in Document
customized section.
4471 oord ERROR Customized section numbers may not be repeated
within Document {DOC_NUMBER}.
4473 oord ERROR Upload session ID is required for Customized Section
4474 oord ERROR Upload session ID for Customized Section
4475 oord ERROR File token is required for Customized Section
4476 oord ERROR File token for Customized Section
4477 oord ERROR Direct mail recipient address file for the direct mail
delivery group does not exist or has expired.
4478 oord ERROR Customized Section {SECTION_NUMBER} of
Document {DOC_NUMBER} includes a file whose
name is longer than 100 characters.
4479 oord ERROR Customized Section {SECTION_NUMBER} of
Document {DOC_NUMBER} includes a file whose type
is not PDF.
4480 oord ERROR File in Customized Section {SECTION_NUMBER} of
Document {DOC_NUMBER} does not exist or has
expired.
4481 oord ERROR Delivery group names are required since the order
contains more than one.

4482 oord ERROR Center ID for the {DELIVERY_GROUP_NAME}delivery
group is not authorized for the customer configuration
profile.
4483 oord ERROR Delivery type for the {DELIVERY_GROUP_NAME}
delivery group is not authorized for the customer
4484 oord ERROR Customer configuration profile name is not recognized.
4485 oord ERROR User ID/password is not recognized.
4487 oord ERROR Password is required when user detail is specified.
4488 oord ERROR Document {DOC_NUMBER} is not recognized.
4490 oord ERROR Uploaded file could not be found for one or more
sections of Document {DOC_NUMBER}.
4491 oord ERROR File upload is not allowed for Section
4492 oord ERROR Credit card payment cannot be accepted for this order
since it will be produced at multiple locations.
4493 oord ERROR Center ID {CENTER_ID} is not available to produce the
items.
4494 oord ERROR User detail is required when customer configuration
profile name is specified.
4495 oord ERROR Direct mail recipient address file does not match the
address count for the direct mail delivery group.
4496 oord ERROR Uploaded file(s) for the catalog document customized
section(s) is not consistent with the document metrics
stored in the catalog.
4497 oord ERROR Uploaded file(s) for the catalog document customized
section(s) is not valid.
4498 oord ERROR Direct mail recipient address file for the direct mail
delivery group is not valid.
4499 oord ERROR Total document weight for the direct mail delivery group
may not exceed 13 ounces.
4500 oord ERROR Only catalog documents are authorized for the
customer configuration profile.
4501 oord ERROR Global catalog documents are not authorized for the
4502 oord ERROR Personal catalog documents are not authorized for the
4503 oord ERROR Personal catalog documents are not currently
supported.
4504 oord ERROR Only one Local Delivery delivery group is allowed per
order.

4505 oord ERROR Pickup and Local Delivery are not supported within the
same order.
4506 oord ERROR Shipment and Local Delivery are not supported within
the same order.
4507 oord ERROR Phone Number Extension may only consist of numeric
characters.
4508 oord ERROR Phone Number Extension may only consist of 8 numeric
characters.
4509 oord ERROR Direct Mail delivery group contains Local Delivery
information.
4510 oord ERROR Pickup delivery group contains Local Delivery
information.
4511 oord ERROR Local Delivery detail is required for the local delivery
group.
4512 oord ERROR Local Delivery delivery group contains Direct Mail
information.
4513 oord ERROR Local Delivery delivery group contains Pickup
information.
4514 oord ERROR Local Delivery delivery group contains Shipment
information.
4515 oord ERROR Order Recipient is required for a Local Delivery delivery
group.
4516 oord ERROR Order Recipient Address is required for a Local Delivery
delivery group.
4517 oord ERROR Recipient Address must contain at least one value for
Street Line for a Local Delivery delivery group.
4518 oord ERROR Recipient Address Street Line may be no longer than 80
characters for a Local Delivery delivery group.
4519 oord ERROR Recipient City is required for the Local Delivery delivery
group.
4520 oord ERROR Recipient City may be no longer than 40 characters for
the LocalDelivery delivery group.
4521 oord ERROR Recipient State/Province is required for a Local Delivery
delivery group.
4522 oord ERROR Recipient State/Province is not recognized for a Local
Delivery delivery group.
4523 oord ERROR Recipient postal code is required for the Local Delivery
delivery group.
4524 oord ERROR Recipient postal code for the Local Delivery delivery
group may be no longer than 15 characters.
4525 oord ERROR Recipient postal code for the Local Delivery delivery
group may only contain numeric characters.
4526 oord ERROR Recipient Country for the Local Delivery delivery group
is required.
4527 oord ERROR Recipient Country for the Local Delivery delivery group
is not recognized.
4528 oord ERROR Requested Delivery Date for the Local Delivery delivery
group is required.

group is invalid.
4530 oord ERROR Requested Delivery Window for the Local Delivery
delivery group is required.
group is not recognized.
group is invalid.
4533 oord ERROR Shipment delivery group contains Local Delivery
information.
4534 oord ERROR Invalid file size for file upload for Section
4535 oord ERROR Invalid file size for catalog document for Section
Pickup delivery group.
4537 oord ERROR Center ID {CENTER_ID} is not a United States location.
4538 oord ERROR Center ID {CENTER_ID} is not a retail location.
4542 oord ERROR Center ID could not be retrieved from the customer
configuration profile for the direct mail delivery group.
4543 oord ERROR Invalid file size.
4544 oord ERROR Requested Delivery Date is before the earliest ready
time for the order. Items cannot be completed until the
{EARLIEST_WINDOW} of {EARLIEST_DATE}.
Local Delivery delivery group.
4546 oord ERROR Center ID {CENTER_ID} does not offer Local Delivery.
4547 oord ERROR Center ID {CENTER_ID} does not offer Local Delivery
for Corporate Orders.
4548 oord ERROR TAB LABEL 1 is required.
4549 oord ERROR Document {DOC_NUMBER} includes tab information
but tab was not requested.
4550 oord ERROR Tab detail is required for Document {DOC_NUMBER}
since tab is requested.
4554 oord ERROR Tabs text font size is limited to 8pt, 10pt, 12pt, or 14pt.
4555 oord ERROR Tabs with different font types are invalid.
4559 oord ERROR Please shorten text or reduce font size.
4560 oord ERROR Font not supported.
4564 oord ERROR Tab/Insert page number is out of document range.
4565 oord ERROR FedEx account number for the shipment delivery group
may not be longer than 24 characters
4567 oord ERROR Your Account is on Hold
4569 oord ERROR Your Account is in pending status
4572 oord ERROR CVV number is not valid

4573 oord ERROR CVV number must be numeric
4577 oord ERROR Credit card processing is unavailable. Please try again.
4578 oord ERROR Credit card processing is unavailable. Please try again.
4581 oord ERROR Direct mail recipient first name is invalid (may be no
longer than 30 characters or less than 2 characters, and
must contain English alphabet letters only) in the
following line(s): {LINE_NUMBERS}
4582 oord ERROR Direct mail recipient last name is invalid (may be no
longer than 30 characters or less than 2 characters, and
must contain English alphabet letters only) in the
4583 oord ERROR Direct mail recipient postal code invalid (may be 5 or 9
character long, and must contain only numbers) in the
6000 oord ERROR Credit card processing is unavailable. Please try again
later
later
later
later
9000 oord FAILURE Unable to complete the request due to a system error.
9001 oord FAILURE Unable to complete the request due to a file processing
error.
9002 oord FAILURE Normalization of mixed page orientation failed.
9003 oord FAILURE Unable to validate binder options due to a database
error.
9004 oord FAILURE Unable to validate binding options due to a database
error.
9005 oord FAILURE Unable to validate color options due to a database error.
9006 oord FAILURE Unable to validate folding options due to a database
error.
9007 oord FAILURE Unable to validate sidedness due to a database error.
9008 oord FAILURE Unable to validate stapling due to a database error.
9010 oord FAILURE Unable to find an available location to produce the order.
9011 oord FAILURE Unable to locate uploaded file.
9015 oord FAILURE Unable to complete the request due to a general
processing or invoicing error.
9016 oord FAILURE Unable to validate the FedEx account number for Print.

9020 oord FAILURE OORD cannot start. Cannot get SystemAccount.
9021 oord FAILURE OORD cannot start. Cannot get guest user.
9022 oord FAILURE Client access denied.
9023 oord FAILURE System is busy. Please try again later.
9024 oord FAILURE Unable to convert the document to the requested media
size.
9026 oord FAILURE Document {DOC_NUMBER} is missing required data in
the catalog.
9028 oord FAILURE OORD cannot start. Cannot instantiate ODOC.


Media Categories and Descriptions
This section details the supported Media Categories for the Office Order Web Service and the
associated Media Descriptions, Detailed Descriptions, and Media Sizes.
Use the following table to select your media type. SKU’s are not used in the request; these are
provided for reference purposes only.
Associated SKU
Media Description Black Black
Media Category Specifications Size
Values & & Color Color
White White Single Double
Single Double Sided Sided
Sided Sided
STANDARD
White paper STANDARD_WHITE Standard White, 8.5X11 0001 0033 N/A N/A
Various weights 20# 8.5X14 0269 0270 N/A N/A
Opaque 11X17 0009 0041 N/A N/A
Acid-free RECYCLED_100_PERCENT Recycled, 20#, 8.5X11 2465 2466 N/A N/A
100% Recycled
Choose: 10M Encore
For everyday print jobs RECYCLED_30_PERCENT FedEx Office 8.5X11 2419 2456 0177 0176
White, 20# 30% 8.5X14 2463 2464 N/A N/A
Recycled 11X17 2461 2462 N/A N/A
PASTEL_BRIGHTS
Opaque ULTRA_LEMON Britehue, Ultra 8.5X11 0002 0034 0173 0178
Lightweight, but not thin Lemon, 60#
Uncoated ULTRA_LIME Britehue, Ultra 8.5X11 0002 0034 0173 0178
Colored paper Lime, 60#
Acid-free SUN_YELLOW Britehue, Sun 8.5X11 0002 0034 0173 0178
Yellow, 60# 8.5X14 0267 0268
Choose: 11X17 0010 0042 0197 0202
For eye-catching ULTRA_ORANGE Britehue, Ultra 8.5X11 0002 0034 0173 0178
promotional items such as Orange, 60#
brochures, handouts,
RED Britehue, Red, 8.5X11 0002 0034 0173 0178
newsletters, fliers, self-
60#
mailers, and small signs
ULTRA_FUSCHIA Britehue, Ultra 8.5X11 0002 0034 0173 0178
Fuschia, 60#
BRIGHT_BLUE Britehue, Blue, 8.5X11 0002 0034 0173 0178
60# 11X17 0010 0042 0197 0202

IVORY Pastels, Ivory, 8.5X11 0002 0034 0173 0178
24# 11X17 0010 0042 0197 0202
CANARY Pastels, Canary, 8.5X11 0002 0034 0173 0178
24#
SALMON Pastels, Salmon, 8.5X11 0002 0034 0173 0178
24#
ORCHID Pastels, Orchid, 8.5X11 0002 0034 0173 0178
24#
PASTEL_BLUE Pastels, Blue, 24# 8.5X11 0002 0034 0173 0178
PASTEL_GREEN Pastels, Green, 8.5X11 0002 0034 0173 0178
24#
CARDSTOCK
Heavyweight ULTRA_LIME Britehue, Ultra 8.5X11 0006 0038 2525 2527
Acid-free Lime, 65#
Matches most SUN_YELLOW Britehue, Sun 8.5X11 0006 0038 2525 2527
Pastel Bright papers Yellow, 65#
ULTRA_ORANGE Britehue, Ultra 8.5X11 0006 0038 2525 2527
Choose: Orange, 65#
For document covers, RED Britehue, Red 8.5X11 0006 0038 2525 2527
business cards, direct mail ULTRA_FUCHSIA Britehue, Ultra 8.5X11 0006 0038 2525 2527
pieces, postcards, document Fuchsia,65#
covers, invitations, tickets BRIGHT_BLUE Britehue, Blue, 8.5X11 0006 0038 2525 2527
for special events, place 65#
cards and announcements ULTRA_BRIGHT_WHITE Cardstock, Ultra 8.5X11 0005 0037 2525 2527
Bright White, 80#
Environment
NATURAL Cardstock, 8.5X11 0005 0037 2509 2513
Natural
IVORY Cardstock, Ivory, 8.5X11 0006 0038 2525 2527
65# Pastel 11X17 0008 0040 2526 2528
CANARY Cardstock, 8.5X11 0006 0038 2525 2527
Canary, 65#
Pastel
PASTEL_BLUE Cardstock, Blue, 8.5X11 0006 0038 2525 2527
65# Pastel
PASTEL_GREEN Cardstock, 8.5X11 0006 0038 2525 2527
Green, 65#
Pastel
INDEX_110_LB Index, White, 8.5X11 N/A N/A N/A N/A
110#, 20%
Recycled

TRANSPARENCY
For single-sided printing TRANSPARENCY TRANSPARENCY 85.X11 N/A N/A N/A N/A
EXECUTIVE
Opaque NATURAL Via Neutrals 8.5X11 0004 0036 0198 0214
Lightweight, but not thin Linen, Natural,
Uncoated 70#
Acid-free ULTRA_BRIGHT_WHITE Environment, 8.5X11 0004 0036 0198 0214
High quality Ultra Bright
White, 80# Text
Choose: PURE_WHITE Strathmore 8.5X11 0004 0036 0198 0214
For formal, professional Writing, 24#,
documents like resumes, 100% Cotton
business proposals and SIGNATURE_WHITE Laser Signature 8.5X11 0218 0221 0224 0227
executive communications White, 32# 8.5X14 0219 0222 0267 0268
11X17 0220 0223 0197 0202
RESUME
SOFT_PINK Environment 8.5X11 N/A N/A N/A N/A
Pageant Rose
SANDSTONE Concept, 8.5X11 0003 0035 0173 0178
Sandstone, 24# 11X17 0012 0044 0197 0202
SEA_SPRAY Concept, Sea 8.5X11 0003 0035 0173 0178
Spray, 24# 11X17 0012 0044 0197 0202
WILLOW Environment, 8.5X11 0003 0035 0173 0178
Willow, 80# Text
ANTIQUE Parchment, 8.5X11 0003 0035 0173 0178
Antique, 60#
TAN Parchment, Tan, 8.5X11 0003 0035 0173 0178
60 #
ANTIQUE_GRAY Environment, 8.5X11 0003 0035 0173 0178
Antique Gray,
80# Text
RESUME_CARDSTOCK
SOFT_PINK Cardstock, 8.5X11 0005 0037 2509 2513
Environment
Pageant Rose
SANDSTONE Cardstock, 8.5X11 0005 0037 2509 2513
Sandstone, 80#
SEA_SPRAY Cardstock, Sea 8.5X11 0005 0037 2509 2513
Spray, 80#

ANTIQUE_GRAY Cardstock, 8.5X11 0005 0037 2509 2513
Antique Gray,
80# Environment
TEXT_GLOSS
Coated slightly shiny finish COLOR_COPY_COVER Color Copy 8.5X11 N/A N/A N/A N/A
Choose: Cover, Photo 11X17 0076 2415 N/A N/A
For everyday printing when White, 80#
you want to add a GLOSS_TEXT Glossy Coated 8.5X11 0006 0038 2507 2511
professional touchX Text, 80# 11X17 0008 0040 2508 2512
STANDARD_LASER
Bright, white paper that SIGNATURE_WHITE Laser Signature 8.5X11 0218 0221 0224 0227
enables colors to print White, 32# 8.5X14 0219 0222 0267 0268
vividly 11X17 0220 0223 0197 0202
COLOR_COPY_COVER 80IB Laser Cover 8.5X11 0362 0364 2525 2527
Choose:
8.5X14 0367 0365 0348 0349
For documents with charts
LASER_PAPER Laser Standard 8.5X11 0330 0331 0173 0178
and graphs, presentations
Note: Standard paper for White, 24# 8.5X14 N/A N/A 0173 0178
and marketing materials,
color printing. 11X17 0332 0333 0197 0202
including those that
COVER_GLOSS
Glossy Coated 8.5X11 0005 0037 2509 2513

GLOSS_COVER_10_PT Cover, 10-pt 11X17 N/A N/A 2510 2514
COVER
BLACK_VINYL_COVER Black Vinyl 8.5X11 N/A N/A N/A N/A
BLUE_VINYL_COVER Blue Vinyl 8.5X11 N/A N/A N/A N/A
FROSTED_COVER Frosted Cover 8.5X11 N/A N/A N/A N/A
CLEAR_COVER Clear, 10 mil 8.5X11 N/A N/A N/A N/A
Design Cover
CARBONLESS_MULTI_PART
Print file with either portrait TWO_PART Carbonless, 2- 8.5X11 0074 2414 N/A N/A
or landscape orientation. part 8.5X14 N/A N/A N/A N/A
Glue binding will be on top
edge of forms THREE_PART Carbonless, 3- 8.5X11 0075 2415 N/A N/A
Choose: part 8.5X14 N/A N/A N/A N/A
For customizing your own
invoices

Finishing Terms Reference
This section provides additional context regarding finishing term definitions.
Finishing Terms Definition / Illustration

Collation When printing multiple copies of a document, your collation selection
designates how you wish to have the printed pages arranged.
Collated* UNCOLLATED
* Default designation. Not an enumerated value within FedEx Web Services for Office
and Print.
Stapling Documents that do not exceed the maximum thickness allowed for the
selected media may be stapled either in the upper left corner of the
document or along the left side of the document.
LEFT_UPPER TWO_ON_LONG_SIDE
Note: See Finishing Thresholds
Drilling Documents may be drilled (hole-punched) with either three holes along
the left side of the document or two holes along the top of the
document.
THREE_HOLE_SIDE TWO_HOLE_TOP

Cutting Single-page documents may be cut in halves, thirds, or quarters either
vertically or horizontally.
HALF_CUT_PORTRAIT HALF_CUT_LANDSCAPE
THIRD_CUT_PORTRAIT THIRD_CUT_LANDSCAPE
QUARTER_CUT_PORTRAIT QUARTER_CUT_LANDSCAPE
Folding Documents that do not exceed the maximum thickness allowed for the
selected media may be folded in single, double, or Z fashion.
SINGLE DOUBLE Z

Binding / Binder Documents that do not exceed the maximum thickness allowed may be
bound in coil or comb fashion, or placed in a binder.
COIL COMB BINDER*
* Binder is a Finishing Option Type, not a Binding type.
Lamination A document that is one sheet maximum may be laminated with a ¼

inch border or no border.
ONE_QUARTER_INCH None*
* Default designation. Not an enumerated value within FedEx Web Services for Office
and Print.
Tab Text positioning and orientation on tabs will be Text In (Portrait) and
Text Out (Landscape) and will default using Text In. This represents
the orientation of the tabs and not the document.
Text In (Portrait) Text Out (Landscape)


Finishing Thresholds
This section details maximum page quantity thresholds associated with finishing options and
selected media.
NOTE: These quantities refer to the number of physical pages, not the number of pages in the
uploaded file. For instance, a 20-page single-sided document has 20 physical pages.
However, a 20-page double-sided document has 10 physical pages.
Media / Pages Finishing
Binder Binding Other
0.5 ” 1.0 ” 1.5 ” 2.0 ” 3.0 ” Comb Coil Fold Staple Lamination
STANDARD 75 150 225 300 375 300 150 5 150 1
PASTEL
57 115 171 228 285 228 115 5 150 1
BRIGHTS
CARDSTOCK 25 50 75 100 125 100 50 1 75 1
EXECUTIVE 52 105 156 208 260 208 105 5 150 1
RESUME 52 105 156 208 260 208 105 5 150 1
RESUME
25 50 75 100 125 100 50 1 75 1
CARDSTOCK
TEXT GLOSS 50 100 150 200 250 200 100 1 75 N/A
STANDARD
75 150 225 300 375 300 150 5 150 1
LASER
COVER
20 40 60 80 100 80 40 1 75 N/A
GLOSS

Office Order Service Transaction Guide Sep 2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Office Order Service Transaction Guide Sep 2020

Uploaded by

Copyright:

Available Formats

FedEx Web Service for Office and Print

FedEx Office Order Service

• Web Services Description Language (WSDL) explained: msdn.microsoft.com/en-

January 2017 Updated with new Branding

September 2020 Updated with new Branding

FedEx Confidential and Proprietary 1

FedEx Confidential and Proprietary 2

FedEx Confidential and Proprietary 3

FedEx Confidential and Proprietary 4

- Request the following page sizes:

- Request desired print and finishing options

FedEx Confidential and Proprietary 5

FedEx Confidential and Proprietary 6

File Upload Output: resultCode=SUCCESS or FAILED; fileAuthToken; errorMessage;

Format: Key1=value1(URL encoded)&key2=value2(URL encoded)

Character set: ASCII

FedEx Confidential and Proprietary 7

FedEx Confidential and Proprietary 8

Element R/O/C Description

Office Order Upload Location Request

Client Detail R Descriptive data used to identify the client application.

Transaction Detail O Client-provided descriptive data used by the client to identify a

Web Authentication Detail

Integrator ID R Data assigned by FedEx used to identify integrator.

Localization O Defines the desired translation for localizedMessage text in

FedEx Confidential and Proprietary 9

Major R Data used by FedEx to identify the service business level.

Intermediate R Data used by FedEx to identify the service interface level.

Minor R Data used by FedEx to identify the service code level.

FedEx Confidential and Proprietary 10

Office Order Upload Location Reply

Values (in order from high to low):

Notifications Descriptive data detailing the status of a submitted transaction.

Transaction Detail Client-provided descriptive data used by the client to identify a

Values (in order from high to low):

Source Identifies the FedEx system, sub-system, or component that generated

Code Identifies the code corresponding to this notification. Combined with

FedEx Confidential and Proprietary 11

Note: See Notification Messages and Codes

Localized Message Translates the message to the localization requested. (Note:

Message Parameters Used internally by FedEx systems for message translation.

Major Data used by FedEx to identify the service business level.

Intermediate Data used by FedEx to identify the service interface level.

Minor Data used by FedEx to identify the service code level.

FedEx Confidential and Proprietary 12

The following details apply:

• Reply message will return the following: resultCode, fileAuthToken, errorMessage. In

FedEx Confidential and Proprietary 13

FedEx Confidential and Proprietary 14

Action Value = “UploadUrl”

See Upload Location Reply

Enctype Value = “multipart/form-data”

Method Value = “POST”

content-length Content-length entity header required.

Type Value =”file”

Name Value =”file1”

File name must be “file1”.

FedEx Confidential and Proprietary 15

Key1=value1(URL encoded)&key2=value2(URL encoded)

In case of multiple file upload, fileAuthToken is a list of comma

resultCode Identifies the severity of the request.

Values (in order from high to low):

fileAuthToken Server assigned token associated with file.