From 0722d33733bcd29b35ee15ad329181f9bbe558ca Mon Sep 17 00:00:00 2001 From: Rad W Date: Tue, 8 Dec 2015 20:14:43 -0500 Subject: [PATCH 1/3] added latest updates --- CHANGES.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/CHANGES.rst b/CHANGES.rst index e8ed688..69097ab 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -1,6 +1,18 @@ Change Log ========== +TODO: next release +------------------ + +* Bump ShipService WSDL to v17 for create and delete shipment. (radlws) +* Bump AddressValidation WSDL to v4. (radlws) +* Bump RateService WSDL to v18. (radlws) +* Bump TrackService WSDL to v10. (radlws) +* General improvements to base class. (radlws) +* Refactoring and updates to examples. (radlws) +* Added test classes. (radlws) +* Remove old and unused WSDLs. (radlws) + 1.1.1 ----- From 3ea0bb213432f33f67c6589d04e78ed0ee71a5c0 Mon Sep 17 00:00:00 2001 From: Rad W Date: Tue, 8 Dec 2015 20:16:00 -0500 Subject: [PATCH 2/3] added quick start and fedex support --- README.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.rst b/README.rst index 2755801..6b1e823 100644 --- a/README.rst +++ b/README.rst @@ -20,6 +20,12 @@ The easiest way is via pip or easy_install:: pip install fedex +Quick Start +----------- + +Edit the example_config.py file in examples with your fedex credentials +and run any of the provided examples. + Documentation ------------- @@ -37,6 +43,12 @@ package's quasi-maintained state, most problems are going to require investigation or a submitted pull request by someone other than Greg Taylor. +Fedex Support and Documentation +------------------------------- + +Fedex Support Email: websupport@fedex.com +Developer Portal: http://www.fedex.com/us/developer/ + Legal Mumbo Jumbo ----------------- From df1caf3ac35fc3c30b837f932733058fdb476da6 Mon Sep 17 00:00:00 2001 From: Rad W Date: Tue, 8 Dec 2015 20:25:17 -0500 Subject: [PATCH 3/3] remove old and or unused WSDLs --- fedex/wsdl/CloseService_v2.wsdl | 548 -- fedex/wsdl/CourierDispatchService_v3.wsdl | 1075 --- fedex/wsdl/RateService_v16.wsdl | 4866 ------------- fedex/wsdl/ReturnTagService_v1.wsdl | 421 -- fedex/wsdl/ShipService_v13.wsdl | 6290 ----------------- fedex/wsdl/ShipService_v7.wsdl | 4656 ------------ fedex/wsdl/TrackService_v5.wsdl | 1510 ---- .../test_server_wsdl/CloseService_v2.wsdl | 548 -- .../CourierDispatchService_v3.wsdl | 1075 --- .../test_server_wsdl/RateService_v16.wsdl | 4866 ------------- .../test_server_wsdl/ReturnTagService_v1.wsdl | 421 -- .../test_server_wsdl/ShipService_v13.wsdl | 6290 ----------------- .../wsdl/test_server_wsdl/ShipService_v7.wsdl | 4656 ------------ .../test_server_wsdl/TrackService_v5.wsdl | 1510 ---- 14 files changed, 38732 deletions(-) delete mode 100755 fedex/wsdl/CloseService_v2.wsdl delete mode 100755 fedex/wsdl/CourierDispatchService_v3.wsdl delete mode 100755 fedex/wsdl/RateService_v16.wsdl delete mode 100755 fedex/wsdl/ReturnTagService_v1.wsdl delete mode 100755 fedex/wsdl/ShipService_v13.wsdl delete mode 100755 fedex/wsdl/ShipService_v7.wsdl delete mode 100755 fedex/wsdl/TrackService_v5.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/CloseService_v2.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/CourierDispatchService_v3.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/RateService_v16.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/ReturnTagService_v1.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/ShipService_v13.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/ShipService_v7.wsdl delete mode 100755 fedex/wsdl/test_server_wsdl/TrackService_v5.wsdl diff --git a/fedex/wsdl/CloseService_v2.wsdl b/fedex/wsdl/CloseService_v2.wsdl deleted file mode 100755 index 11de3a3..0000000 --- a/fedex/wsdl/CloseService_v2.wsdl +++ /dev/null @@ -1,548 +0,0 @@ - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - ? - - - - - ? - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - ? - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - Identifies the date and time up to which unclosed shipments are to be closed. Both the date and time portions of the string are expected to be used. The time is the local time based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2009-04-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by a T (e.g. 2009-04-26T17:00:00). - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - ? - - - - - Service business level. - - - - - Service interface level. - - - - - Service code level. - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/CourierDispatchService_v3.wsdl b/fedex/wsdl/CourierDispatchService_v3.wsdl deleted file mode 100755 index 4159785..0000000 --- a/fedex/wsdl/CourierDispatchService_v3.wsdl +++ /dev/null @@ -1,1075 +0,0 @@ - - - - - - - - - - - - - The descriptive data to schedule a FedEx package pickup request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the origin of the shipment being picked up by FedEx. - - - - - Descriptive data for a freight shipment being picked up by FedEx. This is element is only required when requesting a freight service pickup. - - - - - Identifies the number of packages that are being tendered to FedEx for this pickup request. - - - - - - - - Identifies the total weight of the package or packages being tendered to FedEx for this pickup request. - - - - - Identifies the FedEx operating company (transportation) that is being sent the package pickup request. - - - - - Identifies the number of oversize packages that are being tendered to FedEx for this pickup request. Please refer to the FedEx Service Guide for package size limits to determine if a package is oversized for the service being shipped. - - - - - - - - Identifies any remarks or comments to be passed to the FedEx courier picking up the shipment. - - 60 - - - - - - Identifies the type of commodity being shipped. This element is required for an international shipment. - - 20 - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Identifies the unique client device submitting the request. - - 10 - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data for the local language and locale (i.e. country). - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code). - - 2 - - - - - - - - The descriptive data that governs data payload language/translations. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload(contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. Customers using the FedEx Web Services interface should set this element to "wsi". - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - Descriptive data about the origin of the package being picked up by FedEx. - - - - - Flag identifies if customer wants to use Account address or send and alternate address for pickup. - - - - - Descriptive data about the physical location of the package being picked up by FedEx. - - - - - Identifies the physical location where the courier should pick up the shipment. See CourierDispatchBuildingLocationType for valid values. - - - - - Identifies the part of the building where the package is located for pickup by FedEx. See BuildingPartCode for valid values. - - - - - Identifies additional descriptive information associated with the BuildingPartCode to assist the FedEx courier in finding the pickup location. - - - - - Identifies the date and time the package will be ready for pickup by FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the pickup based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS in 24-hour form. The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). Because this is a local time, no TZD should be included. If a TZD is included, it will be ignored, and the time treated as local to the pickup postal code. - - - - - Identifies the close time of the company requesting the pickup. The time is the local time of the pickup based on the shipper's time zone. The time component must be in the format: HH:MM:SS in 24-hour form (e.g. 17:00:00). Because this is a local time, no TZD should be included. If a TZD is included, it will be ignored, and the time treated as local to the pickup postal code. - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - Descriptive data identifying the point-of-contact person. - - - - - Identifies the contact person's name. - - 35 - - - - - - Identifies the contact person's title. - - 35 - - - - - - Identifies the contact person's company name. - - 35 - - - - - - Identifies the contact person's phone number. - - 16 - - - - - - Identifies the contact person's phone number extension. - - - - - Identifies the contact person's pager number. - - 16 - - - - - - Identifies the contact person's fax machine phone number. - - 16 - - - - - - Identifies the contact person's email address. - - 120 - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - 35 - - - - - - Name of city, town, etc. - - 35 - - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - 2 - - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. This element is required if both the City and StateOrProvinceCode are not present. - - 16 - - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - - - - Identification of a country. - - 2 - - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - Identifies the valid set of valid building locations for package pickup. - - - - - - - - - - - Identifies the valid set of building part types when requesting a package pickup. - - - - - - - - - - - - - Descriptive data regarding a FedEx freight service pickup request. - - - - - Identifies the collection of available FedEx transportation service options. Must be a valid FedEx freight service identifier. - - - - - Identifies the FedEx freight booking number. This element should contain numeric values only. - - 8 - - - - - - Descriptive data detailing the length, width, and height of the freight package or shipment being picked up by FedEx. - - - - - Identifies the type of truck that is needed for FedEx to pick up the freight shipment. See TruckType for valid values. - - - - - Identifies the tailer size needed for FedEx to pick up a freight shipment. See TrailerSizeType for valid values. - - - - - - - Identifies the collection of available FedEx transportation service options. - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data detailing the length, width, and height of a package. - - - - - Identifies the length of the package. - - - - - - - - Identifies the width of the package. - - - - - - - - Identifies the height of the package. - - - - - - - - Identifies the unit of measure associated with a dimensional values. See LinearUnits for valid values. - - - - - - - Identifies the collection of linear units of measure for a package dimension. - - - - - - - - - Identifies the valid set of truck types supported by FedEx. This type is appropriate only for freight pickup requests. - - - - - - - - - - Identifies the valid set of tractor tailer sizes supported by FedEx. This type is appropriate only for freight pickup requests. - - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. See WeightUnits for the valid values. - - - - - Identifies the weight value of the package. - - - - - - - Identifies the collection of units of measure that can be associated with a weight value. - - - - - - - - - The descriptive data returned to a client in response to a courier dispatch (i.e. package pickup) request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies the confirmation number assigned by FedEx for the request. - - 30 - - - - - - Identifies the FedEx Location identifier responsible for dispatching the courier to pickup the package. - - 5 - - - - - - Identifies the FedEx system code associated with the message text in the reply. - - 3 - - - - - - Identifies the message text from the FedEx system regarding whether or not the pickup request was successfully scheduled or not. - - 254 - - - - - - Identifies the Package Return Program control number. - - 19 - - - - - - - - The descriptive data to cancel a package pickup request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies the FedEx operating company (transportation) that was sent the courier dispatch that is being canceled. - - - - - Identifies the dispatch confirmation number that is being canceled. The dispatch confirmation number was returned to the client when the courier dispatch was requested. - - 30 - - - - - - Identifies the scheduled date for the courier dispatch that is being canceled. The scheduled date was provided by the client when the courier dispatch was requested. - - - - - Identifies the FedEx location identifier responsible for dispatching the courier for package pickup that is being canceled. The FedEx location identifier was returned to the client when the courier dispatch was requested. Required for Express service type. - - 5 - - - - - - Identifies comments the customer wants to convey to the FedEx courier regarding the package pickup. - - 60 - - - - - - - - The descriptive data returned to a client in response to a cancel dispatch request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a text message indicating the outcome of the cancel dispatch request. - - 254 - - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Identifies the severity of the Notification item. See NotificationSeverityType for list of returned values. - - - - - Identifies the source - what FedEx system, sub-system, or component generated the Notification item. - - - - - Identifies the error code generated by the FedEx system, sub-system or component. - - 8 - - - - - - Identifies the error message text. - - 255 - - - - - - Identifies the error message text in the localization requested. Currently not supported. - - - - - Used internally by FedEx systems for message translation. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The descriptive data to request availability of pickup. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data providing information about address to pickup from. - - - - - An array of PickupRequestType. If SAME_DAY is included, Options with ScheduleDay of SAME_DAY will be included in the reply. - If FUTURE_DAY is included, Options with ScheduleDay of FUTURE_DAY will be included in the reply. - - - - - The dispatch date (in the local time zone) for the pickup whose availability is being requested. - - - - - The time when the package will be ready to be picked up. The time is local to the pickup postal code, in 24-hour form (e.g. 13:00:00). It should not contain a TZD. If a TZD is included, it will be ignored - - - - - The lastest time at which the courier will be able to gain access to pick up the package(s). The time is local to the pickup postal code, in 24-hour form (e.g. 17:00:00). It should not contain a TZD. If a TZD is included, it will be ignored - - - - - The FedEx carrier(s) for which availability is requested. - - - - - Descriptive information about the shipment. - - - - - - - The descriptive data returned to a client in response to a cancel dispatch request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - the point in time when the request was processed - - - - - Identifies the options for picking up the shipment. - - - - - - - Describes the relationship between the date on which a dispatch occurs and the date on which it is created (scheduled) - by means of a CourierDispatchRequest. FUTURE_DAY means that the dispatch date is later than the date on which it is created. - SAME_DAY means that the dispatch is to occur on the date on which it is created. - - - - - - - - - - Descriptive information about the shipment. - - - - - Descriptive information about the dimensions of the package. - - - - - Descriptive information about the weight of the package. - - - - - - - The constraints on the scheduling of a dispatch, where that dispatch would be made by the Carrier, occur on the PickupDate, - and would be scheduled (created by means of a CourierDispatchRequest) on a date related to the PickupDate as described - by the "ScheduleDay" (SAME_DAY meaning that the creation would occur on the PickupDate, and FUTURE_DAY meaning that the creation - would occur on a date prior to the PickupDate). - - - - - the carrier to which this PickupScheduleOption applies - - - - - Descriptive information about the shipment. - - - - - Tells whether this option describes a dispatch created on the dispatch date (SAME_DAY), or on a prior date (FUTURE_DAY) - - - - - True if this pickup option is available. - - - - - Identifies the date (in the postal code's time zone) to which this PickupScheduleOption refers. - - - - - Identifies the latest allowed ready time (in the postal code's time zone) for a postal code. As a local time, it will not include a Time Zone Designator - - - - - Identifies the minimum required length of the window of time between the ReadyTime and the CustomerCloseTime. - - - - - Identifies availability of residential pickup. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/RateService_v16.wsdl b/fedex/wsdl/RateService_v16.wsdl deleted file mode 100755 index 19a28c1..0000000 --- a/fedex/wsdl/RateService_v16.wsdl +++ /dev/null @@ -1,4866 +0,0 @@ - - - - - - - - Specifies the role that identifies the permissions the accessor of the pending shipment. - - - - - - - - - Specifies additional labels to be produced. All required labels for shipments will be produced without the need to request additional labels. These are only available as thermal labels. - - - - - The type of additional labels to return. - - - - - The number of this type label to return - - - - - - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - The fully spelt out name of a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Specifies details for a package containing alcohol - - - - - The license type that the recipient of the alcohol package. - - - - - - - Specifies the type of license that the recipient of the alcohol shipment has. - - - - - - - - - - - - - - - - - - Identification of the type of barcode (symbology) used on FedEx documents and labels. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The instructions indicating how to print the Certificate of Origin ( e.g. whether or not to include the instructions, image type, etc ...) - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - - - - Specifies the type of brokerage to be applied to a shipment. - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the FedEx Office integrator. - - - - - Indicates the region from which the transaction is submitted. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - Identifies the type of funds FedEx should collect upon shipment delivery. - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - - Specifies the details of the charges are to be added to the COD collect amount. - - - - - Identifies the type of funds FedEx should collect upon package delivery - - - - - For Express this is the descriptive data that is used for the recipient of the FedEx Letter containing the COD payment. For Ground this is the descriptive data for the party to receive the payment that prints the COD receipt. - - - - - When the FedEx COD payment type is not CASH, indicates the contact and address of the financial institution used to service the payment of the COD. - - - - - Specifies the name of person or company receiving the secured/unsecured funds payment - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - - - - - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through the FedEx Systems. Customers are responsible for printing their own Commercial Invoice.If you would likeFedEx to generate a Commercial Invoice and transmit it to Customs. for clearance purposes, you need to specify that in the ShippingDocumentSpecification element. If you would like a copy of the Commercial Invoice that FedEx generated returned to you in reply it needs to be specified in the ETDDetail/RequestedDocumentCopies element. Commercial Invoice support consists of maximum of 99 commodity line items. - - - - - Any comments that need to be communicated about this shipment. - - - - - Any freight charges that are associated with this shipment. - - - - - Any taxes or miscellaneous charges(other than Freight charges or Insurance charges) that are associated with this shipment. - - - - - Specifies which kind of charge is being recorded in the preceding field. - - - - - Any packing costs that are associated with this shipment. - - - - - Any handling costs that are associated with this shipment. - - - - - Free-form text. - - - - - Free-form text. - - - - - Free-form text. - - - - - The reason for the shipment. Note: SOLD is not a valid purpose for a Proforma Invoice. - - - - - Name of the International Expert that completed the Commercial Invoice different from Sender. - - - - - Required for dutiable international Express or Ground shipments. This field is not applicable to an international PIB(document) or a non-document which does not require a Commercial Invoice. - - - - - - - The instructions indicating how to print the Commercial Invoice( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies the usage and identification of a customer supplied image to be used on this document. - - - - - - - Information about the transit time and delivery commitment date and time. - - - - - The Commodity applicable to this commitment. - - - - - The FedEx service type applicable to this commitment. - - - - - Shows the specific combination of service options combined with the service type that produced this committment in the set returned to the caller. - - - - - Supporting detail for applied options identified in preceding field. - - - - - THe delivery commitment date/time. Express Only. - - - - - The delivery commitment day of the week. - - - - - The number of transit days; applies to Ground and LTL Freight; indicates minimum transit time for SmartPost. - - - - - Maximum number of transit days, for SmartPost shipments. - - - - - The service area code for the destination of this shipment. Express only. - - - - - The address of the broker to be used for this shipment. - - - - - The FedEx location identifier for the broker. - - - - - The delivery commitment date/time the shipment will arrive at the border. - - - - - The delivery commitment day of the week the shipment will arrive at the border. - - - - - The number of days it will take for the shipment to make it from broker to destination - - - - - The delivery commitment date for shipment served by GSP (Global Service Provider) - - - - - The delivery commitment day of the week for the shipment served by GSP (Global Service Provider) - - - - - Messages concerning the ability to provide an accurate delivery commitment on an International commit quote. These could be messages providing information about why a commitment could not be returned or a successful message such as "REQUEST COMPLETED" - - - - - Messages concerning the delivery commitment on an International commit quote such as "0:00 A.M. IF NO CUSTOMS DELAY" - - - - - Information about why a shipment delivery is delayed and at what level (country/service etc.). - - - - - - Required documentation for this shipment. - - - - - Freight origin and destination city center information and total distance between origin and destination city centers. - - - - - - - The type of delay this shipment will encounter. - - - - - - - - - - - - - - - - - - - - - - - - - - This field is used for enterprise transactions. - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - - - - - - - - - Uniquely identifies a consolidation, which is a logical container for a collection of shipments. - - - - - Specifies the type of consolidation. - - - - - Uniquely identifies the consolidation, within a given type and date. - - - - - The date on which the consolidation was created. - - - - - - - - - - - - - - - - - The descriptive data for a point-of-contact person. - - - - - Client provided identifier corresponding to this contact information. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies a toll free number, if any, associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - - - - - - - - - - - The currency code for the original (converted FROM) currency. - - - - - The currency code for the final (converted INTO) currency. - - - - - Multiplier used to convert fromCurrency units to intoCurrency units. - - - - - - - - - Indicates the type of custom delivery being requested. - - - - - Time by which delivery is requested. - - - - - Range of dates for custom delivery request; only used if type is BETWEEN. - - - - - Date for custom delivery request; only used for types of ON, BETWEEN, or AFTER. - - - - - - - - - - - - - - - Data required to produce a custom-specified document, either at shipment or package level. - - - - - Common information controlling document production. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Identifies the formatting specification used to construct this custom document. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified barcode symbology. - - - - - - - - - Width of thinnest bar/space element in the barcode. - - - - - - - - Solid (filled) rectangular area on label. - - - - - - - - - - - - - - - - - - - - - - - - Image to be included from printer's memory, or from a local file for offline clients. - - - - - - Printer-specific index of graphic image to be printed. - - - - - Fully-qualified path and file name for graphic image to be printed. - - - - - - - - - Horizontal position, relative to left edge of custom area. - - - - - Vertical position, relative to top edge of custom area. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified printer font (for thermal labels) or generic font/size (for plain paper labels). - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - Generic font name for use with plain paper labels. - - - - - Generic font size for use with plain paper labels. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default is former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - - - Controls which data/sections will be suppressed. - - - - - For customers producing their own Ground labels, this field specifies which secondary barcode will be printed on the label; so that the primary barcode produced by FedEx has the correct SCNC. - - - - - - - Controls the number of additional copies of supplemental labels. - - - - - This value reduces the default quantity of destination/consignee air waybill labels. A value of zero indicates no change to default. A minimum of one copy will always be produced. - - - - - - - - - - - - - - - - - Interacts both with properties of the shipment and contractual relationship with the shipper. - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - - - - - - - - - - - Specifies additional description about customs options. This is a required field when the customs options type is "OTHER". - - - - - - - - - - - - - - - - - - - - - - - - - - - Describes an approved container used to package dangerous goods commodities. This does not describe any individual inner receptacles that may be within this container. - - - - - Indicates whether there are additional inner receptacles within this container. - - - - - Indicates the type of this dangerous goods container, as specified by the IATA packing instructions. For example, steel cylinder, fiberboard box, plastic jerrican and steel drum. - - - - - Indicates the packaging type of the container used to package the radioactive materials. - - - - - Indicates the number of occurrences of this container with identical dangerous goods configuration. - - - - - Documents the kinds and quantities of all hazardous commodities in the current container. - - - - - - - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - Indicates which kinds of hazardous content are in the current package. - - - - - Indicates whether there is additional customer provided packaging enclosing the approved dangerous goods containers. - - - - - Identifies the configuration of this dangerous goods package. The common configuration is represented at the shipment level. - - - - - Indicates one or more containers used to pack dangerous goods commodities. - - - - - Description of the packaging of this commodity, suitable for use on OP-900 and OP-950 forms. - - - - - Name, title and place of the signatory for this shipment. - - - - - Telephone number to use for contact in the event of an emergency. - - - - - Offeror's name or contract number, per DOT regulation. - - - - - Specifies the contact of the party responsible for handling the infectious substances, if any, in the dangerous goods shipment. - - - - - Specifies additional handling information for the current package. - - - - - Specifies the radioactivity detail for the current package, if the package contains radioactive materials. - - - - - - - - - - - - The instructions indicating how to print the 1421c form for dangerous goods shipment. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Specifies that name, title and place of the signatory responsible for the dangerous goods shipment. - - - - - - - Indicates the place where the form is signed. - - - - - - - - - - - - - - - - - - - - - - - - Information about why a shipment delivery is delayed and at what level( country/service etc.). - - - - - The date of the delay - - - - - - The attribute of the shipment that caused the delay(e.g. Country, City, LocationId, Zip, service area, special handling ) - - - - - The point where the delay is occurring (e.g. Origin, Destination, Broker location) - - - - - The reason for the delay (e.g. holiday, weekend, etc.). - - - - - The name of the holiday in that country that is causing the delay. - - - - - - - The attribute of the shipment that caused the delay(e.g. Country, City, LocationId, Zip, service area, special handling ) - - - - - - - - - - - - - - The point where the delay is occurring ( e.g. Origin, Destination, Broker location). - - - - - - - - - - - - - - - Specifies the tracking id for the return, if preassigned. - - - - - - - Data required to complete the Destionation Control Statement for US exports. - - - - - - Comma-separated list of up to four country codes, required for DEPARTMENT_OF_STATE statement. - - - - - Name of end user, required for DEPARTMENT_OF_STATE statement. - - - - - - - - - - - - - - - - - - - - - Driving or other transportation distances, distinct from dimension measurements. - - - - - Identifies the distance quantity. - - - - - Identifies the unit of measure for the distance value. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Content of the email message. - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - - - - - - - - - Information describing the address of of the email recipient, role of the email recipient and languages that are requested to be supported. - - - - - EMail address of the recipient. - - - - - The relationship that the customer has to the pending shipment. - - - - - Specifies how the email notification for the pending shipment need to be processed. - - - - - Localization and language details specified by the recipient of the EMail. - - - - - - - - - - - - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how to apply the localization detail to the current context. - - - - - - - - Electronic Trade document references used with the ETD special service. - - - - - Indicates the types of shipping documents produced for the shipper by FedEx (see ShippingDocumentSpecification) which should be copied back to the shipper in the shipment result data. - - - - - - - - - The instructions indicating how to print the Export Declaration. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US). - - - - - - - - - - - - - - - - - - - - - - - - - Indicates a FedEx Express operating region. - - - - - - - - - - - - Identifies a kind of FedEx facility. - - - - - - - - - - - - - - - Specifies the optional features/characteristics requested for a Freight shipment utilizing a flatbed trailer. - - - - - - - - - - - - - - Data required to produce the Freight handling-unit-level address labels. Note that the number of UNIQUE labels (the N as in 1 of N, 2 of N, etc.) is determined by total handling units. - - - - - - Indicates the number of copies to be produced for each unique label. - - - - - Specifies the quadrant of the page on which the label printing will start. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - - - - Individual charge which contributes to the total base charge for the shipment. - - - - - Freight class for this line item. - - - - - Effective freight class used for rating this line item. - - - - - NMFC Code for commodity. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - Rate or factor applied to this line item. - - - - - Identifies the manner in which the chargeRate for this line item was applied. - - - - - The net or extended charge for this line item. - - - - - - - Specifies the way in which base charges for a Freight shipment or shipment leg are calculated. - - - - - - - - - - - - - - - - These values represent the industry-standard freight classes used for FedEx Freight and FedEx National Freight shipment description. (Note: The alphabetic prefixes are required to distinguish these values from decimal numbers on some client platforms.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Information about the Freight Service Centers associated with this shipment. - - - - - Information about the origin Freight Service Center. - - - - - Information about the destination Freight Service Center. - - - - - The distance between the origin and destination FreightService Centers - - - - - - - - - - Date for all Freight guarantee types. - - - - - - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - - - - - Rate data specific to FedEx Freight or FedEx National Freight services. - - - - - A unique identifier for a specific rate quotation. - - - - - Specifies whether the rate quote was automated or manual. - - - - - Specifies how total base charge is determined. - - - - - Freight charges which accumulate to the total base charge for the shipment. - - - - - Human-readable descriptions of additional information on this shipment rating. - - - - - - - Additional non-monetary data returned with Freight rates. - - - - - Unique identifier for notation. - - - - - Human-readable explanation of notation. - - - - - - - Specifies the type of rate quote - - - - - - - - - This class describes the relationship between a customer-specified address and the FedEx Freight / FedEx National Freight Service Center that supports that address. - - - - - Freight Industry standard non-FedEx carrier identification - - - - - The name of the Interline carrier. - - - - - Additional time it might take at the origin or destination to pickup or deliver the freight. This is usually due to the remoteness of the location. This time is included in the total transit time. - - - - - Service branding which may be used for local pickup or delivery, distinct from service used for line-haul of customer's shipment. - - - - - Distance between customer address (pickup or delivery) and the supporting Freight / National Freight service center. - - - - - Time to travel between customer address (pickup or delivery) and the supporting Freight / National Freight service center. - - - - - Specifies when/how the customer can arrange for pickup or delivery. - - - - - Specifies days of operation if localServiceScheduling is LIMITED. - - - - - Freight service center that is a gateway on the border of Canada or Mexico. - - - - - Alphabetical code identifying a Freight Service Center - - - - - Freight service center Contact and Address - - - - - - - Specifies the type of service scheduling offered from a Freight or National Freight Service Center to a customer-supplied address. - - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Account number used with FEDEX_FREIGHT service. - - - - - Used for validating FedEx Freight account number and (optionally) identifying third party payment on the bill of lading. - - - - - Used in connection with "Send Bill To" (SBT) identification of customer's account used for billing. - - - - - Indicates the role of the party submitting the transaction. - - - - - Designates the terms of the "collect" payment for a Freight Shipment. - - - - - Identifies the declared value for the shipment - - - - - Identifies the declared value units corresponding to the above defined declared value - - - - - - Identifiers for promotional discounts offered to customers. - - - - - Total number of individual handling units in the entire shipment (for unit pricing). - - - - - Estimated discount rate provided by client for unsecured rate quote. - - - - - Total weight of pallets used in shipment. - - - - - Overall shipment dimensions. - - - - - Description for the shipment. - - - - - Specifies which party will pay surcharges for any special services which support split billing. - - - - - - Details of the commodities in the shipment. - - - - - - - Description of an individual commodity or class of content in a shipment. - - - - - Freight class for this line item. - - - - - Specification of handling-unit packaging for this commodity or class line. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - - Volume (cubic measure) for this commodity or class line. - - - - - - - Indicates the role of the party submitting the transaction. - - - - - - - - - Specifies which party will be responsible for payment of any surcharges for Freight special services for which split billing is allowed. - - - - - Identifies the special service. - - - - - Indicates who will pay for the special service. - - - - - - - Data required to produce a General Agency Agreement document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - This describes the inner receptacle details for a hazardous commodity within the dangerous goods container. - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies the details of any radio active materials within the commodity. - - - - - - - Identifies and describes an individual hazardous commodity. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - - - - - - - Indicates any special processing options to be applied to the description of the dangerous goods commodity. - - - - - Information related to quantity limitations and operator or state variations as may be applicable to the dangerous goods commodity. - - - - - - - Specifies any special processing to be applied to the dangerous goods commodity description validation. - - - - - - - - This describes information about the inner receptacles for the hazardous commodity in a particular dangerous goods container. - - - - - This specifies the quantity contained in the inner receptacle. - - - - - - - Specifies how the commodity is to be labeled. - - - - - - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies how the customer wishes the label text to be handled for this commodity in this package. - - - - - Text used in labeling the commodity under control of the labelTextOption field. - - - - - - - Indicates which kind of hazardous content is being reported. - - - - - - - - - - - - - Identifies number and type of packaging units for hazardous commodities. - - - - - Number of units of the type below. - - - - - Units in which the hazardous commodity is packaged. - - - - - - - Specifies documentation and limits for validation of an individual packing group/category. - - - - - - Coded specification for how commodity is to be packed. - - - - - - - Identifies DOT packing group for a hazardous commodity. - - - - - - - - - - - Identifies amount and units for quantity of hazardous commodities. - - - - - Number of units of the type below. - - - - - Units by which the hazardous commodity is measured. For IATA commodity, the units values are restricted based on regulation type. - - - - - Specifies which measure of quantity is to be validated. - - - - - - - Specifies the measure of quantity to be validated against a prescribed limit. - - - - - - - - - Identifies the source of regulation for hazardous commodity data. - - - - - - - - - - - - - - - - - - Contact phone number for recipient of shipment. - - - - - Contact and address of FedEx facility at which shipment is to be held. - - - - - Type of facility at which package/shipment is to be held. - - - - - Location identification (for facilities identified by an alphanumeric location code). - - - - - Location identification (for facilities identified by an numeric location code). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - - - - - - Specifies the order in which the labels will be returned - - - - - - - - - - - - - - - Relative to normal orientation for the printer. - - - - - - - - - - - - - - - - - - Specifies the order in which the labels are requested to be returned - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the Liability Coverage Amount. For Jan 2010 this value represents coverage amount per pound - - - - - - - - - - - - - Represents a one-dimensional measurement in small units (e.g. suitable for measuring a package or document), contrasted with Distance, which represents a large one-dimensional measurement (e.g. distance between cities). - - - - - The numerical quantity of this measurement. - - - - - The units for this measurement. - - - - - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - - - - - - - - - - - - - - - - - - - - - - Data required to produce a Certificate of Origin document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - Contact information for "Authorized Signature" area of form. - - - - - - - - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - Date range over which RVC net cost was calculated. - - - - - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - - - - - - - - - - The instructions indicating how to print the OP-900 form for hazardous materials packages. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Identifies which reference type (from the package's customer references) is to be used as the source for the reference on this OP-900. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - Data field to be used when a name is to be printed in the document instead of (or in addition to) a signature image. - - - - - - - - - - - - - - Data for a package's rates, as calculated per a specific rate type. - - - - - Type used for this specific set of rate data. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - - The dimensional weight of this package (if greater than actual). - - - - - The oversize weight of this package (if the package is oversize). - - - - - The transportation charge only (prior to any discounts applied) for this package. - - - - - The sum of all discounts on this package. - - - - - This package's baseCharge - totalFreightDiscounts. - - - - - The sum of all surcharges on this package. - - - - - This package's netFreight + totalSurcharges (not including totalTaxes). - - - - - The sum of all taxes on this package. - - - - - This package's netFreight + totalSurcharges + totalTaxes. - - - - - - All rate discounts that apply to this package. - - - - - All rebates that apply to this package. - - - - - All surcharges that apply to this package (either because of characteristics of the package itself, or because it is carrying per-shipment surcharges for the shipment of which it is a part). - - - - - All taxes applicable (or distributed to) this package. - - - - - - - - - - - - - - - - - - - - These special services are available at the package level for some or all service types. If the shipper is requesting a special service which requires additional data, the package special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment or package. - - - - - For use with FedEx Ground services only; COD must be present in shipment's special services. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This information describes the kind of pending shipment being requested. - - - - - - Date after which the pending shipment will no longer be available for completion. - - - - - Only used with type of EMAIL. - - - - - - These are documents that are recommended to be included with the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This class describes the pickup characteristics of a shipment (e.g. for use in a tag request). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates the packaging type of the container used to package radioactive hazardous materials. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates whether packaging type "EXCEPTED" or "EXCEPTED_PACKAGE" is for radioactive material in reportable quantity. - - - - - - - - - Indicates the reason that a dim divisor value was chose. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Selects the value from a set of rate data to which the percentage is applied. - - - - - - - - - - - The response to a RateRequest. The Notifications indicate whether the request was successful or not. - - - - - This indicates the highest level of severity of all the notifications returned in this reply. - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Contains the CustomerTransactionId that was sent in the request. - - - - - The version of this reply. - - - - - Each element contains all rate data for a single service. If service was specified in the request, there will be a single entry in this array; if service was omitted in the request, there will be a separate entry in this array for each service being compared. - - - - - - - - - - - Shows the specific combination of service options combined with the service type that produced this committment in the set returned to the caller. - - - - - Supporting detail for applied options identified in preceding field. - - - - - - - - - - - Not populated by FAST service in Jan07. - - - - - Not populated by FAST service in Jan07. - - - - - Not populated by FAST service in Jan07. - - - - - Maximum expected transit time - - - - - Not populated by FAST service in Jan07. Actual signature option applied, to allow for cases in wihch the original value conflicted with other service features in the shipment. - - - - - - Each element contains all rate data for a single rate type. - - - - - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - - - - Allows the caller to specify that the transit time and commit data are to be returned in the reply. - - - - - Candidate carriers for rate-shopping use case. This field is only considered if requestedShipment/serviceType is omitted. - - - - - Contains zero or more service options whose combinations are to be considered when replying with available services. - - - - - If provided, identifies the consolidation to which this open shipment should be added after successful creation. - - - - - The shipment for which a rate quote (or rate-shopping comparison) is desired. - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - - - Echoed from the corresponding package in the rate request (if provided). - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - The difference between "list" and "account" net charge. - - - - - Ground COD is shipment level. - - - - - - Rate data that are tied to a specific package and rate type combination. - - - - - - - This class groups the shipment and package rating data for a specific rate type for use in a rating reply, which groups result data by rate type. - - - - - The difference between "list" and "account" total net charge. - - - - - Express COD is shipment level. - - - - - The shipment-level totals for this rate type. - - - - - The package-level data for this rate type. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - Specifies the kind of identification being used. - - - - - Contains the actual ID value, of the type specified above. - - - - - - - - - - - - - - Specifies the details about documents that are recommended to be included with the shipment for ease of shipment processing and transportation. - - - - - - - - Type of documents that are recommended to be included with the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies details needed to generate any label artifacts required due to regulatory requirements. - - - - - - Specifies how the customer requested the regulatory label to be generated. - - - - - - - - - - - - Describes the vertical position of an item relative to another item. - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - - Specifies the declared value for carriage of the package. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the package. This field is only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case total weight and packageCount on the shipment will be used to determine this value. - - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - Human-readable text describing the contents of the package to be used for clearance purposes. - - - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - - - - - - - - Specifies the total declared value for carriage of the shipment. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the shipment. - - - - - This attribute indicates the currency the caller requests to have used in all returned monetary values (when a choice is possible). - - - - - - - - Physical starting address for the shipment, if different from shipper's address. - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Used with Ground Home Delivery and Freight. - - - - - - Customs clearance data, used for both international and intra-country shipping. - - - - - For use in "process tag" transaction. - - - - - Specifies the characteristics of a shipment pertaining to SmartPost services. - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - - Contains data used to create additional (non-label) shipping documents. - - - - - Specifies whether and what kind of rates the customer wishes to have quoted on this shipment. The reply will also be constrained by other data on the shipment and customer. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - The total number of packages in the entire shipment (even when the shipment spans multiple transactions.) - - - - - Specifies which package-level data values are provided at the shipment-level only. The package-level data values types specified here will not be provided at the package-level. - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the tracking number of the master associated with the return shipment. - - - - - - - - These values are used to control the availability of certain special services at the time when a customer uses the e-mail label link to create a return shipment. - - - - - - - - - - - - Identifies the allowed (merchant-authorized) special services which may be selected when the subsequent shipment is created. Only services represented in EMailLabelAllowedSpecialServiceType will be controlled by this list. - - - - - - - The instructions indicating how to print the return instructions( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies additional customer provided text to be inserted into the return document. - - - - - - - - - - - - - - - - - - - - - - The "PAYOR..." rates are expressed in the currency identified in the payor's rate table(s). The "RATED..." rates are expressed in the currency of the origin country. Former "...COUNTER..." values have become "...RETAIL..." values, except for PAYOR_COUNTER and RATED_COUNTER, which have been removed. - - - - - - - - - - - - - - - June 2011 ITG 121203 IR-RMA number has been removed from this structure and added as a new customer reference type. The structure remains because of the reason field below. - - - - - - - - Describes the rotation of an item from its default orientation. - - - - - - - - - - - - - - - - - - - These values control the optional features of service that may be combined in a commitment/rate comparision transaction. - - - - - - - - - - - - Supporting detail for applied options identified in a rate quote. - - - - - Identifies the type of Freight Guarantee applied, if FREIGHT_GUARANTEE is applied to the rate quote. - - - - - Identifies the smartPostHubId used during rate quote, if SMART_POST_HUB_ID is a variable option on the rate request. - - - - - Identifies the indicia used during rate quote, if SMART_POST_ALLOWED_INDICIA is a variable option on the rate request. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - Specifies the data that is common to dangerous goods packages in the shipment. This is populated when the shipment contains packages with identical dangerous goods commodities. - - - - - - - Shipment-level totals of dry ice data across all packages. - - - - - Total number of packages in the shipment that contain dry ice. - - - - - Total shipment dry ice weight for all packages. - - - - - - - Data for a single leg of a shipment's total/summary rates, as calculated per a specific rate type. - - - - - Human-readable text describing the shipment leg. - - - - - Origin for this leg. - - - - - Specifies the location id the origin of shipment leg. - - - - - Destination for this leg. - - - - - Specifies the location id the destination of shipment leg. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - These values identify which package-level data values will be provided at the shipment-level. - - - - - - - - - - Data for a shipment's total/summary rates, as calculated per a specific rate type. The "total..." fields may differ from the sum of corresponding package data for Multiweight or Express MPS. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Identifies the Rate Details per each leg in a Freight Shipment - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These special services are available at the shipment level for some or all service types. If the shipper is requesting a special service which requires additional data (such as the COD amount), the shipment special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment (or other shipment-level transaction). - - - - - - - - - - This field should be populated for pending shipments (e.g. e-mail label) It is required by a PENDING_SHIPMENT special service type. - - - - - - - - - - - Electronic Trade document references. - - - - - Specification for date or range of dates on which delivery is to be attempted. - - - - - - - Each occurrence of this class specifies a particular way in which a kind of shipping document is to be produced and provided. - - - - - Values in this field specify how to create and return the document. - - - - - Specifies how to organize all documents of this type. - - - - - Specifies how to e-mail document images. - - - - - Specifies how a queued document is to be printed. - - - - - - - Specifies how to return a shipping document to the caller. - - - - - - - - - - - - - - - Specifies how to e-mail shipping documents. - - - - - Provides the roles and email addresses for e-mail recipients. - - - - - Identifies the convention by which documents are to be grouped as e-mail attachments. - - - - - Specifies the language in which the email containing the document is requested to be composed. - - - - - - - - - - - - - Specifies an individual recipient of e-mailed shipping document(s). - - - - - Identifies the relationship of this recipient in the shipment. - - - - - Address to which the document is to be sent. - - - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies how to create, organize, and return the document. - - - - - Specifies how far down the page to move the beginning of the image; allows for printing on letterhead and other pre-printed stock. - - - - - - - For those shipping document types which have both a "form" and "instructions" component (e.g. NAFTA Certificate of Origin and General Agency Agreement), this field indicates whether to provide the instructions. - - - - - - Governs the language to be used for this individual document, independently from other content returned for the same shipment. - - - - - - - Specifies how to organize all shipping documents of the same type. - - - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - Specifies printing options for a shipping document. - - - - - Provides environment-specific printer identification. - - - - - - - Contains all data required for additional (non-label) shipping documents to be produced in conjunction with a specific shipment. - - - - - Indicates the types of shipping documents requested by the shipper. - - - - - - - Specifies the production of each package-level custom document (the same specification is used for all packages). - - - - - Specifies the production of a shipment-level custom document. - - - - - - - - Specifies the production of the OP-900 document for hazardous materials packages. - - - - - Specifies the production of the 1421c document for dangerous goods shipment. - - - - - Specifies the production of the OP-900 document for hazardous materials. - - - - - Specifies the production of the return instructions document. - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These values are mutually exclusive; at most one of them can be attached to a SmartPost shipment. - - - - - - - - - - - - - - - - - - - - - Data required for shipments handled under the SMART_POST and GROUND_SMART_POST service types. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifice the kind of tax or miscellaneous charge being reported on a Commercial Invoice. - - - - - - - - - - - - - - - - - Identifies the usage of Tax Identification Number in Shipment processing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the date until which the document is available - - - - - - - Specifies the application that is responsible for managing the document id. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Description of the uploaded document. - - - - - - - - - - - - - - - - - - - - - This definition of variable handling charge detail is intended for use in Jan 2011 corp load. - - - - - - Actual percentage (10 means 10%, which is a mutiplier of 0.1) - - - - - Select the value from a set of rate data to which the percentage is applied. - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - - - - - - - Three-dimensional volume/cubic measurement. - - - - - - - - - Units of three-dimensional volume/cubic measure. - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/ReturnTagService_v1.wsdl b/fedex/wsdl/ReturnTagService_v1.wsdl deleted file mode 100755 index 70bf802..0000000 --- a/fedex/wsdl/ReturnTagService_v1.wsdl +++ /dev/null @@ -1,421 +0,0 @@ - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Identifying part of the authentication key. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Identifies the unique client device submitting the request. - - 10 - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data that governs data payload language/translations. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - The descriptive data for the local language and locale (i.e. country). - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code). - - 2 - - - - - - - - The descriptive data regarding the version/level of a service operation performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - - - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. First five characters will be accepted. - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - - - - Identification of a country. - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Identifies the severity of the Notification item. See NotificationSeverityType for list of returned values. - - - - - Identifies the source - what FedEx system, sub-system, or component generated the Notification item. - - - - - Identifies the error code generated by the FedEx system, sub-system or component. - - 8 - - - - - - Identifies the error message text. - - 255 - - - - - - Identifies the error message text in the localization requested. Currently not supported. - - - - - Used internally by FedEx systems for message translation. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - FedEx Express Tag Availability request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Package ready date and time. - - - - - Sender postal code and country. - - - - - FedEx Service type. - - - - - FedEx Packaging type. - - - - - - - FedEx Express Tag Availability reply. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - This is the minimum time window that must be allocated for the FedEx courier to make the pickup. This is a length of time. The difference between the Business close time, (or the local Cutoff time if it is earlier than the Business Close time), and the Ready Time must be equal to or exceed the access time. - - - - - Latest time a FedEx courier will be available to pick up the package from the Sender. - - - - - Indicates the Express Tag Service availability at the sender postal code indicated in the request. - - - - - - - Identifies the Express Tag Service availability. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/ShipService_v13.wsdl b/fedex/wsdl/ShipService_v13.wsdl deleted file mode 100755 index 4c4bd09..0000000 --- a/fedex/wsdl/ShipService_v13.wsdl +++ /dev/null @@ -1,6290 +0,0 @@ - - - - - - - - - - - - - - - - - - Specifies additional labels to be produced. All required labels for shipments will be produced without the need to request additional labels. These are only available as thermal labels. - - - - - The type of additional labels to return. - - - - - The number of this type label to return - - - - - - - Identifies the type of additional labels. - - - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - The fully spelt out name of a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Specifies the details around the ADR license required for shipping. - - - - - - - - - - - - - - - Specifies the tracking id for the payment on the return. - - - - - Specifies additional customer reference data about the associated shipment. - - - - - Specifies shipment level operational information. - - - - - Specifies package level operational information on the associated shipment. This information is not tied to an individual outbound package. - - - - - - - - - - - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - - - - - - - - Identification of the type of barcode (symbology) used on FedEx documents and labels. - - - - - - - - - - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as binary data (i.e. not ASCII text). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to Cancel a Pending shipment. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The instructions indicating how to print the Certificate of Origin ( e.g. whether or not to include the instructions, image type, etc ...) - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - - - - Specifies the type of brokerage to be applied to a shipment. - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - Specifies the type of adjustment was performed to the COD collection amount during rating. - - - - - - - - - Identifies the type of funds FedEx should collect upon shipment delivery. - - - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - - Specifies the details of the charges are to be added to the COD collect amount. - - - - - Identifies the type of funds FedEx should collect upon package delivery - - - - - For Express this is the descriptive data that is used for the recipient of the FedEx Letter containing the COD payment. For Ground this is the descriptive data for the party to receive the payment that prints the COD receipt. - - - - - When the FedEx COD payment type is not CASH, indicates the contact and address of the financial institution used to service the payment of the COD. - - - - - Specifies the name of person or company receiving the secured/unsecured funds payment - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - - - Specifies the information associated with a package that has COD special service in a ground shipment. - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through the FedEx Systems. Customers are responsible for printing their own Commercial Invoice.If you would likeFedEx to generate a Commercial Invoice and transmit it to Customs. for clearance purposes, you need to specify that in the ShippingDocumentSpecification element. If you would like a copy of the Commercial Invoice that FedEx generated returned to you in reply it needs to be specified in the ETDDetail/RequestedDocumentCopies element. Commercial Invoice support consists of maximum of 99 commodity line items. - - - - - Any comments that need to be communicated about this shipment. - - - - - Any freight charges that are associated with this shipment. - - - - - Any taxes or miscellaneous charges(other than Freight charges or Insurance charges) that are associated with this shipment. - - - - - Specifies which kind of charge is being recorded in the preceding field. - - - - - Any packing costs that are associated with this shipment. - - - - - Any handling costs that are associated with this shipment. - - - - - Free-form text. - - - - - Free-form text. - - - - - Free-form text. - - - - - The reason for the shipment. Note: SOLD is not a valid purpose for a Proforma Invoice. - - - - - Additional customer reference data. - - - - - Name of the International Expert that completed the Commercial Invoice different from Sender. - - - - - Required for dutiable international Express or Ground shipment. This field is not applicable to an international PIB(document) or a non-document which does not require a Commercial Invoice - - - - - - - The instructions indicating how to print the Commercial Invoice( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies the usage and identification of a customer supplied image to be used on this document. - - - - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Name of this commodity. - - - - - Total number of pieces of this commodity - - - - - Complete and accurate description of this commodity. - - 450 - - - - - - Country code where commodity contents were produced or manufactured in their final form. - - 2 - - - - - - - Unique alpha/numeric representing commodity item. - At least one occurrence is required for US Export shipments if the Customs Value is greater than $2500 or if a valid US Export license is required. - - - 14 - - - - - - Total weight of this commodity. 1 explicit decimal position. Max length 11 including decimal. - - - - - This field is used for enterprise transactions. - - - - - Unit of measure used to express the quantity of this commodity line item. - - 3 - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - Value of each unit in Quantity. Six explicit decimal positions, Max length 18 including decimal. - - - - - - Total customs value for this line item. - It should equal the commodity unit quantity times commodity unit value. - Six explicit decimal positions, max length 18 including decimal. - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - Applicable to US export shipping only. - - 12 - - - - - - - Date of expiration. Must be at least 1 day into future. - The date that the Commerce Export License expires. Export License commodities may not be exported from the U.S. on an expired license. - Applicable to US Export shipping only. - Required only if commodity is shipped on commerce export license, and Export License Number is supplied. - - - - - - - An identifying mark or number used on the packaging of a shipment to help customers identify a particular shipment. - - - 15 - - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - Specifies the results of processing for the COD special service. - - - - - - - - - - - The identifier for all clearance documents associated with this shipment. - - - - - - - - Completed package-level hazardous commodity information for a single package. - - - - - A unique reference id that matches the package to a package configuration. This is populated if the client provided a package configuration for several packages that have the exact same dangerous goods content. - - - - - - When true indicates that the package can be transported only on a cargo aircraft. - - - - - - Specifies the maximum radiation level from the package (measured in microSieverts per hour at a distance of one meter from the external surface of the package, divided by 10). - - - - - Specifies the label that is to be put on a package containing radioactive material. The label type is determined in accordance with the Transportation of Dangerous Goods Act and indicates the type of radioactive material being handled as well as the relative risk. - - - - - Documents the kinds and quantities of all hazardous commodities in the current package. - - - - - - - Computed shipment level hazardous commodity information. - - - - - - - This contains the ADR License information, which identifies the license number and ADR category under which the customer is allowed to ship. - - - - - - - - - Specifies the total number of packages containing hazardous commodities in small exceptions. - - - - - - - - - Identifies the branded location name, the hold at location phone number and the address of the location. - - - - - Identifies the type of FedEx location. - - - - - - - - - The package sequence number of this package in a multiple piece shipment. - - - - - The Tracking number and form id for this package. - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - Oversize class for this package. - - - - - All package-level rating data for this package, which may include data for multiple rate types. - - - - - - The label image or printer commands to print the label. - - - - - All package-level shipping documents (other than labels and barcodes). For use in loads after January, 2008. - - - - - Specifies the information associated with this package that has COD special service in a ground shipment. - - - - - Actual signature option applied, to allow for cases in which the original value conflicted with other service features in the shipment. - - - - - - Documents the kinds and quantities of all hazardous commodities in the current package, using updated hazardous commodity description data. - - - - - - - - - Indicates whether or not this is a US Domestic shipment. - - - - - Indicates the carrier that will be used to deliver this shipment. - - - - - The master tracking number and form id of this multiple piece shipment. This information is to be provided for each subsequent of a multiple piece shipment. - - - - - Description of the FedEx service used for this shipment. Currently not supported. - - 70 - - - - - - Description of the packaging used for this shipment. Currently not supported. - - 40 - - - - - - - Only used with pending shipments. - - - - - Only used in the reply to tag requests. - - - - - Provides reply information specific to SmartPost shipments. - - - - - Computed shipment level information about hazarous commodities. - - - - - All shipment-level rating data for this shipment, which may include data for multiple rate types. - - - - - Returns the default holding location information when HOLD_AT_LOCATION special service is requested and the client does not specify the hold location address. - - - - - Returns any defaults or updates applied to RequestedShipment.exportDetail.exportComplianceStatement. - - - - - - All shipment-level shipping documents (other than labels and barcodes). - - - - - - - Package level details about this package. - - - - - - - Provides reply information specific to SmartPost shipments. - - - - - Identifies the carrier that will pick up the SmartPost shipment. - - - - - Indicates whether the shipment is deemed to be machineable, based on dimensions, weight, and packaging. - - - - - - - Provides reply information specific to a tag request. - - - - - . - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - FEDEX INTERNAL USE ONLY: for use by INET. - - - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - 1 of 12 possible zones to position data. - - - - - The identifiying text for the data in this zone. - - - - - A reference to a field in either the request or reply to print in this zone following the header. - - - - - A literal value to print after the header in this zone. - - - - - - - The descriptive data for a point-of-contact person. - - - - - Client provided identifier corresponding to this contact information. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies a toll free number, if any, associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - Content Record. - - - - - Part Number. - - - - - Item Number. - - - - - Received Quantity. - - - - - Description. - - - - - - - Reply to the Close Request transaction. The Close Reply bring back the ASCII data buffer which will be used to print the Close Manifest. The Manifest is essential at the time of pickup. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Create Pending Shipment Request - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Currency exchange rate information. - - - - - The currency code for the original (converted FROM) currency. - - - - - The currency code for the final (converted INTO) currency. - - - - - Multiplier used to convert fromCurrency units to intoCurrency units. - - - - - - - - - Indicates the type of custom delivery being requested. - - - - - Time by which delivery is requested. - - - - - Range of dates for custom delivery request; only used if type is BETWEEN. - - - - - Date for custom delivery request; only used for types of ON, BETWEEN, or AFTER. - - - - - - - - - - - - - - - Data required to produce a custom-specified document, either at shipment or package level. - - - - - Common information controlling document production. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Identifies the formatting specification used to construct this custom document. - - - - - Identifies the individual document specified by the client. - - - - - If provided, thermal documents will include specified doc tab content. If omitted, document will be produced without doc tab content. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified barcode symbology. - - - - - - - - - Width of thinnest bar/space element in the barcode. - - - - - - - - Solid (filled) rectangular area on label. - - - - - - - - - Valid values for CustomLabelCoordinateUnits - - - - - - - - - - - - - - - - - - Image to be included from printer's memory, or from a local file for offline clients. - - - - - - Printer-specific index of graphic image to be printed. - - - - - Fully-qualified path and file name for graphic image to be printed. - - - - - - - - - Horizontal position, relative to left edge of custom area. - - - - - Vertical position, relative to top edge of custom area. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified printer font (for thermal labels) or generic font/size (for plain paper labels). - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - Generic font name for use with plain paper labels. - - - - - Generic font size for use with plain paper labels. - - - - - - - - - - - - - - - - - - - - Reference information to be associated with this package. - - - - - The reference type to be associated with this reference data. - - - - - - - - The types of references available for use. - - - - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default is former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - Defines any custom content to print on the label. - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - Controls which data/sections will be suppressed. - - - - - For customers producing their own Ground labels, this field specifies which secondary barcode will be printed on the label; so that the primary barcode produced by FedEx has the correct SCNC. - - - - - - Controls the number of additional copies of supplemental labels. - - - - - This value reduces the default quantity of destination/consignee air waybill labels. A value of zero indicates no change to default. A minimum of one copy will always be produced. - - - - - - - - - - Interacts both with properties of the shipment and contractual relationship with the shipper. - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - - - - - - - - - This provides the information necessary to identify the different statements, declarations, acts, and/or certifications that apply to this shipment. - - - - - This indicates the different statements, declarations, acts, and/or certifications that apply to this shipment. - - - - - Specifies the NAFTA low value statement information. - - - - - - - This indicates the different statements, declarations, acts, and certifications that may apply to a shipment. - - - - - - - - - - - Specifies additional description about customs options. This is a required field when the customs options type is "OTHER". - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Describes an approved container used to package dangerous goods commodities. This does not describe any individual inner receptacles that may be within this container. - - - - - Indicates whether there are additional inner receptacles within this container. - - - - - Indicates the type of this dangerous goods container, as specified by the IATA packing instructions. For example, steel cylinder, fiberboard box, plastic jerrican and steel drum. - - - - - Indicates the packaging type of the container used to package the radioactive materials. - - - - - Indicates the number of occurrences of this container with identical dangerous goods configuration. - - - - - Documents the kinds and quantities of all hazardous commodities in the current container. - - - - - - - The descriptive data required for a FedEx shipment containing dangerous goods (hazardous materials). - - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - Indicates which kinds of hazardous content are in the current package. - - - - - Indicates whether there is additional customer provided packaging enclosing the approved dangerous goods containers. - - - - - Identifies the configuration of this dangerous goods package. The common configuration is represented at the shipment level. - - - - - Indicates one or more containers used to pack dangerous goods commodities. - - - - - Description of the packaging of this commodity, suitable for use on OP-900 and OP-950 forms. - - - - - Name, title and place of the signatory for this shipment. - - - - - Telephone number to use for contact in the event of an emergency. - - - - - Offeror's name or contract number, per DOT regulation. - - - - - Specifies the contact of the party responsible for handling the infectious substances, if any, in the dangerous goods shipment. - - - - - Specifies additional handling information for the current package. - - - - - Specifies the radioactivity detail for the current package, if the package contains radioactive materials. - - - - - - - - - - - - The instructions indicating how to print the 1421c form for dangerous goods shipment. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Specifies that name, title and place of the signatory responsible for the dangerous goods shipment. - - - - - - - Indicates the place where the form is signed. - - - - - - - - - The beginning date in a date range. - - - - - The end date in a date range. - - - - - - - Valid values for DayofWeekType - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to delete a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The timestamp of the shipment request. - - - - - Identifies the FedEx tracking number of the package being cancelled. - - - - - Determines the type of deletion to be performed in relation to package level vs shipment level. - - - - - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Only used for tags which had FedEx Express services. - - - - - Only used for tags which had FedEx Express services. - - - - - If the original ProcessTagRequest specified third-party payment, then the delete request must contain the same pay type and payor account number for security purposes. - - - - - Also known as Pickup Confirmation Number or Dispatch Number - - - - - - - Specifies the type of deletion to be performed on a shipment. - - - - - - - - - - - - - - Specifies the tracking id for the return, if preassigned. - - - - - - - Data required to complete the Destionation Control Statement for US exports. - - - - - List of applicable Statment types. - - - - - Comma-separated list of up to four country codes, required for DEPARTMENT_OF_STATE statement. - - - - - Name of end user, required for DEPARTMENT_OF_STATE statement. - - - - - - - Used to indicate whether the Destination Control Statement is of type Department of Commerce, Department of State or both. - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - - - The DocTabContentType options available. - - - - - The DocTabContentType should be set to ZONE001 to specify additional Zone details. - - - - - The DocTabContentType should be set to BARCODED to specify additional BarCoded details. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Zone number can be between 1 and 12. - - - - - Header value on this zone. - - - - - Reference path to the element in the request/reply whose value should be printed on this zone. - - - - - Free form-text to be printed in this zone. - - - - - Justification for the text printed on this zone. - - - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. - - - - - - - - - - - - Describes specific information about the email label shipment. - - - - - Notification email will be sent to this email address - - - - - Message to be sent in the notification email - - - - - - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - Specifies whether/how email notifications are grouped. - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - The descriptive data for a FedEx email notification recipient. - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - Identifies the set of valid email notification recipient types. For SHIPPER, RECIPIENT and BROKER the email address asssociated with their definitions will be used, any email address sent with the email notification for these three email notification recipient types will be ignored. - - - - - - - - - - - - - - - - - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Electronic Trade document references used with the ETD special service. - - - - - Indicates the types of shipping documents produced for the shipper by FedEx (see ShippingDocumentSpecification) which should be copied back to the shipper in the shipment result data. - - - - - - - - The instructions indicating how to print the Export Declaration. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Country specific details of an International shipment. - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US). - - - - - This field is applicable only to Canada export non-document shipments of any value to any destination. No special characters allowed. - - 10 - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - - - Details specific to an Express freight shipment. - - - - - Indicates whether or nor a packing list is enclosed. - - - - - - Total shipment pieces. - e.g. 3 boxes and 3 pallets of 100 pieces each = Shippers Load and Count of 303. - Applicable to International Priority Freight and International Economy Freight. - Values must be in the range of 1 - 99999 - - - - - - Required for International Freight shipping. Values must be 8- 12 characters in length. - - 12 - - - - - - - - Identifies a kind of FedEx facility. - - - - - - - - - - - - - - - Data required to produce the Freight handling-unit-level address labels. Note that the number of UNIQUE labels (the N as in 1 of N, 2 of N, etc.) is determined by total handling units. - - - - - - Indicates the number of copies to be produced for each unique label. - - - - - Specifies the quadrant of the page on which the label printing will start. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - - - - - Individual charge which contributes to the total base charge for the shipment. - - - - - Freight class for this line item. - - - - - Effective freight class used for rating this line item. - - - - - NMFC Code for commodity. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - Rate or factor applied to this line item. - - - - - Identifies the manner in which the chargeRate for this line item was applied. - - - - - The net or extended charge for this line item. - - - - - - - Specifies the way in which base charges for a Freight shipment or shipment leg are calculated. - - - - - - - - - - - - - - - - - These values represent the industry-standard freight classes used for FedEx Freight and FedEx National Freight shipment description. (Note: The alphabetic prefixes are required to distinguish these values from decimal numbers on some client platforms.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Date for all Freight guarantee types. - - - - - - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - - - - - Rate data specific to FedEx Freight or FedEx National Freight services. - - - - - A unique identifier for a specific rate quotation. - - - - - Specifies whether the rate quote was automated or manual. - - - - - Specifies how total base charge is determined. - - - - - Freight charges which accumulate to the total base charge for the shipment. - - - - - Human-readable descriptions of additional information on this shipment rating. - - - - - - - Additional non-monetary data returned with Freight rates. - - - - - Unique identifier for notation. - - - - - Human-readable explanation of notation. - - - - - - - Specifies the type of rate quote - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Account number used with FEDEX_FREIGHT service. - - - - - Used for validating FedEx Freight account number and (optionally) identifying third party payment on the bill of lading. - - - - - Used in connection with "Send Bill To" (SBT) identification of customer's account used for billing. - - - - - Identification values to be printed during creation of a Freight bill of lading. - - - - - Indicates the role of the party submitting the transaction. - - - - - Designates the terms of the "collect" payment for a Freight Shipment. - - - - - Identifies the declared value for the shipment - - - - - Identifies the declared value units corresponding to the above defined declared value - - - - - - Identifiers for promotional discounts offered to customers. - - - - - Total number of individual handling units in the entire shipment (for unit pricing). - - - - - Estimated discount rate provided by client for unsecured rate quote. - - - - - Total weight of pallets used in shipment. - - - - - Overall shipment dimensions. - - - - - Description for the shipment. - - - - - Specifies which party will pay surcharges for any special services which support split billing. - - - - - Must be populated if any line items contain hazardous materials. - - - - - - Details of the commodities in the shipment. - - - - - - - Description of an individual commodity or class of content in a shipment. - - - - - Freight class for this line item. - - - - - FEDEX INTERNAL USE ONLY: for FedEx system that estimate freight class from customer-provided dimensions and weight. - - - - - Number of individual handling units to which this line applies. (NOTE: Total of line-item-level handling units may not balance to shipment-level total handling units.) - - - - - Specification of handling-unit packaging for this commodity or class line. - - - - - Number of pieces for this commodity or class line. - - - - - NMFC Code for commodity. - - - - - Indicates the kind of hazardous material content in this line item. - - - - - For printed reference per line item. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - FED EX INTERNAL USE ONLY - Individual line item dimensions. - - - - - Volume (cubic measure) for this commodity or class line. - - - - - - - Indicates the role of the party submitting the transaction. - - - - - - - - - Specifies which party will be responsible for payment of any surcharges for Freight special services for which split billing is allowed. - - - - - Identifies the special service. - - - - - Indicates who will pay for the special service. - - - - - - - Data required to produce a General Agency Agreement document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - - Represents features of FedEx Ground delivery for which the shipment is eligible. - - - - - - - - - - - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - This describes the inner receptacle details for a hazardous commodity within the dangerous goods container. - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies the details of any radio active materials within the commodity. - - - - - - - Identifies and describes an individual hazardous commodity. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - - - - - - - Indicates any special processing options to be applied to the description of the dangerous goods commodity. - - - - - Information related to quantity limitations and operator or state variations as may be applicable to the dangerous goods commodity. - - - - - - - Specifies any special processing to be applied to the dangerous goods commodity description validation. - - - - - - - - This describes information about the inner receptacles for the hazardous commodity in a particular dangerous goods container. - - - - - This specifies the quantity contained in the inner receptacle. - - - - - - - Specifies how the commodity is to be labeled. - - - - - - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies how the customer wishes the label text to be handled for this commodity in this package. - - - - - Text used in labeling the commodity under control of the labelTextOption field. - - - - - - - Indicates which kind of hazardous content is being reported. - - - - - - - - - - - - - Identifies number and type of packaging units for hazardous commodities. - - - - - Number of units of the type below. - - - - - Units in which the hazardous commodity is packaged. - - - - - - - Specifies documentation and limits for validation of an individual packing group/category. - - - - - - Coded specification for how commodity is to be packed. - - - - - - - Identifies DOT packing group for a hazardous commodity. - - - - - - - - - - - Identifies amount and units for quantity of hazardous commodities. - - - - - Number of units of the type below. - - - - - Units by which the hazardous commodity is measured. For IATA commodity, the units values are restricted based on regulation type. - - - - - Specifies which measure of quantity is to be validated. - - - - - - - Specifies the measure of quantity to be validated against a prescribed limit. - - - - - - - - - Identifies the source of regulation for hazardous commodity data. - - - - - - - - - - - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. - - - - - Contact phone number for recipient of shipment. - - - - - Contact and address of FedEx facility at which shipment is to be held. - - - - - Type of facility at which package/shipment is to be held. - - - - - - - The descriptive data required by FedEx for home delivery services. - - - - - The type of Home Delivery Premium service being requested. - - - - - Required for Date Certain Home Delivery. - - - - - Required for Date Certain and Appointment Home Delivery. - - 15 - - - - - - - - The type of Home Delivery Premium service being requested. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The type of International shipment. - - - - - - - - - - - - - - - Specifies the type of label to be returned. - - - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - - - - - Relative to normal orientation for the printer. - - - - - - - - - - - Description of shipping label to be returned in the reply - - - - - Specifies how to create, organize, and return the document. - - - - - Specify type of label to be returned - - - - - Specifies the image format used for a shipping document. - - - - - For thermal printer lables this indicates the size of the label and the location of the doc tab if present. - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - If present, this contact and address information will replace the return address information on the label. - - - - - Allows customer-specified control of label content. - - - - - - - For thermal printer labels this indicates the size of the label and the location of the doc tab if present. - - - - - - - - - - - - - - - - - - - - - - - Identifies the Liability Coverage Amount. For Jan 2010 this value represents coverage amount per pound - - - - - - - - - - - - - - - License or Permit Number. - - - - - Specifies the effective date of the license. - - - - - Specifies the expiration date of the license. - - - - - - - Represents a one-dimensional measurement in small units (e.g. suitable for measuring a package or document), contrasted with Distance, which represents a large one-dimensional measurement (e.g. distance between cities). - - - - - The numerical quantity of this measurement. - - - - - The units for this measurement. - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - - - - - - - Identifies which type minimum charge was applied. - - - - - - - - - - - - The descriptive data for the medium of exchange for FedEx services. - - - - - Identifies the currency of the monetary amount. - - 3 - - - - - - Identifies the monetary amount. - - - - - - - Data required to produce a Certificate of Origin document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - Contact information for "Authorized Signature" area of form. - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - Date range over which RVC net cost was calculated. - - - - - - - - - - - - - - - Specifies the information necessary for printing the NAFTA Low Value statement on customs documentation. - - - - - Specifies the NAFTA statement role. - - - - - - - Net cost method used. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The instructions indicating how to print the OP-900 form for hazardous materials packages. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Identifies which reference type (from the package's customer references) is to be used as the source for the reference on this OP-900. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - Data field to be used when a name is to be printed in the document instead of (or in addition to) a signature image. - - - - - - - - - Position of operational instruction element. - - - - - Content corresponding to the operational instruction. - - - - - - - The oversize class types. - - - - - - - - - - Each instance of this data type represents the set of barcodes (of all types) which are associated with a specific package. - - - - - Binary-style barcodes for this package. - - - - - String-style barcodes for this package. - - - - - - - Package-level data required for labeling and/or movement. - - - - - Human-readable text for pre-January 2011 clients. - - - - - Human-readable content for use on a label. - - - - - The operational barcodes pertaining to the current package. - - - - - The FedEx internal code that represents the service and/or features of service for the current package moving under a FedEx Ground service. - - - - - - - Data for a package's rates, as calculated per a specific rate type. - - - - - Type used for this specific set of rate data. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - The weight that was used to calculate the rate. - - - - - The dimensional weight of this package (if greater than actual). - - - - - The oversize weight of this package (if the package is oversize). - - - - - The transportation charge only (prior to any discounts applied) for this package. - - - - - The sum of all discounts on this package. - - - - - This package's baseCharge - totalFreightDiscounts. - - - - - The sum of all surcharges on this package. - - - - - This package's netFreight + totalSurcharges (not including totalTaxes). - - - - - The sum of all taxes on this package. - - - - - This package's netFreight + totalSurcharges + totalTaxes. - - - - - The total sum of all rebates applied to this package. - - - - - All rate discounts that apply to this package. - - - - - All rebates that apply to this package. - - - - - All surcharges that apply to this package (either because of characteristics of the package itself, or because it is carrying per-shipment surcharges for the shipment of which it is a part). - - - - - All taxes applicable (or distributed to) this package. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - - - This class groups together for a single package all package-level rate data (across all rate types) as part of the response to a shipping request, which groups shipment-level data together and groups package-level data by package. - - - - - This rate type identifies which entry in the following array is considered as presenting the "actual" rates for the package. - - - - - The "list" net charge minus "actual" net charge. - - - - - Each element of this field provides package-level rate data for a specific rate type. - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Ground shipments only. - - - - - - - - - - - - - - - These special services are available at the package level for some or all service types. If the shipper is requesting a special service which requires additional data, the package special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment or package. - - - - - For use with FedEx Ground services only; COD must be present in shipment's special services. - - - - - Descriptive data required for a FedEx shipment containing dangerous materials. This element is required when SpecialServiceType.DANGEROUS_GOODS or HAZARDOUS_MATERIAL is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for a FedEx shipment containing dry ice. This element is required when SpecialServiceType.DRY_ICE is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx signature services. This element is required when SpecialServiceType.SIGNATURE_OPTION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Priority Alert service. This element is required when SpecialServiceType.PRIORITY_ALERT is present in the SpecialServiceTypes collection. - - - - - - - Identifies the collection of available FedEx or customer packaging options. - - - - - - - - - - - - - - - - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data for the monetary compensation given to FedEx for services rendered to the customer. - - - - - Identifies the method of payment for a service. See PaymentType for list of valid enumerated values. - - - - - Descriptive data identifying the party responsible for payment for a service. - - - - - - - Identifies the method of payment for a service. - - - - - - - - - - - - The descriptive data identifying the party responsible for payment for a service. - - - - - - - - This information describes how and when a pending shipment may be accessed for completion. - - - - - Only for pending shipment type of "EMAIL" - - - - - Only for pending shipment type of "EMAIL" - - - - - Only for pending shipment type of "EMAIL" - - - - - This element is currently not supported and is for the future use. - - - - - - - This information describes the kind of pending shipment being requested. - - - - - Identifies the type of FedEx pending shipment - - - - - Date after which the pending shipment will no longer be available for completion. - - - - - Only used with type of EMAIL. - - - - - - - Identifies the type of service for a pending shipment. - - - - - - - - - - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This class describes the pickup characteristics of a shipment (e.g. for use in a tag request). - - - - - - - - Identifies the type of Pickup request - - - - - Identifies the type of source for Pickup request - - - - - - - Identifies the type of source for pickup request service. - - - - - - - - - Identifies the type of pickup request service. - - - - - - - - - Identifies the type of pricing used for this shipment. - - - - - - - - - - - - - - - - - - - - Represents a reference identifier printed on Freight bills of lading - - - - - - - - - Identifies a particular reference identifier printed on a Freight bill of lading. - - - - - - - - - - - - - - - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - Empty unless error label behavior is PACKAGE_ERROR_LABELS and one or more errors occured during transaction processing. - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - - - - - - - - - Indicates the packaging type of the container used to package radioactive hazardous materials. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates whether packaging type "EXCEPTED" or "EXCEPTED_PACKAGE" is for radioactive material in reportable quantity. - - - - - - - - - Indicates the reason that a dim divisor value was chose. - - - - - - - - - - - - Identifies a discount applied to the shipment. - - - - - Identifies the type of discount applied to the shipment. - - - - - - The amount of the discount applied to the shipment. - - - - - The percentage of the discount applied to the shipment. - - - - - - - The type of the discount. - - - - - - - - - - - - - Selects the value from a set of rate data to which the percentage is applied. - - - - - - - - - - - Identifies the type(s) of rates to be returned in the reply. - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - The weight method used to calculate the rate. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - Specifies the kind of identification being used. - - - - - Contains the actual ID value, of the type specified above. - - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin - - - - - - - - - - Describes the vertical position of an item relative to another item. - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - - Specifies the declared value for carriage of the package. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the package. This field is only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case total weight and packageCount on the shipment will be used to determine this value. - - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - The descriptive data for the shipment being tendered to FedEx. - - - - - Identifies the date and time the package is tendered to FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the shipment based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). There is also a UTC offset component indicating the number of hours/mainutes from UTC (e.g 2006-06-26T17:00:00-0400 is defined form June 26, 2006 5:00 pm Eastern Time). - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. See DropoffType for list of valid enumerated values. - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - Identifies the total weight of the shipment being conveyed to FedEx.This is only applicable to International shipments and should only be used on the first package of a mutiple piece shipment.This value contains 1 explicit decimal position - - - - - Specifies the total declared value for carriage of the shipment. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the shipment. - - - - - This attribute indicates the currency the caller requests to have used in all returned monetary values (when a choice is possible). - - - - - Descriptive data identifying the party responsible for shipping the package. Shipper and Origin should have the same address. - - - - - Descriptive data identifying the party receiving the package. - - - - - A unique identifier for a recipient location - - 10 - - - - - - Physical starting address for the shipment, if different from shipper's address. - - - - - Descriptive data indicating the method and means of payment to FedEx for providing shipping services. - - - - - Descriptive data regarding special services requested by the shipper for this shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Details specific to an Express freight shipment. - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Used with Ground Home Delivery and Freight. - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - Customs clearance data, used for both international and intra-country shipping. - - - - - For use in "process tag" transaction. - - - - - Specifies the characteristics of a shipment pertaining to SmartPost services. - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - Details about the image format and printer type the label is to returned in. - - - - - Contains data used to create additional (non-label) shipping documents. - - - - - Specifies whether and what kind of rates the customer wishes to have quoted on this shipment. The reply will also be constrained by other data on the shipment and customer. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - Only used with multiple-transaction shipments, to identify the master package in a multi-piece shipment. - - - - - The total number of packages in the entire shipment (even when the shipment spans multiple transactions.) - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the tracking number of the master associated with the return shipment. - - - - - - - - These values are used to control the availability of certain special services at the time when a customer uses the e-mail label link to create a return shipment. - - - - - - - - - Return Email Details - - - - - Phone number of the merchant - - - - - Identifies the allowed (merchant-authorized) special services which may be selected when the subsequent shipment is created. Only services represented in EMailLabelAllowedSpecialServiceType will be controlled by this list. - - - - - - - The instructions indicating how to print the return instructions( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies additional customer provided text to be inserted into the return document. - - - - - - - Information relating to a return shipment. - - - - - The type of return shipment that is being requested. - - - - - Return Merchant Authorization - - - - - Describes specific information about the email label for return shipment. - - - - - - - - The type of return shipment that is being requested. - - - - - - - - - - The "PAYOR..." rates are expressed in the currency identified in the payor's rate table(s). The "RATED..." rates are expressed in the currency of the origin country. Former "...COUNTER..." values have become "...RETAIL..." values, except for PAYOR_COUNTER and RATED_COUNTER, which have been removed. - - - - - - - - - - - - - - - - - - - - Shipping document type. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - June 2011 ITG 121203 IR-RMA number has been removed from this structure and added as a new customer reference type. The structure remains because of the reason field below. - - - - - The reason for the return. - - 60 - - - - - - - - Describes the rotation of an item from its default orientation. - - - - - - - - - - - - - - - - - - - Identifies the collection of available FedEx service options. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - Specifies the data that is common to dangerous goods packages in the shipment. This is populated when the shipment contains packages with identical dangerous goods commodities. - - - - - - - Shipment-level totals of dry ice data across all packages. - - - - - Total number of packages in the shipment that contain dry ice. - - - - - Total shipment dry ice weight for all packages. - - - - - - - Data for a single leg of a shipment's total/summary rates, as calculated per a specific rate type. - - - - - Human-readable text describing the shipment leg. - - - - - Origin for this leg. - - - - - Specifies the location id the origin of shipment leg. - - - - - Destination for this leg. - - - - - Specifies the location id the destination of shipment leg. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - - - - - - - - - - - This is the state of the destination location ID, and is not necessarily the same as the postal state. - - - - - Expected/estimated date of delivery. - - - - - Expected/estimated day of week of delivery. - - - - - Delivery time, as published in Service Guide. - - - - - Committed date of delivery. - - - - - Committed day of week of delivery. - - - - - Standard transit time per origin, destination, and service. - - - - - Maximum expected transit time - - - - - Transit time based on customer eligibility. - - - - - Indicates that this shipment is not eligible for money back guarantee. - - - - - FedEx Ground delivery features for which this shipment may be eligible. - - - - - Text describing planned delivery. - - - - - - - - - - - - - - Data for a shipment's total/summary rates, as calculated per a specific rate type. The "total..." fields may differ from the sum of corresponding package data for Multiweight or Express MPS. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - Identifies the type of pricing used for this shipment. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - The value used to calculate the weight based on the dimensions. - - - - - Identifies the type of dim divisor that was applied. - - - - - Specifies a fuel surcharge percentage. - - - - - The weight used to calculate these rates. - - - - - Sum of dimensional weights for all packages. - - - - - The total freight charge that was calculated for this package before surcharges, discounts and taxes. - - - - - The total discounts used in the rate calculation. - - - - - The freight charge minus discounts. - - - - - The total amount of all surcharges applied to this shipment. - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - The net charge after applying all discounts and surcharges. - - - - - The total sum of all rebates applied to this shipment. - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Identifies the Rate Details per each leg in a Freight Shipment - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - This class groups together all shipment-level rate data (across all rate types) as part of the response to a shipping request, which groups shipment-level data together and groups package-level data by package. - - - - - This rate type identifies which entry in the following array is considered as presenting the "actual" rates for the shipment. - - - - - The "list" total net charge minus "actual" total net charge. - - - - - Each element of this field provides shipment-level rate totals for a specific rate type. - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Express shipments only. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These special services are available at the shipment level for some or all service types. If the shipper is requesting a special service which requires additional data (such as the COD amount), the shipment special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment (or other shipment-level transaction). - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. This element is required when SpecialServiceType.COD is present in the SpecialServiceTypes collection. - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. This element is required when SpecialServiceType.HOLD_AT_LOCATION is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for FedEx to provide email notification to the customer regarding the shipment. This element is required when SpecialServiceType.EMAIL_NOTIFICATION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Printed Return Label. This element is required when SpecialServiceType.PRINTED_RETURN_LABEL is present in the SpecialServiceTypes collection - - - - - This field should be populated for pending shipments (e.g. e-mail label) It is required by a PENDING_SHIPMENT special service type. - - - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - The descriptive data required for FedEx Home Delivery options. This element is required when SpecialServiceType.HOME_DELIVERY_PREMIUM is present in the SpecialServiceTypes collection - - - - - - Electronic Trade document references. - - - - - Specification for date or range of dates on which delivery is to be attempted. - - - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Shipping Document Type - - - - - Specifies how this document image/file is organized. - - - - - - The name under which a STORED or DEFERRED document is written. - - - - - Specifies the image type of this shipping document. - - - - - Specifies the image resolution in DPI (dots per inch). - - - - - Can be zero for documents whose disposition implies that no content is included. - - - - - One or more document parts which make up a single logical document, such as multiple pages of a single form. - - - - - - - Each occurrence of this class specifies a particular way in which a kind of shipping document is to be produced and provided. - - - - - Values in this field specify how to create and return the document. - - - - - Specifies how to organize all documents of this type. - - - - - Specifies how to e-mail document images. - - - - - Specifies how a queued document is to be printed. - - - - - - - Specifies how to return a shipping document to the caller. - - - - - - - - - - - - - - Specifies how to e-mail shipping documents. - - - - - Provides the roles and email addresses for e-mail recipients. - - - - - Identifies the convention by which documents are to be grouped as e-mail attachments. - - - - - - - - - - - - - Specifies an individual recipient of e-mailed shipping document(s). - - - - - Identifies the relationship of this recipient in the shipment. - - - - - Address to which the document is to be sent. - - - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies how to create, organize, and return the document. - - - - - Specifies how far down the page to move the beginning of the image; allows for printing on letterhead and other pre-printed stock. - - - - - - - For those shipping document types which have both a "form" and "instructions" component (e.g. NAFTA Certificate of Origin and General Agency Agreement), this field indicates whether to provide the instructions. - - - - - Governs the language to be used for this individual document, independently from other content returned for the same shipment. - - - - - Identifies the individual document specified by the client. - - - - - - - Specifies how to organize all shipping documents of the same type. - - - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - - - - A single part of a shipping document, such as one page of a multiple-page document whose format requires a separate image per page. - - - - - The one-origin position of this part within a document. - - - - - Graphic or printer commands for this image within a document. - - - - - - - Specifies printing options for a shipping document. - - - - - Provides environment-specific printer identification. - - - - - - - Contains all data required for additional (non-label) shipping documents to be produced in conjunction with a specific shipment. - - - - - Indicates the types of shipping documents requested by the shipper. - - - - - - - Specifies the production of each package-level custom document (the same specification is used for all packages). - - - - - Specifies the production of a shipment-level custom document. - - - - - - This element is currently not supported and is for the future use. (Details pertaining to the GAA.) - - - - - - Specifies the production of the OP-900 document for hazardous materials packages. - - - - - Specifies the production of the 1421c document for dangerous goods shipment. - - - - - Specifies the production of the OP-900 document for hazardous materials. - - - - - Specifies the production of the return instructions document. - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - - - - - The descriptive data required for FedEx delivery signature services. - - - - - Identifies the delivery signature services option selected by the customer for this shipment. See OptionType for the list of valid values. - - - - - Identifies the delivery signature release authorization number. - - 10 - - - - - - - - Identifies the delivery signature services options offered by FedEx. - - - - - - - - - - - - These values are mutually exclusive; at most one of them can be attached to a SmartPost shipment. - - - - - - - - - - - - - - - - - - - - - Data required for shipments handled under the SMART_POST and GROUND_SMART_POST service types. - - - - - - - - - The CustomerManifestId is used to group Smart Post packages onto a manifest for each trailer that is being prepared. If you do not have multiple trailers this field can be omitted. If you have multiple trailers, you - must assign the same Manifest Id to each SmartPost package as determined by its trailer. In other words, all packages on a trailer must have the same Customer Manifest Id. The manifest Id must be unique to your account number for a minimum of 6 months - and cannot exceed 8 characters in length. We recommend you use the day of year + the trailer id (this could simply be a sequential number for that trailer). So if you had 3 trailers that you started loading on Feb 10 - the 3 manifest ids would be 041001, 041002, 041003 (in this case we used leading zeros on the trailer numbers). - - - - - - - - Special circumstance rating used for this shipment. - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - Identifies each surcharge applied to the shipment. - - - - - The type of surcharge applied to the shipment. - - - - - - - The amount of the surcharge applied to the shipment. - - - - - - - - - - - - - The type of the surcharge. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies each tax applied to the shipment. - - - - - The type of tax applied to the shipment. - - - - - - The amount of the tax applied to the shipment. - - - - - - - The type of the tax. - - - - - - - - - - - - - - Specifice the kind of tax or miscellaneous charge being reported on a Commercial Invoice. - - - - - - - - - - - - - The descriptive data for taxpayer identification information. - - - - - Identifies the category of the taxpayer identification number. See TinType for the list of values. - - - - - Identifies the taxpayer identification number. - - 15 - - - - - - Identifies the usage of Tax Identification Number in Shipment processing - - - - - - - - Required for dutiable international express or ground shipment. This field is not applicable to an international PIB (document) or a non-document which does not require a commercial invoice express shipment. - CFR_OR_CPT (Cost and Freight/Carriage Paid TO) - CIF_OR_CIP (Cost Insurance and Freight/Carraige Insurance Paid) - DDP (Delivered Duty Paid) - DDU (Delivered Duty Unpaid) - EXW (Ex Works) - FOB_OR_FCA (Free On Board/Free Carrier) - - - - - - - - - - - - - - - - Identifies the category of the taxpayer identification number. - - - - - - - - - - - - - - - - For use with SmartPost tracking IDs only - - - - - - - - TrackingIdType - - - - - - - - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the set of valid shipment transit time values. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to validate a shipment. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - The mass points are a calculation used by ADR regulations for measuring the risk of a particular hazardous commodity. - - - - - Customer-provided specifications for handling individual commodities. - - - - - - - Identifies and describes an individual hazardous commodity. For 201001 load, this is based on data from the FedEx Ground Hazardous Materials Shipping Guide. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - Fully-expanded descriptive text for a hazardous commodity. - - - - - - - - Coded indications for special requirements or constraints. - - - - - - - - - - - - Specifies the concept of a container used to package dangerous goods commodities. - - - - - Indicates that the quantity of the dangerous goods packaged is permissible for shipping. This is used to ensure that the dangerous goods commodities do not exceed the net quantity per package restrictions. - - - - - Documents the kinds and quantities of all hazardous commodities in the current package. - - - - - - - This definition of variable handling charge detail is intended for use in Jan 2011 corp load. - - - - - - Used with Variable handling charge type of FIXED_VALUE. - Contains the amount to be added to the freight charge. - Contains 2 explicit decimal positions with a total max length of 10 including the decimal. - - - - - - Actual percentage (10 means 10%, which is a mutiplier of 0.1) - - - - - Select the value from a set of rate data to which the percentage is applied. - - - - - Select the type of rate from which the element is to be selected. - - - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The variable handling charge amount calculated based on the requested variable handling charge detail. - - - - - - - The calculated varibale handling charge plus the net charge. - - - - - - - Three-dimensional volume/cubic measurement. - - - - - - - - - Units of three-dimensional volume/cubic measure. - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - Identifies the unit of measure associated with a weight value. See the list of enumerated types for valid values. - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/ShipService_v7.wsdl b/fedex/wsdl/ShipService_v7.wsdl deleted file mode 100755 index a36f26e..0000000 --- a/fedex/wsdl/ShipService_v7.wsdl +++ /dev/null @@ -1,4656 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the type of additional labels. - - - - - - - - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - 35 - - - - - - Name of city, town, etc. - - - 35 - 20 - - - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - 14 - - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. This element is required if both the City and StateOrProvinceCode are not present. - - 16 - - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - 100 - - - - - - Identification of a country. - - 2 - - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - - - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to Cancel a Pending shipment. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The FedEx account number assigned to the customer initiating the request. - - 12 - - - - - - Identifies the unique client device submitting the request. This number is assigned by FedEx and identifies the unique device from which the request is originating. - - 10 - - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - Identifies what freight charges should be added to the COD collect amount. - - - - - - - - - - - - - - - - - - - - - Identifies the type of funds FedEx should collect upon package delivery. - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - Identifies if freight charges are to be added to the COD amount. This element determines which freight charges should be added to the COD collect amount. See CodAddTransportationChargesType for the list of valid enumerated values. - - - - - Identifies the type of funds FedEx should collect upon package delivery. See CodCollectionType for the list of valid enumerated values. - - - - - Descriptive data about the recipient of the COD shipment. - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - Currently not supported. - - TBD - - - - - - The description of the FedEx service type used for the COD return shipment. Currently not supported. - - 70 - - - - - - The description of the packaging used for the COD return shipment. - - 40 - - - - - - Currently not supported. - - TBD - - - - - - Currently not supported. - - - - - Currently not supported. - - - - - The CodRoutingDetail element will contain the COD return tracking number and form id. In the case of a COD multiple piece shipment these will need to be inserted in the request for the last piece of the multiple piece shipment. - The service commitment is the only other element of the RoutingDetail that is used for a CodRoutingDetail. - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through FedEx System. Customers are responsible for printing their own Commercial Invoice. Commercial Invoice support consists of a maximum of 99 commodity line items. - - - - - Commercial Invoice comments to be uploaded to customs. - - 444 - - - - - - Format: Two explicit decimal positions max length 19 including decimal. - Required if Terms Of Sale is CFR or CIF. - This charge should be added to the total customs value amount. - - - - - - Format: Two explicit decimal positions max length 19 including decimal. - This charge should be added to the total customs value amount. - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - Customer assigned invoice number. - - 15 - - - - - - Defines the terms of the sale. - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - ? - - - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Name of this commodity. - - - - - Total number of pieces of this commodity - - - - - Complete and accurate description of this commodity. - - 450 - - - - - - Country code where commodity contents were produced or manufactured in their final form. - - 2 - - - - - - - Unique alpha/numeric representing commodity item. - At least one occurrence is required for US Export shipments if the Customs Value is greater than $2500 or if a valid US Export license is required. - - - 14 - - - - - - Total weight of this commodity. 1 explicit decimal position. Max length 11 including decimal. - - - - - Number of units of a commodity in total number of pieces for this line item. Max length is 9 - - - - - Unit of measure used to express the quantity of this commodity line item. - - 3 - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - Value of each unit in Quantity. Six explicit decimal positions, Max length 18 including decimal. - - - - - Total customs value for this line item. - It should equal the commodity unit quantity times commodity unit value. - Six explicit decimal positions, max length 18 including decimal. - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - Applicable to US export shipping only. - - 12 - - - - - - Date of expiration. Must be at least 1 day into future. - The date that the Commerce Export License expires. Export License commodities may not be exported from the U.S. on an expired license. - Applicable to US Export shipping only. - Required only if commodity is shipped on commerce export license, and Export License Number is supplied. - - - - - - An identifying mark or number used on the packaging of a shipment to help customers identify a particular shipment. - - - 15 - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - - - The package sequence number of this package in a multiple piece shipment. - - - - - The Tracking number and form id for this package. - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - Oversize class for this package. - - - - - The rating information for this package. Note, this is a courtesy rate and may be different from what is invoiced. - - - - - The data that is used to from the Astra and 2DCommon barcodes for the label.. - - - - - The textual description of the special service applied to the package. - - - - - The label image or printer commands to print the label. - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Information about the COD return shipment. - - - - - The actual signature option applied to this shipment. This could be different than the signature option requested if a conflict occured with other service features in the shipment. - - - - - - - - - Indicates whether or not this is a US Domestic shipment. - - - - - Indicates the carrier that will be used to deliver this shipment. - - - - - The master tracking number and form id of this multiple piece shipment. This information is to be provided for each subsequent of a multiple piece shipment. - - - - - Description of the FedEx service used for this shipment. Currently not supported. - - 70 - - - - - - Description of the packaging used for this shipment. Currently not supported. - - 40 - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The code indicating the Ground service type and any special services associated with this shipment. Currently not supported. - - - - - Access Details about PendingShipment information. - - - - - Only used in the reply to tag requests. - - - - - Provides reply information specific to SmartPost shipments. - - - - - The rating information for this shipment. Note, this is a courtesy rate and may be different from what is invoiced. - - - - - Information about the COD return shipment. - - - - - Indicates whether or not this shipment is eligible for a money back guarantee. - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US. - - - - - - All shipment-level shipping documents (other than labels and barcodes). - - - - - Package level details about this package. - - - - - - - - - - - - Provides reply information specific to a tag request. - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - 1 of 12 possible zones to position data. - - - - - The identifiying text for the data in this zone. - - - - - A reference to a field in either the request or reply to print in this zone following the header. - - - - - A literal value to print after the header in this zone. - - - - - - - The descriptive data for a point-of-contact person. - - - - - Identifies the contact person's name. - - 35 - - - - - - Identifies the contact person's title. Not currently used. - - - - - Identifies the contact person's company name. - - 35 - - - - - - Identifies the contact person's phone number. - - 15 - - - - - - Identifies the contact person's pager number. - - 15 - - - - - - Identifies the contact person's fax machine phone number. - - 15 - - - - - - Identifies the contact person's email address. - - 120 - - - - - - - - - - - - - - Create Pending Shipment Request - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Reply to the Close Request transaction. The Close Reply bring back the ASCII data buffer which will be used to print the Close Manifest. The Manifest is essential at the time of pickup. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Currency exchange rate information. - - - - - The currency type being converted from. - - - - - The currency type being converted to. - - - - - The resulting amount. - - - - - - - Content Record. - - - - - Part Number. - - - - - Item Number. - - - - - Received Quantity. - - - - - Description. - - - - - - - Reference information to be associated with this package. - - - - - The reference type to be associated with this reference data. - - - - - - - - The types of references available for use. - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - Defines any custom content to print on the label. - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - Data to exclude from printing on the label. - - - - - - - - - - - - - - - - - - - - - - - - - - Valid values for CustomLabelCoordinateUnits - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - - - - The descriptive data required for a FedEx shipment containing dangerous goods (hazardous materials). - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - - - - - - - - - The beginning date in a date range. - - - - - The end date in a date range. - - - - - - - Valid values for DayofWeekType - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to delete a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The timestamp of the shipment request. - - - - - Identifies the FedEx tracking number of the package being cancelled. - - - - - Determines the type of deletion to be performed in relation to package level vs shipment level. - - - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Express Location Identifier. - - - - - The date FedEx will attempt to pick up the shipment from the Sender. - - - - - - Also known as Pickup Confirmation Number or Dispatch Number - - - - - - - Valid values for DeletionControlType - - - - - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - List of applicable Statment types. - - - - - Countries this shipment is destined for. - - - - - Department of State End User. - - - - - - - Used to indicate whether the Destination Control Statement is of type Department of Commerce, Department of State or both. - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - - - - - - - - - - - - - - - The DocTabContentType options available. - - - - - The DocTabContentType should be set to ZONE001 to specify additional Zone details. - - - - - The DocTabContentType should be set to BARCODED to specify additional BarCoded details. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Zone number can be between 1 and 12. - - - - - Header value on this zone. - - - - - Reference path to the element in the request/reply whose value should be printed on this zone. - - - - - Free form-text to be printed in this zone. - - - - - Justification for the text printed on this zone. - - - - - - - - - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. - - - - - - - - - - - - Describes the special services the merchant will allow on a return shipment. - - - - - - - - - Describes specific information about the email label shipment. - - - - - Notification email will be sent to this email address - - - - - Message to be sent in the notification email - - - - - - - The descriptive data required for FedEx to provide email notification to the customer regarding the shipment. - - - - - Identifies the message text to be sent in the email notification. - - 120 - - - - - - The descriptive data element for the collection of email recipients. - - - - - - - A unique format can be specified for each email address indicated. The format will apply to notification emails sent to a particular email address. - - - - - - - - - - The descriptive data for a FedEx email notification recipient. - - - - - Identifies the email notification recipient type. See EMailNotificationRecipientType for a list of valid enumerated values. - - - - - Identifies the email address of the notification recipient. - - 120 - - - - - - Identifies if an email notification should be sent to the recipient when the package is shipped. - - - - - Identifies if an email notification should be sent to the recipient when an exception occurs during package movement from origin to destination. - - - - - Identifies if an email notification should be sent to the recipient when the package is delivered. - - - - - A unique format can be specified for each email address indicated. The format will apply to notification emails sent to a particular email address.. - - - - - Indicates the language the notification is expressed in. - - - - - - - Identifies the set of valid email notification recipient types. For SHIPPER, RECIPIENT and BROKER the email address asssociated with their definitions will be used, any email address sent with the email notification for these three email notification recipient types will be ignored. - - - - - - - - - - - Country specific details of an International shipment. - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - Required only if B13AFilingOption is one of the following: - FILED_ELECTRONICALLY - MANUALLY_ATTACHED - SUMMARY_REPORTING - If B13AFilingOption = NOT_REQUIRED, this field should contain a valid B13A Exception Number. - - - 50 - - - - - - This field is applicable only to Canada export non-document shipments of any value to any destination. No special characters allowed. - - 10 - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - - - Details specific to an Express freight shipment. - - - - - Indicates whether or nor a packing list is enclosed. - - - - - Total shipment pieces. - e.g. 3 boxes and 3 pallets of 100 pieces each = Shippers Load and Count of 303. - Applicable to International Priority Freight and International Economy Freight. - Values must be in the range of 1 - 99999 - - - - - - Required for International Freight shipping. Values must be 8- 12 characters in length. - - 12 - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - to be included in the OP-950 (Hazardous Materials Certificate) returned in Close reply - - - - - which broad class (as established by the United States DOT) the contents of this shipment falls into; The user should be aware that these (up to three) 50-character elements will actually be formatted on the certificate in a 25-character-wide column on up to six lines; Up to 25 characters of the first element will appear on the first line, and any additional characters starting with the 26th will appear on a second line. The first 25 of the second element, if it exists, will appear on a third line, and any additional characters starting with the 26th will appear on the fourth line. The first 25 characters of the third element will appear on a fifth line, and any additional characters starting with the 26th will appear on a sixth line. - - 50 - - - - - - which broad class (as established by the United States Department of Transportation) the contents of this shipment falls into. - - 25 - - - - - - ID Number (UN or NA number), including prefix. - - 11 - - - - - - Type of D.O.T. diamond hazard label, or "Ltd. Qty.", or Exemption Number. - - 50 - - - - - - materials in certain classes, the Packing Group signifies the degree of hazard. - - 3 - - - - - - Quantity (in the given unites) of dangerous goods in shipment. - - - - - - - - - - Units in which the Quantity is expressed. - - 4 - - - - - - 24-hour emergency response contact phone number. - - 15 - - - - - - 24-hour emergency response contact name. - - 50 - - - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. - - - - - Identifies a telephone number. - - 15 - - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data required by FedEx for home delivery services. - - - - - The type of Home Delivery Premium service being requested. - - - - - Required for Date Certain Home Delivery. - - - - - Required for Date Certain and Appointment Home Delivery. - - 15 - - - - - - - - The type of Home Delivery Premium service being requested. - - - - - - - - - - - - Descriptive data identifying the Broker responsible for the shipment. - Required if BROKER_SELECT_OPTION is requested in Special Services. - - - - - - Applicable only for Commercial Invoice. If the consignee and importer are not the same, the Following importer fields are required. - Importer/Contact/PersonName - Importer/Contact/CompanyName - Importer/Contact/PhoneNumber - Importer/Address/StreetLine[0] - Importer/Address/City - Importer/Address/StateOrProvinceCode - if Importer Country Code is US or CA - Importer/Address/PostalCode - if Importer Country Code is US or CA - Importer/Address/CountryCode - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - Indicates how payment of duties for the shipment will be made. - - - - - Indicates whether this shipment contains documents only or non-documents. - - - - - The total customs value for the shipment. This total will rrepresent th esum of the values of all commodities, and may include freight, miscellaneous, and insurance charges. Must contain 2 explicit decimal positions with a max length of 17 including the decimal. For Express International MPS, the Total Customs Value is in the master transaction and all child transactions - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through FedEx System. Customers are responsible for printing their own Commercial Invoice. Commercial Invoice support consists of a maximum of 20 commodity line items. - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Country specific details of an International shipment. - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin. - - - - - - - The type of International shipment. - - - - - - - - - Specifies the type of label to be returned. - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - - - - - Description of shipping label to be returned in the reply - - - - - Specify type of label to be returned - - - - - Specifies the image format used for a shipping document. - - - - - For thermal printer lables this indicates the size of the label and the location of the doc tab if present. - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - If present, this contact and address information will replace the return address information on the label. - - - - - Allows customer-specified control of label content. - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - For thermal printer labels this indicates the size of the label and the location of the doc tab if present. - - - - - - - - - - - - - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Governs any future language/translations used for human-readable text. - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code) associated with the language. - - 2 - - - - - - - - Identifies which type minimum charge was applied. - - - - - - - - - - - - The descriptive data for the medium of exchange for FedEx services. - - - - - Identifies the currency of the monetary amount. - - 3 - - - - - - Identifies the monetary amount. - - - - - - - - - - This element is currently not supported and is for the future use. (The descriptive data regarding NAFTA COO.) - - - - - - - - - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - - - - - - - - - - - - - - - - ? - - - - - - - This element is currently not supported and is for the future use. - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - - - - - Date range over which RVC net cost was calculated. - - - - - - - Net cost method used. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - The severity of this notification. this can indicate success or failure or some other information about the request such as errors or notes. - - - - - Indicates the source of the notification. Combined with Code, it uniqely identifies this message. - - - - - A code that represents this notification. Combined with Source, it uniqely identifies this message. - - 8 - - - - - - Text that explains this notification. - - 255 - - - - - - A translated message. The translation is based on the Localization element of the ClientDetail element of the request. Not currently supported - - - - - If the message used parameter replacement to be specific as to the meaning of the message, this is the list of parameters that were used. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The oversize class types. - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as binary data (i.e. not ASCII text). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - Each instance of this data type represents the set of barcodes (of all types) which are associated with a specific package. - - - - - Binary-style barcodes for this package. - - - - - String-style barcodes for this package. - - - - - - - - - The type of rates this information contains either account based or list rates. - - - - - The method used to calculate the weight to be used in rating the package. - - - - - The method used to calculate the weight to be used in rating the package. - - - - - The weight that was used to calculate the rate. - - - - - The dimensional weight that was calculated for this package. - - - - - The oversize weight that was used in the rate calculation. - - - - - The freight charge that was calculated for this package before surcharges, discounts and taxes.. - - - - - The total discounts used in the rate calculation. - - - - - The base charge minus discounts. - - - - - The total amount of all surcharges applied to this package. - - - - - - The total sum of all taxes applied to this package. - - - - - The the charge for this package including surcharges, discounts and taxes. - - - - - The total sum of all rebates applied to this package. - - - - - A list of discounts that were applied to this package. - - - - - - A list of the surcharges applied to this package. - - - - - A list of the taxes applied to this package. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - - - Package level rate information. - - - - - Identifies which entry in the PackageRateDetails array is considered as presenting the actual rates for the package. - - - - - The difference between account based rates and list rates. Only returned when list rates are requested. - - - - - Each element of this field provides package-level rate data for a specific rate type. - - - - - - - Descriptive data regarding special services requested by the shipper for a shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Identifies the collection of special service types requested by the shipper. See SpecialServiceTypes for the list of valid enumerated types. - - - - - The COD amount that must be collected upon delivery of a package shipped using the COD special service. - - - - - Descriptive data required for a FedEx shipment containing dangerous materials. This element is required when SpecialServiceType.DANGEROUS_GOODS or HAZARDOUS_MATERIAL is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for a FedEx shipment containing dry ice. This element is required when SpecialServiceType.DRY_ICE is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx signature services. This element is required when SpecialServiceType.SIGNATURE_OPTION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Priority Alert service. This element is required when SpecialServiceType.PRIORITY_ALERT is present in the SpecialServiceTypes collection. - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Ground shipments only. - - - - - - - - - - - - - Identifies the collection of available FedEx or customer packaging options. - - - - - - - - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Descriptive data for taxpayer identification information. - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data for the monetary compensation given to FedEx for services rendered to the customer. - - - - - Identifies the method of payment for a service. See PaymentType for list of valid enumerated values. - - - - - Descriptive data identifying the party responsible for payment for a service. - - - - - - - Identifies the method of payment for a service. - - - - - - - - - - - The descriptive data identifying the party responsible for payment for a service. - - - - - Identifies the FedEx account number assigned to the payor. - - 12 - - - - - - Identifies the country of the payor. - - 2 - - - - - - - - Descriptive data for FedEx pending shipment - - - - - Provides the url for accessing email label. - - - - - User id. - - - - - Password. - - - - - This element is currently not supported and is for the future use. - - - - - - - The descriptive data for FedEx pending shipment - - - - - Identifies the type of FedEx pending shipment - - - - - Date when the pending shipment expires. - - - - - Descriptive data about notification email - - - - - - - Identifies the type of service for a pending shipment. - - - - - - - - - - - - - Identifies the type of Pickup request - - - - - Identifies the type of source for Pickup request - - - - - - - Identifies the type of source for pickup request service. - - - - - - - - - Identifies the type of pickup request service. - - - - - - - - - Identifies the type of pricing used for this shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - - - - - - - - - Identifies a discount applied to the shipment. - - - - - Identifies the type of discount applied to the shipment. - - - - - - The amount of the discount applied to the shipment. - - - - - The percentage of the discount applied to the shipment. - - - - - - - The type of the discount. - - - - - - - - - - - The weight method used to calculate the rate. - - - - - - - - - - - - - - - - - Identifies the type(s) of rates to be returned in the reply. - - - - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin - - - - - - - - - - The descriptive data for the shipment being tendered to FedEx. - - - - - Identifies the date and time the package is tendered to FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the shipment based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). There is also a UTC offset component indicating the number of hours/mainutes from UTC (e.g 2006-06-26T17:00:00-0400 is defined form June 26, 2006 5:00 pm Eastern Time). - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. See DropoffType for list of valid enumerated values. - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - Identifies the total weight of the shipment being conveyed to FedEx.This is only applicable to International shipments and should only be used on the first package of a mutiple piece shipment.This value contains 1 explicit decimal position - - - - - Total insured amount. - - - - - Descriptive data identifying the party responsible for shipping the package. Shipper and Origin should have the same address. - - - - - Descriptive data identifying the party receiving the package. - - - - - A unique identifier for a recipient location - - 10 - - - - - - Physical starting address for the shipment, if different from Shipper Address. - - - - - Descriptive data indicating the method and means of payment to FedEx for providing shipping services. - - - - - Descriptive data regarding special services requested by the shipper for this shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Details specific to an Express freight shipment. - - - - - Used with Ground Home Delivery and Freight. - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - Information about this package that only applies to an international (export) shipment. - - - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - Details about the image format and printer type the label is to returned in. - - - - - Details such as shipping document types, NAFTA information, CI information, and GAA information. - - - - - Indicates the type of rates to be returned. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - Used when requesting child pieces in a multiple piece shipment. The master tracking information will be returned in reply from the first package requested for a multiple piece shipment. That master tracking information is then inserted into the requests for each additional package requested for that multiple pice shipment. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - For a multiple piece shipment this is the total number of packages in the shipment. - - - - - Specifies whether packages are described individually,in groups, or summarized in a single description for total-piece-total-weight. This field controls which fields of the RequestedPackageLineItem will be used, and how many occurrences are expected. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - Return Email Details - - - - - Phone number of the merchant - - - - - Allowed Special service type - - - - - - - - - - - - - - - - - - Information relating to a return shipment. - - - - - The type of return shipment that is being requested. - - - - - Return Merchant Authorization - - - - - Describes specific information about the email label for return shipment. - - - - - - - The type of return shipment that is being requested. - - - - - - - - - - Shipping document type. - - - - - - - - - - - - - - - - - - - - - - - Return Merchant Authorization - - - - - The RMA number. - - 20 - - - - - - The reason for the return. - - 60 - - - - - - - - The tracking number information and the data to form the Astra barcode for the label. - - - - - The tracking number information for the shipment. - - - - - - - The textual description of the special service applied to the package. - - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The routing information detail for this shipment. - - - - - The tracking number information and the data to form the Astra barcode for the label. - - - - - - - Identifies the collection of available FedEx service options. - - - - - - - - - - - - - - - - - - - - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Shipping Document Type - - - - - Number of copies to print. - - - - - One or more document parts which make up a single logical document, such as - multiple pages of a single form. - - - - - - - - Format of shipping documents - - - - - - - - - - - - - - - - - - - - - - One or more document parts which make up a single logical document, such as - multiple pages of a single form. - - - - - - The one-origin position of this part within a document. - - - - - Graphic or printer commands for this image within a document. - - - - - - - Description of shipping documents - - - - - Specify type of documents - - - - - ? - - - - - ? - - - - - ? - - - - - This element is currently not supported and is for the future use. (Details pertaining to the GAA.) - - - - - ? - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - - - - - Shipment level rate information. Currently this is the same as the package level rate information. - - - - - The type used for this specific set of rate data. - - - - - The FedEx rate scale used to calculate these rates. - - 5 - - - - - - The FedEx rate zone used to calculate these rates. - - 1 - - - - - - Identifies the type of pricing used for this shipment. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Currency exchange rate information. - - - - - Special circumstance rating used for this shipment. - - - - - The value used to calculate the weight based on the dimensions. - - - - - Specifies a fuel surcharge percentage. - - - - - The weight used to calculate these rates. - - - - - The dimensional weith used to calculate these rates, if applicible. - - - - - The total freight charge that was calculated for this package before surcharges, discounts and taxes. - - - - - The total discounts used in the rate calculation. - - - - - The freight charge minus discounts. - - - - - The total amount of all surcharges applied to this shipment. - - - - - - The total amount of all taxes applied to this shipment. Currently not supported. - - - - - The net charge after applying all discounts and surcharges. - - - - - The total sum of all rebates applied to this shipment. - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The total of the package and shipment level variable handling charges. - - - - - - - - - - - - - - - - - - - - - - Shipment level rate information. - - - - - Identifies which entry in the ShipmentRateDetails array is considered as presenting the actual rates for the shipment. - - - - - The difference between account based rates and list rates. Only returned when list rates are requested. - - - - - Each element of this field provides shipment-level rate data for a specific rate type. - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The prefix portion of the URSA (Universal Routing and Sort Aid) code. - - 2 - - - - - - The suffix portion of the URSA code. - - 5 - - - - - - The identifier of the origin location of the shipment. Express only. - - 5 - - - - - - - The identifier of the destination location of the shipment. Express only. - - 5 - - - - - - - The state or province code of the destination of the shipment. - - 14 - - - - - - The date the shipment is expected to be delivered. - - - - - The day of the week the shipment is expected to be delivered. Express only. - - - - - The date the shipment is committed to be delivered. - - - - - The day of the week the shipment is committed to be delivered. Express only. - - - - - Currently not supported. - - - - - Text describing planned delivery. - - - - - Currently not supported. - - TBD - - - - - - The postal code of the destination of the shipment. - - 16 - - - - - - The state or province code of the destination of the shipment. - - 14 - - - - - - The country code of the destination of the shipment. - - 2 - - - - - - The identifier for the airport of the destination of the shipment. - - 4 - - - - - - - - Descriptive data regarding special services requested by the shipper for a shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Identifies the collection of special service types requested by the shipper. See SpecialServiceTypes for the list of valid enumerated types. - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. This element is required when SpecialServiceType.COD is present in the SpecialServiceTypes collection. - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a shipment shipped using the COD special service. - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. This element is required when SpecialServiceType.HOLD_AT_LOCATION is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for FedEx to provide email notification to the customer regarding the shipment. This element is required when SpecialServiceType.EMAIL_NOTIFICATION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Printed Return Label. This element is required when SpecialServiceType.PRINTED_RETURN_LABEL is present in the SpecialServiceTypes collection - - - - - The descriptive data required for FedEx Pending shipment. This element is required when SpecialServiceType.PENDING_SHIPMENT is present in the SpecialServiceTypes collection - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - The descriptive data required for FedEx Home Delivery options. This element is required when SpecialServiceType.HOME_DELIVERY_PREMIUM is present in the SpecialServiceTypes collection - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Express shipments only. - - - - - - - - - - - - - - - - - - - - - The descriptive data required for FedEx delivery signature services. - - - - - Identifies the delivery signature services option selected by the customer for this shipment. See OptionType for the list of valid values. - - - - - Identifies the delivery signature release authorization number. - - 10 - - - - - - - - Identifies the delivery signature services options offered by FedEx. - - - - - - - - - - - - - - - - - - - - - - - - The CustomerManifestId is used to group Smart Post packages onto a manifest for each trailer that is being prepared. If you do not have multiple trailers this field can be omitted. If however you - have multiple trailers a manifest Id must be assigned to each Smart Post package determined by the trailer it is being loaded onto. The manifest Id must be unique to your account number for a minimum of 6 months - and cannot exceed 8 characters in length. We recommend you use the day of year + the trailer id (this could simply be a sequential number for that trailer). So if you had 3 trailers that you started loading on Feb 10 - the 3 manifest ids would be 041001, 041002, 041003 (in this case we used leading zeros on the trailer numbers). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Special circumstance rating used for this shipment. - - - - - - - - - Identifies each surcharge applied to the shipment. - - - - - The type of surcharge applied to the shipment. - - - - - - - The amount of the surcharge applied to the shipment. - - - - - - - The type of the surcharge. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies each tax applied to the shipment. - - - - - The type of tax applied to the shipment. - - - - - - The amount of the tax applied to the shipment. - - - - - - - The descriptive data for taxpayer identification information. - - - - - Identifies the category of the taxpayer identification number. See TinType for the list of values. - - - - - Identifies the taxpayer identification number. - - 15 - - - - - - - - The type of the tax. - - - - - - - - - - - - - Required for dutiable international express or ground shipment. This field is not applicable to an international PIB (document) or a non-document which does not require a commercial invoice express shipment. - CFR_OR_CPT (Cost and Freight/Carriage Paid TO) - CIF_OR_CIP (Cost Insurance and Freight/Carraige Insurance Paid) - DDP (Delivered Duty Paid) - DDU (Delivered Duty Unpaid) - EXW (Ex Works) - FOB_OR_FCA (Free On Board/Free Carrier) - - - - - - - - - - - - - - Identifies the category of the taxpayer identification number. - - - - - - - - - - - - - - - - TrackingIdType - - - - - - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload(contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the set of valid shipment transit time values. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to validate a shipment. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - The type of handling charge to be calculated and returned in the reply. - - - - - Used with Variable handling charge type of FIXED_VALUE. - Contains the amount to be added to the freight charge. - Contains 2 explicit decimal positions with a total max length of 10 including the decimal. - - - - - - Used with Variable handling charge types PERCENTAGE_OF_BASE, PERCENTAGE_OF_NET or PERCETAGE_OF_NET_EXCL_TAXES. - Used to calculate the amount to be added to the freight charge. - Contains 2 explicit decimal positions. - - - - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The variable handling charge amount calculated based on the requested variable handling charge detail. - - - - - The calculated varibale handling charge plus the net charge. - - - - - - - The type of handling charge to be calculated and returned in the reply. - - - - - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. For this release this value should be set to 6. - - - - - Identifies the service interface level. For this release this value should be set to 0. - - - - - Identifies the service code level. For this release this value should be set to 0. - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. See WeightUnits for the list of valid enumerated values. - - - - - Identifies the weight value of the package/shipment. Contains 1 explicit decimal position - - - - - - - - - - - - Identifies the unit of measure associated with a weight value. See the list of enumerated types for valid values. - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. The way in which it is uses within a RequestedShipment depends on the RequestedPackageDetailType value specified for that shipment. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - ? - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalweight and packageCount on the shipment will be used to determine this value. - - - - - ? - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - ? - - - - - ? - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - ? - - - - - - - - - - - ? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/TrackService_v5.wsdl b/fedex/wsdl/TrackService_v5.wsdl deleted file mode 100755 index 8c5520f..0000000 --- a/fedex/wsdl/TrackService_v5.wsdl +++ /dev/null @@ -1,1510 +0,0 @@ - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Identifies where a tracking event occurs. - - - - - - - - - - - - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data for a point-of-contact person. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - Driving or other transportation distances, distinct from dimension measurements. - - - - - Identifies the distance quantity. - - - - - Identifies the unit of measure for the distance value. - - - - - - - Identifies the collection of units of measure that can be associated with a distance value. - - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - - - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - - - - - - - - - Identification for a FedEx operating company (transportation and non-transportation). - - - - - - - - The enumerated packaging type used for this package. - - - - - - - - - - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - FedEx assigned identifier for a package/shipment. - - - - - The date the package was shipped. - - - - - If the account number used to ship the package is provided in the request the shipper and recipient information is included on the letter or fax. - - - - - FedEx operating company that delivered the package. - - - - - Only country is used for elimination of duplicate tracking numbers. - - - - - - - - - - - - - - The service type of the package/shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FedEx Signature Proof Of Delivery Fax reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - Confirmation of fax transmission. - - - - - - - FedEx Signature Proof Of Delivery Fax request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - Additional customer-supplied text to be added to the body of the letter. - - - - - Contact and address information about the person requesting the fax to be sent. - - - - - Contact and address information, including the fax number, about the person to receive the fax. - - - - - - - Identifies the set of SPOD image types. - - - - - - - - FedEx Signature Proof Of Delivery Letter reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Image of letter encoded in Base64 format. - - - - - Image of letter encoded in Base64 format. - - - - - - - FedEx Signature Proof Of Delivery Letter request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - Additional customer-supplied text to be added to the body of the letter. - - - - - Identifies the set of SPOD image types. - - - - - If provided this information will be print on the letter. - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - The delivery location at the delivered to address. - - - - - - - - - - - - - - - - Detailed tracking information about a particular package. - - - - - To report soft error on an individual track detail. - - - - - The FedEx package identifier. - - - - - - When duplicate tracking numbers exist this data is returned with summary information for each of the duplicates. The summary information is used to determine which of the duplicates the intended tracking number is. This identifier is used on a subsequent track request to retrieve the tracking data for the desired tracking number. - - - - - A code that identifies this type of status. This is the most recent status. - - - - - A human-readable description of this status. - - - - - Used to report the status of a piece of a multiple piece shipment which is no longer traveling with the rest of the packages in the shipment or has not been accounted for. - - - - - Used to convey information such as. 1. FedEx has received information about a package but has not yet taken possession of it. 2. FedEx has handed the package off to a third party for final delivery. 3. The package delivery has been cancelled - - - - - Identifies a FedEx operating company (transportation). - - - - - Identifies operating transportation company that is the specific to the carrier code. - - - - - Specifies the FXO production centre contact and address. - - - - - Other related identifiers for this package such as reference numbers. - - - - - Retained for legacy compatibility only. User/screen friendly description of the Service type (e.g. Priority Overnight). - - - - - Strict representation of the Service type (e.g. PRIORITY_OVERNIGHT). - - - - - The weight of this package. - - - - - Physical dimensions of the package. - - - - - The dimensional weight of the package. - - - - - The weight of the entire shipment. - - - - - Retained for legacy compatibility only. - - - - - Strict representation of the Packaging type (e.g. FEDEX_BOX, YOUR_PACKAGING). - - - - - The sequence number of this package in a shipment. This would be 2 if it was package number 2 of 4. - - - - - The number of packages in this shipment. - - - - - - - The address information for the shipper. - - - - - The address of the FedEx pickup location/facility. - - - - - Estimated package pickup time for shipments that haven't been picked up. - - - - - Time package was shipped/tendered over to FedEx. Time portion will be populated if available, otherwise will be set to midnight. - - - - - The distance from the origin to the destination. Returned for Custom Critical shipments. - - - - - Total distance package still has to travel. Returned for Custom Critical shipments. - - - - - The address this package is to be (or has been) delivered. - - - - - The address of the FedEx delivery location/facility. - - - - - Projected package delivery time based on ship time stamp, service and destination. Not populated if delivery has already occurred. - - - - - The time the package was actually delivered. - - - - - Actual address where package was delivered. Differs from destinationAddress, which indicates where the package was to be delivered; This field tells where delivery actually occurred (next door, at station, etc.) - - - - - Identifies the method of office order delivery. - - - - - Strict text indicating the delivery location at the delivered to address. - - - - - User/screen friendly representation of the DeliveryLocationType (delivery location at the delivered to address). Can be returned in localized text. - - - - - This is either the name of the person that signed for the package or "Signature not requested" or "Signature on file". - - - - - True if signed for by signature image is available. - - - - - The types of email notifications that are available for the package. - - - - - Returned for cargo shipments only when they are currently split across vehicles. - - - - - Indicates redirection eligibility as determined by tracking service, subject to refinement/override by redirect-to-hold service. - - - - - Event information for a tracking number. - - - - - - - FedEx scanning information about a package. - - - - - The time this event occurred. - - - - - Carrier's scan code. Pairs with EventDescription. - - - - - Literal description that pairs with the EventType. - - - - - Further defines the Scan Type code's specific type (e.g., DEX08 business closed). Pairs with StatusExceptionDescription. - - - - - Literal description that pairs with the StatusExceptionCode. - - - - - Address information of the station that is responsible for the scan. - - - - - Indicates where the arrival actually occurred. - - - - - - - The type of track to be performed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FedEx assigned identifier for a package/shipment. - - - - - When duplicate tracking numbers exist this data is returned with summary information for each of the duplicates. The summary information is used to determine which of the duplicates the intended tracking number is. This identifier is used on a subsequent track request to retrieve the tracking data for the desired tracking number. - - - - - Identification of a FedEx operating company (transportation). - - - - - The date the package was shipped (tendered to FedEx). - - - - - The destination address of this package. Only city, state/province, and country are returned. - - - - - Options available for a tracking notification recipient. - - - - - - - Options available for a tracking notification recipient. - - - - - The types of email notifications available for this recipient. - - - - - - - FedEx Track Notification reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - True if duplicate packages (more than one package with the same tracking number) have been found, the packages array contains information about each duplicate. Use this information to determine which of the tracking numbers is the one you need and resend your request using the tracking number and TrackingNumberUniqueIdentifier for that package. - - - - - True if additional packages remain to be retrieved. - - - - - Value that must be passed in a TrackNotification request to retrieve the next set of packages (when MoreDataAvailable = true). - - - - - Information about the notifications that are available for this tracking number. If there are duplicates the ship date and destination address information is returned for determining which TrackingNumberUniqueIdentifier to use on a subsequent request. - - - - - - - FedEx Track Notification request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The tracking number to which the notifications will be triggered from. - - - - - Indicates whether to return tracking information for all associated packages. - - - - - When the MoreDataAvailable field is true in a TrackNotificationReply the PagingToken must be sent in the subsequent TrackNotificationRequest to retrieve the next page of data. - - - - - Use this field when your original request informs you that there are duplicates of this tracking number. If you get duplicates you will also receive some information about each of the duplicate tracking numbers to enable you to chose one and resend that number along with the TrackingNumberUniqueId to get notifications for that tracking number. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - Included in the email notification identifying the requester of this notification. - - - - - Included in the email notification identifying the requester of this notification. - - - - - Who to send the email notifications to and for which events. The notificationRecipientType and NotifyOnShipment fields are not used in this request. - - - - - - - The type and value of the package identifier that is to be used to retrieve the tracking information for a package. - - - - - The value to be used to retrieve tracking information for a package. - - - - - The type of the Value to be used to retrieve tracking information for a package (e.g. SHIPPER_REFERENCE, PURCHASE_ORDER, TRACKING_NUMBER_OR_DOORTAG, etc..) . - - - - - - - Used to report the status of a piece of a multiple piece shipment which is no longer traveling with the rest of the packages in the shipment or has not been accounted for. - - - - - An identifier for this type of status. - - - - - A human-readable description of this status. - - - - - - - The descriptive data returned from a FedEx package tracking request. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - True if duplicate packages (more than one package with the same tracking number) have been found, and only limited data will be provided for each one. - - - - - True if additional packages remain to be retrieved. - - - - - Value that must be passed in a TrackNotification request to retrieve the next set of packages (when MoreDataAvailable = true). - - - - - Contains detailed tracking information for the requested packages(s). - - - - - - - The descriptive data sent by a client to track a FedEx package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - The FedEx operating company (transportation) used for this package's delivery. - - - - - Identifies operating transportation company that is the specific to the carrier code. - - - - - The type and value of the package identifier that is to be used to retrieve the tracking information for a package or group of packages. - - - - - Used to distinguish duplicate FedEx tracking numbers. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - For tracking by references information either the account number or destination postal code and country must be provided. - - - - - For tracking by references information either the account number or destination postal code and country must be provided. - - - - - If false the reply will contain summary/profile data including current status. If true the reply contains profile + detailed scan activity for each package. - - - - - When the MoreData field = true in a TrackReply the PagingToken must be sent in the subsequent TrackRequest to retrieve the next page of data. - - - - - - - - - - - - - Used when a cargo shipment is split across vehicles. This is used to give the status of each part of the shipment. - - - - - The number of pieces in this part. - - - - - The date and time this status began. - - - - - A code that identifies this type of status. - - - - - A human-readable description of this status. - - - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - Identifies the collection of units of measure that can be associated with a weight value. - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/fedex/wsdl/test_server_wsdl/CloseService_v2.wsdl b/fedex/wsdl/test_server_wsdl/CloseService_v2.wsdl deleted file mode 100755 index 113bd2e..0000000 --- a/fedex/wsdl/test_server_wsdl/CloseService_v2.wsdl +++ /dev/null @@ -1,548 +0,0 @@ - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - ? - - - - - ? - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - ? - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - Identifies the date and time up to which unclosed shipments are to be closed. Both the date and time portions of the string are expected to be used. The time is the local time based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2009-04-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by a T (e.g. 2009-04-26T17:00:00). - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - ? - - - - - Service business level. - - - - - Service interface level. - - - - - Service code level. - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/test_server_wsdl/CourierDispatchService_v3.wsdl b/fedex/wsdl/test_server_wsdl/CourierDispatchService_v3.wsdl deleted file mode 100755 index 98f7e77..0000000 --- a/fedex/wsdl/test_server_wsdl/CourierDispatchService_v3.wsdl +++ /dev/null @@ -1,1075 +0,0 @@ - - - - - - - - - - - - - The descriptive data to schedule a FedEx package pickup request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the origin of the shipment being picked up by FedEx. - - - - - Descriptive data for a freight shipment being picked up by FedEx. This is element is only required when requesting a freight service pickup. - - - - - Identifies the number of packages that are being tendered to FedEx for this pickup request. - - - - - - - - Identifies the total weight of the package or packages being tendered to FedEx for this pickup request. - - - - - Identifies the FedEx operating company (transportation) that is being sent the package pickup request. - - - - - Identifies the number of oversize packages that are being tendered to FedEx for this pickup request. Please refer to the FedEx Service Guide for package size limits to determine if a package is oversized for the service being shipped. - - - - - - - - Identifies any remarks or comments to be passed to the FedEx courier picking up the shipment. - - 60 - - - - - - Identifies the type of commodity being shipped. This element is required for an international shipment. - - 20 - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Identifies the unique client device submitting the request. - - 10 - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data for the local language and locale (i.e. country). - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code). - - 2 - - - - - - - - The descriptive data that governs data payload language/translations. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload(contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. Customers using the FedEx Web Services interface should set this element to "wsi". - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - Descriptive data about the origin of the package being picked up by FedEx. - - - - - Flag identifies if customer wants to use Account address or send and alternate address for pickup. - - - - - Descriptive data about the physical location of the package being picked up by FedEx. - - - - - Identifies the physical location where the courier should pick up the shipment. See CourierDispatchBuildingLocationType for valid values. - - - - - Identifies the part of the building where the package is located for pickup by FedEx. See BuildingPartCode for valid values. - - - - - Identifies additional descriptive information associated with the BuildingPartCode to assist the FedEx courier in finding the pickup location. - - - - - Identifies the date and time the package will be ready for pickup by FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the pickup based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS in 24-hour form. The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). Because this is a local time, no TZD should be included. If a TZD is included, it will be ignored, and the time treated as local to the pickup postal code. - - - - - Identifies the close time of the company requesting the pickup. The time is the local time of the pickup based on the shipper's time zone. The time component must be in the format: HH:MM:SS in 24-hour form (e.g. 17:00:00). Because this is a local time, no TZD should be included. If a TZD is included, it will be ignored, and the time treated as local to the pickup postal code. - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - Descriptive data identifying the point-of-contact person. - - - - - Identifies the contact person's name. - - 35 - - - - - - Identifies the contact person's title. - - 35 - - - - - - Identifies the contact person's company name. - - 35 - - - - - - Identifies the contact person's phone number. - - 16 - - - - - - Identifies the contact person's phone number extension. - - - - - Identifies the contact person's pager number. - - 16 - - - - - - Identifies the contact person's fax machine phone number. - - 16 - - - - - - Identifies the contact person's email address. - - 120 - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - 35 - - - - - - Name of city, town, etc. - - 35 - - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - 2 - - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. This element is required if both the City and StateOrProvinceCode are not present. - - 16 - - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - - - - Identification of a country. - - 2 - - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - Identifies the valid set of valid building locations for package pickup. - - - - - - - - - - - Identifies the valid set of building part types when requesting a package pickup. - - - - - - - - - - - - - Descriptive data regarding a FedEx freight service pickup request. - - - - - Identifies the collection of available FedEx transportation service options. Must be a valid FedEx freight service identifier. - - - - - Identifies the FedEx freight booking number. This element should contain numeric values only. - - 8 - - - - - - Descriptive data detailing the length, width, and height of the freight package or shipment being picked up by FedEx. - - - - - Identifies the type of truck that is needed for FedEx to pick up the freight shipment. See TruckType for valid values. - - - - - Identifies the tailer size needed for FedEx to pick up a freight shipment. See TrailerSizeType for valid values. - - - - - - - Identifies the collection of available FedEx transportation service options. - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data detailing the length, width, and height of a package. - - - - - Identifies the length of the package. - - - - - - - - Identifies the width of the package. - - - - - - - - Identifies the height of the package. - - - - - - - - Identifies the unit of measure associated with a dimensional values. See LinearUnits for valid values. - - - - - - - Identifies the collection of linear units of measure for a package dimension. - - - - - - - - - Identifies the valid set of truck types supported by FedEx. This type is appropriate only for freight pickup requests. - - - - - - - - - - Identifies the valid set of tractor tailer sizes supported by FedEx. This type is appropriate only for freight pickup requests. - - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. See WeightUnits for the valid values. - - - - - Identifies the weight value of the package. - - - - - - - Identifies the collection of units of measure that can be associated with a weight value. - - - - - - - - - The descriptive data returned to a client in response to a courier dispatch (i.e. package pickup) request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies the confirmation number assigned by FedEx for the request. - - 30 - - - - - - Identifies the FedEx Location identifier responsible for dispatching the courier to pickup the package. - - 5 - - - - - - Identifies the FedEx system code associated with the message text in the reply. - - 3 - - - - - - Identifies the message text from the FedEx system regarding whether or not the pickup request was successfully scheduled or not. - - 254 - - - - - - Identifies the Package Return Program control number. - - 19 - - - - - - - - The descriptive data to cancel a package pickup request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies the FedEx operating company (transportation) that was sent the courier dispatch that is being canceled. - - - - - Identifies the dispatch confirmation number that is being canceled. The dispatch confirmation number was returned to the client when the courier dispatch was requested. - - 30 - - - - - - Identifies the scheduled date for the courier dispatch that is being canceled. The scheduled date was provided by the client when the courier dispatch was requested. - - - - - Identifies the FedEx location identifier responsible for dispatching the courier for package pickup that is being canceled. The FedEx location identifier was returned to the client when the courier dispatch was requested. Required for Express service type. - - 5 - - - - - - Identifies comments the customer wants to convey to the FedEx courier regarding the package pickup. - - 60 - - - - - - - - The descriptive data returned to a client in response to a cancel dispatch request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a text message indicating the outcome of the cancel dispatch request. - - 254 - - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Identifies the severity of the Notification item. See NotificationSeverityType for list of returned values. - - - - - Identifies the source - what FedEx system, sub-system, or component generated the Notification item. - - - - - Identifies the error code generated by the FedEx system, sub-system or component. - - 8 - - - - - - Identifies the error message text. - - 255 - - - - - - Identifies the error message text in the localization requested. Currently not supported. - - - - - Used internally by FedEx systems for message translation. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The descriptive data to request availability of pickup. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data providing information about address to pickup from. - - - - - An array of PickupRequestType. If SAME_DAY is included, Options with ScheduleDay of SAME_DAY will be included in the reply. - If FUTURE_DAY is included, Options with ScheduleDay of FUTURE_DAY will be included in the reply. - - - - - The dispatch date (in the local time zone) for the pickup whose availability is being requested. - - - - - The time when the package will be ready to be picked up. The time is local to the pickup postal code, in 24-hour form (e.g. 13:00:00). It should not contain a TZD. If a TZD is included, it will be ignored - - - - - The lastest time at which the courier will be able to gain access to pick up the package(s). The time is local to the pickup postal code, in 24-hour form (e.g. 17:00:00). It should not contain a TZD. If a TZD is included, it will be ignored - - - - - The FedEx carrier(s) for which availability is requested. - - - - - Descriptive information about the shipment. - - - - - - - The descriptive data returned to a client in response to a cancel dispatch request. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - the point in time when the request was processed - - - - - Identifies the options for picking up the shipment. - - - - - - - Describes the relationship between the date on which a dispatch occurs and the date on which it is created (scheduled) - by means of a CourierDispatchRequest. FUTURE_DAY means that the dispatch date is later than the date on which it is created. - SAME_DAY means that the dispatch is to occur on the date on which it is created. - - - - - - - - - - Descriptive information about the shipment. - - - - - Descriptive information about the dimensions of the package. - - - - - Descriptive information about the weight of the package. - - - - - - - The constraints on the scheduling of a dispatch, where that dispatch would be made by the Carrier, occur on the PickupDate, - and would be scheduled (created by means of a CourierDispatchRequest) on a date related to the PickupDate as described - by the "ScheduleDay" (SAME_DAY meaning that the creation would occur on the PickupDate, and FUTURE_DAY meaning that the creation - would occur on a date prior to the PickupDate). - - - - - the carrier to which this PickupScheduleOption applies - - - - - Descriptive information about the shipment. - - - - - Tells whether this option describes a dispatch created on the dispatch date (SAME_DAY), or on a prior date (FUTURE_DAY) - - - - - True if this pickup option is available. - - - - - Identifies the date (in the postal code's time zone) to which this PickupScheduleOption refers. - - - - - Identifies the latest allowed ready time (in the postal code's time zone) for a postal code. As a local time, it will not include a Time Zone Designator - - - - - Identifies the minimum required length of the window of time between the ReadyTime and the CustomerCloseTime. - - - - - Identifies availability of residential pickup. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/test_server_wsdl/RateService_v16.wsdl b/fedex/wsdl/test_server_wsdl/RateService_v16.wsdl deleted file mode 100755 index d66c8c1..0000000 --- a/fedex/wsdl/test_server_wsdl/RateService_v16.wsdl +++ /dev/null @@ -1,4866 +0,0 @@ - - - - - - - - Specifies the role that identifies the permissions the accessor of the pending shipment. - - - - - - - - - Specifies additional labels to be produced. All required labels for shipments will be produced without the need to request additional labels. These are only available as thermal labels. - - - - - The type of additional labels to return. - - - - - The number of this type label to return - - - - - - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - The fully spelt out name of a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Specifies details for a package containing alcohol - - - - - The license type that the recipient of the alcohol package. - - - - - - - Specifies the type of license that the recipient of the alcohol shipment has. - - - - - - - - - - - - - - - - - - Identification of the type of barcode (symbology) used on FedEx documents and labels. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The instructions indicating how to print the Certificate of Origin ( e.g. whether or not to include the instructions, image type, etc ...) - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - - - - Specifies the type of brokerage to be applied to a shipment. - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the FedEx Office integrator. - - - - - Indicates the region from which the transaction is submitted. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - Identifies the type of funds FedEx should collect upon shipment delivery. - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - - Specifies the details of the charges are to be added to the COD collect amount. - - - - - Identifies the type of funds FedEx should collect upon package delivery - - - - - For Express this is the descriptive data that is used for the recipient of the FedEx Letter containing the COD payment. For Ground this is the descriptive data for the party to receive the payment that prints the COD receipt. - - - - - When the FedEx COD payment type is not CASH, indicates the contact and address of the financial institution used to service the payment of the COD. - - - - - Specifies the name of person or company receiving the secured/unsecured funds payment - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - - - - - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through the FedEx Systems. Customers are responsible for printing their own Commercial Invoice.If you would likeFedEx to generate a Commercial Invoice and transmit it to Customs. for clearance purposes, you need to specify that in the ShippingDocumentSpecification element. If you would like a copy of the Commercial Invoice that FedEx generated returned to you in reply it needs to be specified in the ETDDetail/RequestedDocumentCopies element. Commercial Invoice support consists of maximum of 99 commodity line items. - - - - - Any comments that need to be communicated about this shipment. - - - - - Any freight charges that are associated with this shipment. - - - - - Any taxes or miscellaneous charges(other than Freight charges or Insurance charges) that are associated with this shipment. - - - - - Specifies which kind of charge is being recorded in the preceding field. - - - - - Any packing costs that are associated with this shipment. - - - - - Any handling costs that are associated with this shipment. - - - - - Free-form text. - - - - - Free-form text. - - - - - Free-form text. - - - - - The reason for the shipment. Note: SOLD is not a valid purpose for a Proforma Invoice. - - - - - Name of the International Expert that completed the Commercial Invoice different from Sender. - - - - - Required for dutiable international Express or Ground shipments. This field is not applicable to an international PIB(document) or a non-document which does not require a Commercial Invoice. - - - - - - - The instructions indicating how to print the Commercial Invoice( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies the usage and identification of a customer supplied image to be used on this document. - - - - - - - Information about the transit time and delivery commitment date and time. - - - - - The Commodity applicable to this commitment. - - - - - The FedEx service type applicable to this commitment. - - - - - Shows the specific combination of service options combined with the service type that produced this committment in the set returned to the caller. - - - - - Supporting detail for applied options identified in preceding field. - - - - - THe delivery commitment date/time. Express Only. - - - - - The delivery commitment day of the week. - - - - - The number of transit days; applies to Ground and LTL Freight; indicates minimum transit time for SmartPost. - - - - - Maximum number of transit days, for SmartPost shipments. - - - - - The service area code for the destination of this shipment. Express only. - - - - - The address of the broker to be used for this shipment. - - - - - The FedEx location identifier for the broker. - - - - - The delivery commitment date/time the shipment will arrive at the border. - - - - - The delivery commitment day of the week the shipment will arrive at the border. - - - - - The number of days it will take for the shipment to make it from broker to destination - - - - - The delivery commitment date for shipment served by GSP (Global Service Provider) - - - - - The delivery commitment day of the week for the shipment served by GSP (Global Service Provider) - - - - - Messages concerning the ability to provide an accurate delivery commitment on an International commit quote. These could be messages providing information about why a commitment could not be returned or a successful message such as "REQUEST COMPLETED" - - - - - Messages concerning the delivery commitment on an International commit quote such as "0:00 A.M. IF NO CUSTOMS DELAY" - - - - - Information about why a shipment delivery is delayed and at what level (country/service etc.). - - - - - - Required documentation for this shipment. - - - - - Freight origin and destination city center information and total distance between origin and destination city centers. - - - - - - - The type of delay this shipment will encounter. - - - - - - - - - - - - - - - - - - - - - - - - - - This field is used for enterprise transactions. - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - - - - - - - - - Uniquely identifies a consolidation, which is a logical container for a collection of shipments. - - - - - Specifies the type of consolidation. - - - - - Uniquely identifies the consolidation, within a given type and date. - - - - - The date on which the consolidation was created. - - - - - - - - - - - - - - - - - The descriptive data for a point-of-contact person. - - - - - Client provided identifier corresponding to this contact information. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies a toll free number, if any, associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - - - - - - - - - - - The currency code for the original (converted FROM) currency. - - - - - The currency code for the final (converted INTO) currency. - - - - - Multiplier used to convert fromCurrency units to intoCurrency units. - - - - - - - - - Indicates the type of custom delivery being requested. - - - - - Time by which delivery is requested. - - - - - Range of dates for custom delivery request; only used if type is BETWEEN. - - - - - Date for custom delivery request; only used for types of ON, BETWEEN, or AFTER. - - - - - - - - - - - - - - - Data required to produce a custom-specified document, either at shipment or package level. - - - - - Common information controlling document production. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Identifies the formatting specification used to construct this custom document. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified barcode symbology. - - - - - - - - - Width of thinnest bar/space element in the barcode. - - - - - - - - Solid (filled) rectangular area on label. - - - - - - - - - - - - - - - - - - - - - - - - Image to be included from printer's memory, or from a local file for offline clients. - - - - - - Printer-specific index of graphic image to be printed. - - - - - Fully-qualified path and file name for graphic image to be printed. - - - - - - - - - Horizontal position, relative to left edge of custom area. - - - - - Vertical position, relative to top edge of custom area. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified printer font (for thermal labels) or generic font/size (for plain paper labels). - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - Generic font name for use with plain paper labels. - - - - - Generic font size for use with plain paper labels. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default is former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - - - Controls which data/sections will be suppressed. - - - - - For customers producing their own Ground labels, this field specifies which secondary barcode will be printed on the label; so that the primary barcode produced by FedEx has the correct SCNC. - - - - - - - Controls the number of additional copies of supplemental labels. - - - - - This value reduces the default quantity of destination/consignee air waybill labels. A value of zero indicates no change to default. A minimum of one copy will always be produced. - - - - - - - - - - - - - - - - - Interacts both with properties of the shipment and contractual relationship with the shipper. - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - - - - - - - - - - - Specifies additional description about customs options. This is a required field when the customs options type is "OTHER". - - - - - - - - - - - - - - - - - - - - - - - - - - - Describes an approved container used to package dangerous goods commodities. This does not describe any individual inner receptacles that may be within this container. - - - - - Indicates whether there are additional inner receptacles within this container. - - - - - Indicates the type of this dangerous goods container, as specified by the IATA packing instructions. For example, steel cylinder, fiberboard box, plastic jerrican and steel drum. - - - - - Indicates the packaging type of the container used to package the radioactive materials. - - - - - Indicates the number of occurrences of this container with identical dangerous goods configuration. - - - - - Documents the kinds and quantities of all hazardous commodities in the current container. - - - - - - - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - Indicates which kinds of hazardous content are in the current package. - - - - - Indicates whether there is additional customer provided packaging enclosing the approved dangerous goods containers. - - - - - Identifies the configuration of this dangerous goods package. The common configuration is represented at the shipment level. - - - - - Indicates one or more containers used to pack dangerous goods commodities. - - - - - Description of the packaging of this commodity, suitable for use on OP-900 and OP-950 forms. - - - - - Name, title and place of the signatory for this shipment. - - - - - Telephone number to use for contact in the event of an emergency. - - - - - Offeror's name or contract number, per DOT regulation. - - - - - Specifies the contact of the party responsible for handling the infectious substances, if any, in the dangerous goods shipment. - - - - - Specifies additional handling information for the current package. - - - - - Specifies the radioactivity detail for the current package, if the package contains radioactive materials. - - - - - - - - - - - - The instructions indicating how to print the 1421c form for dangerous goods shipment. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Specifies that name, title and place of the signatory responsible for the dangerous goods shipment. - - - - - - - Indicates the place where the form is signed. - - - - - - - - - - - - - - - - - - - - - - - - Information about why a shipment delivery is delayed and at what level( country/service etc.). - - - - - The date of the delay - - - - - - The attribute of the shipment that caused the delay(e.g. Country, City, LocationId, Zip, service area, special handling ) - - - - - The point where the delay is occurring (e.g. Origin, Destination, Broker location) - - - - - The reason for the delay (e.g. holiday, weekend, etc.). - - - - - The name of the holiday in that country that is causing the delay. - - - - - - - The attribute of the shipment that caused the delay(e.g. Country, City, LocationId, Zip, service area, special handling ) - - - - - - - - - - - - - - The point where the delay is occurring ( e.g. Origin, Destination, Broker location). - - - - - - - - - - - - - - - Specifies the tracking id for the return, if preassigned. - - - - - - - Data required to complete the Destionation Control Statement for US exports. - - - - - - Comma-separated list of up to four country codes, required for DEPARTMENT_OF_STATE statement. - - - - - Name of end user, required for DEPARTMENT_OF_STATE statement. - - - - - - - - - - - - - - - - - - - - - Driving or other transportation distances, distinct from dimension measurements. - - - - - Identifies the distance quantity. - - - - - Identifies the unit of measure for the distance value. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Content of the email message. - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - - - - - - - - - Information describing the address of of the email recipient, role of the email recipient and languages that are requested to be supported. - - - - - EMail address of the recipient. - - - - - The relationship that the customer has to the pending shipment. - - - - - Specifies how the email notification for the pending shipment need to be processed. - - - - - Localization and language details specified by the recipient of the EMail. - - - - - - - - - - - - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how to apply the localization detail to the current context. - - - - - - - - Electronic Trade document references used with the ETD special service. - - - - - Indicates the types of shipping documents produced for the shipper by FedEx (see ShippingDocumentSpecification) which should be copied back to the shipper in the shipment result data. - - - - - - - - - The instructions indicating how to print the Export Declaration. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US). - - - - - - - - - - - - - - - - - - - - - - - - - Indicates a FedEx Express operating region. - - - - - - - - - - - - Identifies a kind of FedEx facility. - - - - - - - - - - - - - - - Specifies the optional features/characteristics requested for a Freight shipment utilizing a flatbed trailer. - - - - - - - - - - - - - - Data required to produce the Freight handling-unit-level address labels. Note that the number of UNIQUE labels (the N as in 1 of N, 2 of N, etc.) is determined by total handling units. - - - - - - Indicates the number of copies to be produced for each unique label. - - - - - Specifies the quadrant of the page on which the label printing will start. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - - - - Individual charge which contributes to the total base charge for the shipment. - - - - - Freight class for this line item. - - - - - Effective freight class used for rating this line item. - - - - - NMFC Code for commodity. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - Rate or factor applied to this line item. - - - - - Identifies the manner in which the chargeRate for this line item was applied. - - - - - The net or extended charge for this line item. - - - - - - - Specifies the way in which base charges for a Freight shipment or shipment leg are calculated. - - - - - - - - - - - - - - - - These values represent the industry-standard freight classes used for FedEx Freight and FedEx National Freight shipment description. (Note: The alphabetic prefixes are required to distinguish these values from decimal numbers on some client platforms.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Information about the Freight Service Centers associated with this shipment. - - - - - Information about the origin Freight Service Center. - - - - - Information about the destination Freight Service Center. - - - - - The distance between the origin and destination FreightService Centers - - - - - - - - - - Date for all Freight guarantee types. - - - - - - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - - - - - Rate data specific to FedEx Freight or FedEx National Freight services. - - - - - A unique identifier for a specific rate quotation. - - - - - Specifies whether the rate quote was automated or manual. - - - - - Specifies how total base charge is determined. - - - - - Freight charges which accumulate to the total base charge for the shipment. - - - - - Human-readable descriptions of additional information on this shipment rating. - - - - - - - Additional non-monetary data returned with Freight rates. - - - - - Unique identifier for notation. - - - - - Human-readable explanation of notation. - - - - - - - Specifies the type of rate quote - - - - - - - - - This class describes the relationship between a customer-specified address and the FedEx Freight / FedEx National Freight Service Center that supports that address. - - - - - Freight Industry standard non-FedEx carrier identification - - - - - The name of the Interline carrier. - - - - - Additional time it might take at the origin or destination to pickup or deliver the freight. This is usually due to the remoteness of the location. This time is included in the total transit time. - - - - - Service branding which may be used for local pickup or delivery, distinct from service used for line-haul of customer's shipment. - - - - - Distance between customer address (pickup or delivery) and the supporting Freight / National Freight service center. - - - - - Time to travel between customer address (pickup or delivery) and the supporting Freight / National Freight service center. - - - - - Specifies when/how the customer can arrange for pickup or delivery. - - - - - Specifies days of operation if localServiceScheduling is LIMITED. - - - - - Freight service center that is a gateway on the border of Canada or Mexico. - - - - - Alphabetical code identifying a Freight Service Center - - - - - Freight service center Contact and Address - - - - - - - Specifies the type of service scheduling offered from a Freight or National Freight Service Center to a customer-supplied address. - - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Account number used with FEDEX_FREIGHT service. - - - - - Used for validating FedEx Freight account number and (optionally) identifying third party payment on the bill of lading. - - - - - Used in connection with "Send Bill To" (SBT) identification of customer's account used for billing. - - - - - Indicates the role of the party submitting the transaction. - - - - - Designates the terms of the "collect" payment for a Freight Shipment. - - - - - Identifies the declared value for the shipment - - - - - Identifies the declared value units corresponding to the above defined declared value - - - - - - Identifiers for promotional discounts offered to customers. - - - - - Total number of individual handling units in the entire shipment (for unit pricing). - - - - - Estimated discount rate provided by client for unsecured rate quote. - - - - - Total weight of pallets used in shipment. - - - - - Overall shipment dimensions. - - - - - Description for the shipment. - - - - - Specifies which party will pay surcharges for any special services which support split billing. - - - - - - Details of the commodities in the shipment. - - - - - - - Description of an individual commodity or class of content in a shipment. - - - - - Freight class for this line item. - - - - - Specification of handling-unit packaging for this commodity or class line. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - - Volume (cubic measure) for this commodity or class line. - - - - - - - Indicates the role of the party submitting the transaction. - - - - - - - - - Specifies which party will be responsible for payment of any surcharges for Freight special services for which split billing is allowed. - - - - - Identifies the special service. - - - - - Indicates who will pay for the special service. - - - - - - - Data required to produce a General Agency Agreement document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - This describes the inner receptacle details for a hazardous commodity within the dangerous goods container. - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies the details of any radio active materials within the commodity. - - - - - - - Identifies and describes an individual hazardous commodity. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - - - - - - - Indicates any special processing options to be applied to the description of the dangerous goods commodity. - - - - - Information related to quantity limitations and operator or state variations as may be applicable to the dangerous goods commodity. - - - - - - - Specifies any special processing to be applied to the dangerous goods commodity description validation. - - - - - - - - This describes information about the inner receptacles for the hazardous commodity in a particular dangerous goods container. - - - - - This specifies the quantity contained in the inner receptacle. - - - - - - - Specifies how the commodity is to be labeled. - - - - - - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies how the customer wishes the label text to be handled for this commodity in this package. - - - - - Text used in labeling the commodity under control of the labelTextOption field. - - - - - - - Indicates which kind of hazardous content is being reported. - - - - - - - - - - - - - Identifies number and type of packaging units for hazardous commodities. - - - - - Number of units of the type below. - - - - - Units in which the hazardous commodity is packaged. - - - - - - - Specifies documentation and limits for validation of an individual packing group/category. - - - - - - Coded specification for how commodity is to be packed. - - - - - - - Identifies DOT packing group for a hazardous commodity. - - - - - - - - - - - Identifies amount and units for quantity of hazardous commodities. - - - - - Number of units of the type below. - - - - - Units by which the hazardous commodity is measured. For IATA commodity, the units values are restricted based on regulation type. - - - - - Specifies which measure of quantity is to be validated. - - - - - - - Specifies the measure of quantity to be validated against a prescribed limit. - - - - - - - - - Identifies the source of regulation for hazardous commodity data. - - - - - - - - - - - - - - - - - - Contact phone number for recipient of shipment. - - - - - Contact and address of FedEx facility at which shipment is to be held. - - - - - Type of facility at which package/shipment is to be held. - - - - - Location identification (for facilities identified by an alphanumeric location code). - - - - - Location identification (for facilities identified by an numeric location code). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - - - - - - Specifies the order in which the labels will be returned - - - - - - - - - - - - - - - Relative to normal orientation for the printer. - - - - - - - - - - - - - - - - - - Specifies the order in which the labels are requested to be returned - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the Liability Coverage Amount. For Jan 2010 this value represents coverage amount per pound - - - - - - - - - - - - - Represents a one-dimensional measurement in small units (e.g. suitable for measuring a package or document), contrasted with Distance, which represents a large one-dimensional measurement (e.g. distance between cities). - - - - - The numerical quantity of this measurement. - - - - - The units for this measurement. - - - - - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - - - - - - - - - - - - - - - - - - - - - - Data required to produce a Certificate of Origin document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - Contact information for "Authorized Signature" area of form. - - - - - - - - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - Date range over which RVC net cost was calculated. - - - - - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - - - - - - - - - - The instructions indicating how to print the OP-900 form for hazardous materials packages. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Identifies which reference type (from the package's customer references) is to be used as the source for the reference on this OP-900. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - Data field to be used when a name is to be printed in the document instead of (or in addition to) a signature image. - - - - - - - - - - - - - - Data for a package's rates, as calculated per a specific rate type. - - - - - Type used for this specific set of rate data. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - - The dimensional weight of this package (if greater than actual). - - - - - The oversize weight of this package (if the package is oversize). - - - - - The transportation charge only (prior to any discounts applied) for this package. - - - - - The sum of all discounts on this package. - - - - - This package's baseCharge - totalFreightDiscounts. - - - - - The sum of all surcharges on this package. - - - - - This package's netFreight + totalSurcharges (not including totalTaxes). - - - - - The sum of all taxes on this package. - - - - - This package's netFreight + totalSurcharges + totalTaxes. - - - - - - All rate discounts that apply to this package. - - - - - All rebates that apply to this package. - - - - - All surcharges that apply to this package (either because of characteristics of the package itself, or because it is carrying per-shipment surcharges for the shipment of which it is a part). - - - - - All taxes applicable (or distributed to) this package. - - - - - - - - - - - - - - - - - - - - These special services are available at the package level for some or all service types. If the shipper is requesting a special service which requires additional data, the package special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment or package. - - - - - For use with FedEx Ground services only; COD must be present in shipment's special services. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This information describes the kind of pending shipment being requested. - - - - - - Date after which the pending shipment will no longer be available for completion. - - - - - Only used with type of EMAIL. - - - - - - These are documents that are recommended to be included with the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This class describes the pickup characteristics of a shipment (e.g. for use in a tag request). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates the packaging type of the container used to package radioactive hazardous materials. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates whether packaging type "EXCEPTED" or "EXCEPTED_PACKAGE" is for radioactive material in reportable quantity. - - - - - - - - - Indicates the reason that a dim divisor value was chose. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Selects the value from a set of rate data to which the percentage is applied. - - - - - - - - - - - The response to a RateRequest. The Notifications indicate whether the request was successful or not. - - - - - This indicates the highest level of severity of all the notifications returned in this reply. - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Contains the CustomerTransactionId that was sent in the request. - - - - - The version of this reply. - - - - - Each element contains all rate data for a single service. If service was specified in the request, there will be a single entry in this array; if service was omitted in the request, there will be a separate entry in this array for each service being compared. - - - - - - - - - - - Shows the specific combination of service options combined with the service type that produced this committment in the set returned to the caller. - - - - - Supporting detail for applied options identified in preceding field. - - - - - - - - - - - Not populated by FAST service in Jan07. - - - - - Not populated by FAST service in Jan07. - - - - - Not populated by FAST service in Jan07. - - - - - Maximum expected transit time - - - - - Not populated by FAST service in Jan07. Actual signature option applied, to allow for cases in wihch the original value conflicted with other service features in the shipment. - - - - - - Each element contains all rate data for a single rate type. - - - - - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - - - - Allows the caller to specify that the transit time and commit data are to be returned in the reply. - - - - - Candidate carriers for rate-shopping use case. This field is only considered if requestedShipment/serviceType is omitted. - - - - - Contains zero or more service options whose combinations are to be considered when replying with available services. - - - - - If provided, identifies the consolidation to which this open shipment should be added after successful creation. - - - - - The shipment for which a rate quote (or rate-shopping comparison) is desired. - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - - - Echoed from the corresponding package in the rate request (if provided). - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - The difference between "list" and "account" net charge. - - - - - Ground COD is shipment level. - - - - - - Rate data that are tied to a specific package and rate type combination. - - - - - - - This class groups the shipment and package rating data for a specific rate type for use in a rating reply, which groups result data by rate type. - - - - - The difference between "list" and "account" total net charge. - - - - - Express COD is shipment level. - - - - - The shipment-level totals for this rate type. - - - - - The package-level data for this rate type. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - Specifies the kind of identification being used. - - - - - Contains the actual ID value, of the type specified above. - - - - - - - - - - - - - - Specifies the details about documents that are recommended to be included with the shipment for ease of shipment processing and transportation. - - - - - - - - Type of documents that are recommended to be included with the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies details needed to generate any label artifacts required due to regulatory requirements. - - - - - - Specifies how the customer requested the regulatory label to be generated. - - - - - - - - - - - - Describes the vertical position of an item relative to another item. - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - - Specifies the declared value for carriage of the package. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the package. This field is only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case total weight and packageCount on the shipment will be used to determine this value. - - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - Human-readable text describing the contents of the package to be used for clearance purposes. - - - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - - - - - - - - Specifies the total declared value for carriage of the shipment. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the shipment. - - - - - This attribute indicates the currency the caller requests to have used in all returned monetary values (when a choice is possible). - - - - - - - - Physical starting address for the shipment, if different from shipper's address. - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Used with Ground Home Delivery and Freight. - - - - - - Customs clearance data, used for both international and intra-country shipping. - - - - - For use in "process tag" transaction. - - - - - Specifies the characteristics of a shipment pertaining to SmartPost services. - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - - Contains data used to create additional (non-label) shipping documents. - - - - - Specifies whether and what kind of rates the customer wishes to have quoted on this shipment. The reply will also be constrained by other data on the shipment and customer. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - The total number of packages in the entire shipment (even when the shipment spans multiple transactions.) - - - - - Specifies which package-level data values are provided at the shipment-level only. The package-level data values types specified here will not be provided at the package-level. - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the tracking number of the master associated with the return shipment. - - - - - - - - These values are used to control the availability of certain special services at the time when a customer uses the e-mail label link to create a return shipment. - - - - - - - - - - - - Identifies the allowed (merchant-authorized) special services which may be selected when the subsequent shipment is created. Only services represented in EMailLabelAllowedSpecialServiceType will be controlled by this list. - - - - - - - The instructions indicating how to print the return instructions( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies additional customer provided text to be inserted into the return document. - - - - - - - - - - - - - - - - - - - - - - The "PAYOR..." rates are expressed in the currency identified in the payor's rate table(s). The "RATED..." rates are expressed in the currency of the origin country. Former "...COUNTER..." values have become "...RETAIL..." values, except for PAYOR_COUNTER and RATED_COUNTER, which have been removed. - - - - - - - - - - - - - - - June 2011 ITG 121203 IR-RMA number has been removed from this structure and added as a new customer reference type. The structure remains because of the reason field below. - - - - - - - - Describes the rotation of an item from its default orientation. - - - - - - - - - - - - - - - - - - - These values control the optional features of service that may be combined in a commitment/rate comparision transaction. - - - - - - - - - - - - Supporting detail for applied options identified in a rate quote. - - - - - Identifies the type of Freight Guarantee applied, if FREIGHT_GUARANTEE is applied to the rate quote. - - - - - Identifies the smartPostHubId used during rate quote, if SMART_POST_HUB_ID is a variable option on the rate request. - - - - - Identifies the indicia used during rate quote, if SMART_POST_ALLOWED_INDICIA is a variable option on the rate request. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - Specifies the data that is common to dangerous goods packages in the shipment. This is populated when the shipment contains packages with identical dangerous goods commodities. - - - - - - - Shipment-level totals of dry ice data across all packages. - - - - - Total number of packages in the shipment that contain dry ice. - - - - - Total shipment dry ice weight for all packages. - - - - - - - Data for a single leg of a shipment's total/summary rates, as calculated per a specific rate type. - - - - - Human-readable text describing the shipment leg. - - - - - Origin for this leg. - - - - - Specifies the location id the origin of shipment leg. - - - - - Destination for this leg. - - - - - Specifies the location id the destination of shipment leg. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - These values identify which package-level data values will be provided at the shipment-level. - - - - - - - - - - Data for a shipment's total/summary rates, as calculated per a specific rate type. The "total..." fields may differ from the sum of corresponding package data for Multiweight or Express MPS. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Identifies the Rate Details per each leg in a Freight Shipment - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These special services are available at the shipment level for some or all service types. If the shipper is requesting a special service which requires additional data (such as the COD amount), the shipment special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment (or other shipment-level transaction). - - - - - - - - - - This field should be populated for pending shipments (e.g. e-mail label) It is required by a PENDING_SHIPMENT special service type. - - - - - - - - - - - Electronic Trade document references. - - - - - Specification for date or range of dates on which delivery is to be attempted. - - - - - - - Each occurrence of this class specifies a particular way in which a kind of shipping document is to be produced and provided. - - - - - Values in this field specify how to create and return the document. - - - - - Specifies how to organize all documents of this type. - - - - - Specifies how to e-mail document images. - - - - - Specifies how a queued document is to be printed. - - - - - - - Specifies how to return a shipping document to the caller. - - - - - - - - - - - - - - - Specifies how to e-mail shipping documents. - - - - - Provides the roles and email addresses for e-mail recipients. - - - - - Identifies the convention by which documents are to be grouped as e-mail attachments. - - - - - Specifies the language in which the email containing the document is requested to be composed. - - - - - - - - - - - - - Specifies an individual recipient of e-mailed shipping document(s). - - - - - Identifies the relationship of this recipient in the shipment. - - - - - Address to which the document is to be sent. - - - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies how to create, organize, and return the document. - - - - - Specifies how far down the page to move the beginning of the image; allows for printing on letterhead and other pre-printed stock. - - - - - - - For those shipping document types which have both a "form" and "instructions" component (e.g. NAFTA Certificate of Origin and General Agency Agreement), this field indicates whether to provide the instructions. - - - - - - Governs the language to be used for this individual document, independently from other content returned for the same shipment. - - - - - - - Specifies how to organize all shipping documents of the same type. - - - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - Specifies printing options for a shipping document. - - - - - Provides environment-specific printer identification. - - - - - - - Contains all data required for additional (non-label) shipping documents to be produced in conjunction with a specific shipment. - - - - - Indicates the types of shipping documents requested by the shipper. - - - - - - - Specifies the production of each package-level custom document (the same specification is used for all packages). - - - - - Specifies the production of a shipment-level custom document. - - - - - - - - Specifies the production of the OP-900 document for hazardous materials packages. - - - - - Specifies the production of the 1421c document for dangerous goods shipment. - - - - - Specifies the production of the OP-900 document for hazardous materials. - - - - - Specifies the production of the return instructions document. - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These values are mutually exclusive; at most one of them can be attached to a SmartPost shipment. - - - - - - - - - - - - - - - - - - - - - Data required for shipments handled under the SMART_POST and GROUND_SMART_POST service types. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifice the kind of tax or miscellaneous charge being reported on a Commercial Invoice. - - - - - - - - - - - - - - - - - Identifies the usage of Tax Identification Number in Shipment processing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the date until which the document is available - - - - - - - Specifies the application that is responsible for managing the document id. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Description of the uploaded document. - - - - - - - - - - - - - - - - - - - - - This definition of variable handling charge detail is intended for use in Jan 2011 corp load. - - - - - - Actual percentage (10 means 10%, which is a mutiplier of 0.1) - - - - - Select the value from a set of rate data to which the percentage is applied. - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - - - - - - - Three-dimensional volume/cubic measurement. - - - - - - - - - Units of three-dimensional volume/cubic measure. - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/test_server_wsdl/ReturnTagService_v1.wsdl b/fedex/wsdl/test_server_wsdl/ReturnTagService_v1.wsdl deleted file mode 100755 index 3189b7b..0000000 --- a/fedex/wsdl/test_server_wsdl/ReturnTagService_v1.wsdl +++ /dev/null @@ -1,421 +0,0 @@ - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Identifying part of the authentication key. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Identifies the unique client device submitting the request. - - 10 - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data that governs data payload language/translations. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - The descriptive data for the local language and locale (i.e. country). - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code). - - 2 - - - - - - - - The descriptive data regarding the version/level of a service operation performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - - - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. First five characters will be accepted. - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - - - - Identification of a country. - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Identifies the severity of the Notification item. See NotificationSeverityType for list of returned values. - - - - - Identifies the source - what FedEx system, sub-system, or component generated the Notification item. - - - - - Identifies the error code generated by the FedEx system, sub-system or component. - - 8 - - - - - - Identifies the error message text. - - 255 - - - - - - Identifies the error message text in the localization requested. Currently not supported. - - - - - Used internally by FedEx systems for message translation. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - FedEx Express Tag Availability request. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Package ready date and time. - - - - - Sender postal code and country. - - - - - FedEx Service type. - - - - - FedEx Packaging type. - - - - - - - FedEx Express Tag Availability reply. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - This is the minimum time window that must be allocated for the FedEx courier to make the pickup. This is a length of time. The difference between the Business close time, (or the local Cutoff time if it is earlier than the Business Close time), and the Ready Time must be equal to or exceed the access time. - - - - - Latest time a FedEx courier will be available to pick up the package from the Sender. - - - - - Indicates the Express Tag Service availability at the sender postal code indicated in the request. - - - - - - - Identifies the Express Tag Service availability. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/test_server_wsdl/ShipService_v13.wsdl b/fedex/wsdl/test_server_wsdl/ShipService_v13.wsdl deleted file mode 100755 index 12b254a..0000000 --- a/fedex/wsdl/test_server_wsdl/ShipService_v13.wsdl +++ /dev/null @@ -1,6290 +0,0 @@ - - - - - - - - - - - - - - - - - - Specifies additional labels to be produced. All required labels for shipments will be produced without the need to request additional labels. These are only available as thermal labels. - - - - - The type of additional labels to return. - - - - - The number of this type label to return - - - - - - - Identifies the type of additional labels. - - - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - The fully spelt out name of a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Specifies the details around the ADR license required for shipping. - - - - - - - - - - - - - - - Specifies the tracking id for the payment on the return. - - - - - Specifies additional customer reference data about the associated shipment. - - - - - Specifies shipment level operational information. - - - - - Specifies package level operational information on the associated shipment. This information is not tied to an individual outbound package. - - - - - - - - - - - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - - - - - - - - Identification of the type of barcode (symbology) used on FedEx documents and labels. - - - - - - - - - - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as binary data (i.e. not ASCII text). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to Cancel a Pending shipment. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The instructions indicating how to print the Certificate of Origin ( e.g. whether or not to include the instructions, image type, etc ...) - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - - - - - - - Specifies the type of brokerage to be applied to a shipment. - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - Specifies the type of adjustment was performed to the COD collection amount during rating. - - - - - - - - - Identifies the type of funds FedEx should collect upon shipment delivery. - - - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - - Specifies the details of the charges are to be added to the COD collect amount. - - - - - Identifies the type of funds FedEx should collect upon package delivery - - - - - For Express this is the descriptive data that is used for the recipient of the FedEx Letter containing the COD payment. For Ground this is the descriptive data for the party to receive the payment that prints the COD receipt. - - - - - When the FedEx COD payment type is not CASH, indicates the contact and address of the financial institution used to service the payment of the COD. - - - - - Specifies the name of person or company receiving the secured/unsecured funds payment - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - - - Specifies the information associated with a package that has COD special service in a ground shipment. - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through the FedEx Systems. Customers are responsible for printing their own Commercial Invoice.If you would likeFedEx to generate a Commercial Invoice and transmit it to Customs. for clearance purposes, you need to specify that in the ShippingDocumentSpecification element. If you would like a copy of the Commercial Invoice that FedEx generated returned to you in reply it needs to be specified in the ETDDetail/RequestedDocumentCopies element. Commercial Invoice support consists of maximum of 99 commodity line items. - - - - - Any comments that need to be communicated about this shipment. - - - - - Any freight charges that are associated with this shipment. - - - - - Any taxes or miscellaneous charges(other than Freight charges or Insurance charges) that are associated with this shipment. - - - - - Specifies which kind of charge is being recorded in the preceding field. - - - - - Any packing costs that are associated with this shipment. - - - - - Any handling costs that are associated with this shipment. - - - - - Free-form text. - - - - - Free-form text. - - - - - Free-form text. - - - - - The reason for the shipment. Note: SOLD is not a valid purpose for a Proforma Invoice. - - - - - Additional customer reference data. - - - - - Name of the International Expert that completed the Commercial Invoice different from Sender. - - - - - Required for dutiable international Express or Ground shipment. This field is not applicable to an international PIB(document) or a non-document which does not require a Commercial Invoice - - - - - - - The instructions indicating how to print the Commercial Invoice( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies the usage and identification of a customer supplied image to be used on this document. - - - - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Name of this commodity. - - - - - Total number of pieces of this commodity - - - - - Complete and accurate description of this commodity. - - 450 - - - - - - Country code where commodity contents were produced or manufactured in their final form. - - 2 - - - - - - - Unique alpha/numeric representing commodity item. - At least one occurrence is required for US Export shipments if the Customs Value is greater than $2500 or if a valid US Export license is required. - - - 14 - - - - - - Total weight of this commodity. 1 explicit decimal position. Max length 11 including decimal. - - - - - This field is used for enterprise transactions. - - - - - Unit of measure used to express the quantity of this commodity line item. - - 3 - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - Value of each unit in Quantity. Six explicit decimal positions, Max length 18 including decimal. - - - - - - Total customs value for this line item. - It should equal the commodity unit quantity times commodity unit value. - Six explicit decimal positions, max length 18 including decimal. - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - Applicable to US export shipping only. - - 12 - - - - - - - Date of expiration. Must be at least 1 day into future. - The date that the Commerce Export License expires. Export License commodities may not be exported from the U.S. on an expired license. - Applicable to US Export shipping only. - Required only if commodity is shipped on commerce export license, and Export License Number is supplied. - - - - - - - An identifying mark or number used on the packaging of a shipment to help customers identify a particular shipment. - - - 15 - - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - Specifies the results of processing for the COD special service. - - - - - - - - - - - The identifier for all clearance documents associated with this shipment. - - - - - - - - Completed package-level hazardous commodity information for a single package. - - - - - A unique reference id that matches the package to a package configuration. This is populated if the client provided a package configuration for several packages that have the exact same dangerous goods content. - - - - - - When true indicates that the package can be transported only on a cargo aircraft. - - - - - - Specifies the maximum radiation level from the package (measured in microSieverts per hour at a distance of one meter from the external surface of the package, divided by 10). - - - - - Specifies the label that is to be put on a package containing radioactive material. The label type is determined in accordance with the Transportation of Dangerous Goods Act and indicates the type of radioactive material being handled as well as the relative risk. - - - - - Documents the kinds and quantities of all hazardous commodities in the current package. - - - - - - - Computed shipment level hazardous commodity information. - - - - - - - This contains the ADR License information, which identifies the license number and ADR category under which the customer is allowed to ship. - - - - - - - - - Specifies the total number of packages containing hazardous commodities in small exceptions. - - - - - - - - - Identifies the branded location name, the hold at location phone number and the address of the location. - - - - - Identifies the type of FedEx location. - - - - - - - - - The package sequence number of this package in a multiple piece shipment. - - - - - The Tracking number and form id for this package. - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - Oversize class for this package. - - - - - All package-level rating data for this package, which may include data for multiple rate types. - - - - - - The label image or printer commands to print the label. - - - - - All package-level shipping documents (other than labels and barcodes). For use in loads after January, 2008. - - - - - Specifies the information associated with this package that has COD special service in a ground shipment. - - - - - Actual signature option applied, to allow for cases in which the original value conflicted with other service features in the shipment. - - - - - - Documents the kinds and quantities of all hazardous commodities in the current package, using updated hazardous commodity description data. - - - - - - - - - Indicates whether or not this is a US Domestic shipment. - - - - - Indicates the carrier that will be used to deliver this shipment. - - - - - The master tracking number and form id of this multiple piece shipment. This information is to be provided for each subsequent of a multiple piece shipment. - - - - - Description of the FedEx service used for this shipment. Currently not supported. - - 70 - - - - - - Description of the packaging used for this shipment. Currently not supported. - - 40 - - - - - - - Only used with pending shipments. - - - - - Only used in the reply to tag requests. - - - - - Provides reply information specific to SmartPost shipments. - - - - - Computed shipment level information about hazarous commodities. - - - - - All shipment-level rating data for this shipment, which may include data for multiple rate types. - - - - - Returns the default holding location information when HOLD_AT_LOCATION special service is requested and the client does not specify the hold location address. - - - - - Returns any defaults or updates applied to RequestedShipment.exportDetail.exportComplianceStatement. - - - - - - All shipment-level shipping documents (other than labels and barcodes). - - - - - - - Package level details about this package. - - - - - - - Provides reply information specific to SmartPost shipments. - - - - - Identifies the carrier that will pick up the SmartPost shipment. - - - - - Indicates whether the shipment is deemed to be machineable, based on dimensions, weight, and packaging. - - - - - - - Provides reply information specific to a tag request. - - - - - . - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - As of June 2007, returned only for FedEx Express services. - - - - - FEDEX INTERNAL USE ONLY: for use by INET. - - - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - 1 of 12 possible zones to position data. - - - - - The identifiying text for the data in this zone. - - - - - A reference to a field in either the request or reply to print in this zone following the header. - - - - - A literal value to print after the header in this zone. - - - - - - - The descriptive data for a point-of-contact person. - - - - - Client provided identifier corresponding to this contact information. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies a toll free number, if any, associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - Content Record. - - - - - Part Number. - - - - - Item Number. - - - - - Received Quantity. - - - - - Description. - - - - - - - Reply to the Close Request transaction. The Close Reply bring back the ASCII data buffer which will be used to print the Close Manifest. The Manifest is essential at the time of pickup. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Create Pending Shipment Request - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Currency exchange rate information. - - - - - The currency code for the original (converted FROM) currency. - - - - - The currency code for the final (converted INTO) currency. - - - - - Multiplier used to convert fromCurrency units to intoCurrency units. - - - - - - - - - Indicates the type of custom delivery being requested. - - - - - Time by which delivery is requested. - - - - - Range of dates for custom delivery request; only used if type is BETWEEN. - - - - - Date for custom delivery request; only used for types of ON, BETWEEN, or AFTER. - - - - - - - - - - - - - - - Data required to produce a custom-specified document, either at shipment or package level. - - - - - Common information controlling document production. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Applicable only to documents produced on thermal printers with roll stock. - - - - - Identifies the formatting specification used to construct this custom document. - - - - - Identifies the individual document specified by the client. - - - - - If provided, thermal documents will include specified doc tab content. If omitted, document will be produced without doc tab content. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified barcode symbology. - - - - - - - - - Width of thinnest bar/space element in the barcode. - - - - - - - - Solid (filled) rectangular area on label. - - - - - - - - - Valid values for CustomLabelCoordinateUnits - - - - - - - - - - - - - - - - - - Image to be included from printer's memory, or from a local file for offline clients. - - - - - - Printer-specific index of graphic image to be printed. - - - - - Fully-qualified path and file name for graphic image to be printed. - - - - - - - - - Horizontal position, relative to left edge of custom area. - - - - - Vertical position, relative to top edge of custom area. - - - - - - - Constructed string, based on format and zero or more data fields, printed in specified printer font (for thermal labels) or generic font/size (for plain paper labels). - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - Generic font name for use with plain paper labels. - - - - - Generic font size for use with plain paper labels. - - - - - - - - - - - - - - - - - - - - Reference information to be associated with this package. - - - - - The reference type to be associated with this reference data. - - - - - - - - The types of references available for use. - - - - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default is former NONE type). - - - - - Controls the position of the customer specified content relative to the FedEx portion. - - - - - Defines any custom content to print on the label. - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - Controls which data/sections will be suppressed. - - - - - For customers producing their own Ground labels, this field specifies which secondary barcode will be printed on the label; so that the primary barcode produced by FedEx has the correct SCNC. - - - - - - Controls the number of additional copies of supplemental labels. - - - - - This value reduces the default quantity of destination/consignee air waybill labels. A value of zero indicates no change to default. A minimum of one copy will always be produced. - - - - - - - - - - Interacts both with properties of the shipment and contractual relationship with the shipper. - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - - - - - - - - - This provides the information necessary to identify the different statements, declarations, acts, and/or certifications that apply to this shipment. - - - - - This indicates the different statements, declarations, acts, and/or certifications that apply to this shipment. - - - - - Specifies the NAFTA low value statement information. - - - - - - - This indicates the different statements, declarations, acts, and certifications that may apply to a shipment. - - - - - - - - - - - Specifies additional description about customs options. This is a required field when the customs options type is "OTHER". - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Describes an approved container used to package dangerous goods commodities. This does not describe any individual inner receptacles that may be within this container. - - - - - Indicates whether there are additional inner receptacles within this container. - - - - - Indicates the type of this dangerous goods container, as specified by the IATA packing instructions. For example, steel cylinder, fiberboard box, plastic jerrican and steel drum. - - - - - Indicates the packaging type of the container used to package the radioactive materials. - - - - - Indicates the number of occurrences of this container with identical dangerous goods configuration. - - - - - Documents the kinds and quantities of all hazardous commodities in the current container. - - - - - - - The descriptive data required for a FedEx shipment containing dangerous goods (hazardous materials). - - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - Indicates which kinds of hazardous content are in the current package. - - - - - Indicates whether there is additional customer provided packaging enclosing the approved dangerous goods containers. - - - - - Identifies the configuration of this dangerous goods package. The common configuration is represented at the shipment level. - - - - - Indicates one or more containers used to pack dangerous goods commodities. - - - - - Description of the packaging of this commodity, suitable for use on OP-900 and OP-950 forms. - - - - - Name, title and place of the signatory for this shipment. - - - - - Telephone number to use for contact in the event of an emergency. - - - - - Offeror's name or contract number, per DOT regulation. - - - - - Specifies the contact of the party responsible for handling the infectious substances, if any, in the dangerous goods shipment. - - - - - Specifies additional handling information for the current package. - - - - - Specifies the radioactivity detail for the current package, if the package contains radioactive materials. - - - - - - - - - - - - The instructions indicating how to print the 1421c form for dangerous goods shipment. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Specifies that name, title and place of the signatory responsible for the dangerous goods shipment. - - - - - - - Indicates the place where the form is signed. - - - - - - - - - The beginning date in a date range. - - - - - The end date in a date range. - - - - - - - Valid values for DayofWeekType - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to delete a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The timestamp of the shipment request. - - - - - Identifies the FedEx tracking number of the package being cancelled. - - - - - Determines the type of deletion to be performed in relation to package level vs shipment level. - - - - - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Only used for tags which had FedEx Express services. - - - - - Only used for tags which had FedEx Express services. - - - - - If the original ProcessTagRequest specified third-party payment, then the delete request must contain the same pay type and payor account number for security purposes. - - - - - Also known as Pickup Confirmation Number or Dispatch Number - - - - - - - Specifies the type of deletion to be performed on a shipment. - - - - - - - - - - - - - - Specifies the tracking id for the return, if preassigned. - - - - - - - Data required to complete the Destionation Control Statement for US exports. - - - - - List of applicable Statment types. - - - - - Comma-separated list of up to four country codes, required for DEPARTMENT_OF_STATE statement. - - - - - Name of end user, required for DEPARTMENT_OF_STATE statement. - - - - - - - Used to indicate whether the Destination Control Statement is of type Department of Commerce, Department of State or both. - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - - - The DocTabContentType options available. - - - - - The DocTabContentType should be set to ZONE001 to specify additional Zone details. - - - - - The DocTabContentType should be set to BARCODED to specify additional BarCoded details. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Zone number can be between 1 and 12. - - - - - Header value on this zone. - - - - - Reference path to the element in the request/reply whose value should be printed on this zone. - - - - - Free form-text to be printed in this zone. - - - - - Justification for the text printed on this zone. - - - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. - - - - - - - - - - - - Describes specific information about the email label shipment. - - - - - Notification email will be sent to this email address - - - - - Message to be sent in the notification email - - - - - - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - Specifies whether/how email notifications are grouped. - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - The descriptive data for a FedEx email notification recipient. - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - Identifies the set of valid email notification recipient types. For SHIPPER, RECIPIENT and BROKER the email address asssociated with their definitions will be used, any email address sent with the email notification for these three email notification recipient types will be ignored. - - - - - - - - - - - - - - - - - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Electronic Trade document references used with the ETD special service. - - - - - Indicates the types of shipping documents produced for the shipper by FedEx (see ShippingDocumentSpecification) which should be copied back to the shipper in the shipment result data. - - - - - - - - The instructions indicating how to print the Export Declaration. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - - - Country specific details of an International shipment. - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US). - - - - - This field is applicable only to Canada export non-document shipments of any value to any destination. No special characters allowed. - - 10 - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - - - Details specific to an Express freight shipment. - - - - - Indicates whether or nor a packing list is enclosed. - - - - - - Total shipment pieces. - e.g. 3 boxes and 3 pallets of 100 pieces each = Shippers Load and Count of 303. - Applicable to International Priority Freight and International Economy Freight. - Values must be in the range of 1 - 99999 - - - - - - Required for International Freight shipping. Values must be 8- 12 characters in length. - - 12 - - - - - - - - Identifies a kind of FedEx facility. - - - - - - - - - - - - - - - Data required to produce the Freight handling-unit-level address labels. Note that the number of UNIQUE labels (the N as in 1 of N, 2 of N, etc.) is determined by total handling units. - - - - - - Indicates the number of copies to be produced for each unique label. - - - - - Specifies the quadrant of the page on which the label printing will start. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - - - - - Individual charge which contributes to the total base charge for the shipment. - - - - - Freight class for this line item. - - - - - Effective freight class used for rating this line item. - - - - - NMFC Code for commodity. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - Rate or factor applied to this line item. - - - - - Identifies the manner in which the chargeRate for this line item was applied. - - - - - The net or extended charge for this line item. - - - - - - - Specifies the way in which base charges for a Freight shipment or shipment leg are calculated. - - - - - - - - - - - - - - - - - These values represent the industry-standard freight classes used for FedEx Freight and FedEx National Freight shipment description. (Note: The alphabetic prefixes are required to distinguish these values from decimal numbers on some client platforms.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Date for all Freight guarantee types. - - - - - - - - - - - - - Identifies responsibilities with respect to loss, damage, etc. - - - - - - - - - Rate data specific to FedEx Freight or FedEx National Freight services. - - - - - A unique identifier for a specific rate quotation. - - - - - Specifies whether the rate quote was automated or manual. - - - - - Specifies how total base charge is determined. - - - - - Freight charges which accumulate to the total base charge for the shipment. - - - - - Human-readable descriptions of additional information on this shipment rating. - - - - - - - Additional non-monetary data returned with Freight rates. - - - - - Unique identifier for notation. - - - - - Human-readable explanation of notation. - - - - - - - Specifies the type of rate quote - - - - - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Account number used with FEDEX_FREIGHT service. - - - - - Used for validating FedEx Freight account number and (optionally) identifying third party payment on the bill of lading. - - - - - Used in connection with "Send Bill To" (SBT) identification of customer's account used for billing. - - - - - Identification values to be printed during creation of a Freight bill of lading. - - - - - Indicates the role of the party submitting the transaction. - - - - - Designates the terms of the "collect" payment for a Freight Shipment. - - - - - Identifies the declared value for the shipment - - - - - Identifies the declared value units corresponding to the above defined declared value - - - - - - Identifiers for promotional discounts offered to customers. - - - - - Total number of individual handling units in the entire shipment (for unit pricing). - - - - - Estimated discount rate provided by client for unsecured rate quote. - - - - - Total weight of pallets used in shipment. - - - - - Overall shipment dimensions. - - - - - Description for the shipment. - - - - - Specifies which party will pay surcharges for any special services which support split billing. - - - - - Must be populated if any line items contain hazardous materials. - - - - - - Details of the commodities in the shipment. - - - - - - - Description of an individual commodity or class of content in a shipment. - - - - - Freight class for this line item. - - - - - FEDEX INTERNAL USE ONLY: for FedEx system that estimate freight class from customer-provided dimensions and weight. - - - - - Number of individual handling units to which this line applies. (NOTE: Total of line-item-level handling units may not balance to shipment-level total handling units.) - - - - - Specification of handling-unit packaging for this commodity or class line. - - - - - Number of pieces for this commodity or class line. - - - - - NMFC Code for commodity. - - - - - Indicates the kind of hazardous material content in this line item. - - - - - For printed reference per line item. - - - - - Customer-provided description for this commodity or class line. - - - - - Weight for this commodity or class line. - - - - - FED EX INTERNAL USE ONLY - Individual line item dimensions. - - - - - Volume (cubic measure) for this commodity or class line. - - - - - - - Indicates the role of the party submitting the transaction. - - - - - - - - - Specifies which party will be responsible for payment of any surcharges for Freight special services for which split billing is allowed. - - - - - Identifies the special service. - - - - - Indicates who will pay for the special service. - - - - - - - Data required to produce a General Agency Agreement document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - - Represents features of FedEx Ground delivery for which the shipment is eligible. - - - - - - - - - - - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - This describes the inner receptacle details for a hazardous commodity within the dangerous goods container. - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies the details of any radio active materials within the commodity. - - - - - - - Identifies and describes an individual hazardous commodity. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - - - - - - - Indicates any special processing options to be applied to the description of the dangerous goods commodity. - - - - - Information related to quantity limitations and operator or state variations as may be applicable to the dangerous goods commodity. - - - - - - - Specifies any special processing to be applied to the dangerous goods commodity description validation. - - - - - - - - This describes information about the inner receptacles for the hazardous commodity in a particular dangerous goods container. - - - - - This specifies the quantity contained in the inner receptacle. - - - - - - - Specifies how the commodity is to be labeled. - - - - - - - - - - Customer-provided specifications for handling individual commodities. - - - - - Specifies how the customer wishes the label text to be handled for this commodity in this package. - - - - - Text used in labeling the commodity under control of the labelTextOption field. - - - - - - - Indicates which kind of hazardous content is being reported. - - - - - - - - - - - - - Identifies number and type of packaging units for hazardous commodities. - - - - - Number of units of the type below. - - - - - Units in which the hazardous commodity is packaged. - - - - - - - Specifies documentation and limits for validation of an individual packing group/category. - - - - - - Coded specification for how commodity is to be packed. - - - - - - - Identifies DOT packing group for a hazardous commodity. - - - - - - - - - - - Identifies amount and units for quantity of hazardous commodities. - - - - - Number of units of the type below. - - - - - Units by which the hazardous commodity is measured. For IATA commodity, the units values are restricted based on regulation type. - - - - - Specifies which measure of quantity is to be validated. - - - - - - - Specifies the measure of quantity to be validated against a prescribed limit. - - - - - - - - - Identifies the source of regulation for hazardous commodity data. - - - - - - - - - - - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. - - - - - Contact phone number for recipient of shipment. - - - - - Contact and address of FedEx facility at which shipment is to be held. - - - - - Type of facility at which package/shipment is to be held. - - - - - - - The descriptive data required by FedEx for home delivery services. - - - - - The type of Home Delivery Premium service being requested. - - - - - Required for Date Certain Home Delivery. - - - - - Required for Date Certain and Appointment Home Delivery. - - 15 - - - - - - - - The type of Home Delivery Premium service being requested. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The type of International shipment. - - - - - - - - - - - - - - - Specifies the type of label to be returned. - - - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - - - - - Relative to normal orientation for the printer. - - - - - - - - - - - Description of shipping label to be returned in the reply - - - - - Specifies how to create, organize, and return the document. - - - - - Specify type of label to be returned - - - - - Specifies the image format used for a shipping document. - - - - - For thermal printer lables this indicates the size of the label and the location of the doc tab if present. - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - If present, this contact and address information will replace the return address information on the label. - - - - - Allows customer-specified control of label content. - - - - - - - For thermal printer labels this indicates the size of the label and the location of the doc tab if present. - - - - - - - - - - - - - - - - - - - - - - - Identifies the Liability Coverage Amount. For Jan 2010 this value represents coverage amount per pound - - - - - - - - - - - - - - - License or Permit Number. - - - - - Specifies the effective date of the license. - - - - - Specifies the expiration date of the license. - - - - - - - Represents a one-dimensional measurement in small units (e.g. suitable for measuring a package or document), contrasted with Distance, which represents a large one-dimensional measurement (e.g. distance between cities). - - - - - The numerical quantity of this measurement. - - - - - The units for this measurement. - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - - - - - - - Identifies which type minimum charge was applied. - - - - - - - - - - - - The descriptive data for the medium of exchange for FedEx services. - - - - - Identifies the currency of the monetary amount. - - 3 - - - - - - Identifies the monetary amount. - - - - - - - Data required to produce a Certificate of Origin document. Remaining content (business data) to be defined once requirements have been completed. - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - Contact information for "Authorized Signature" area of form. - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - Date range over which RVC net cost was calculated. - - - - - - - - - - - - - - - Specifies the information necessary for printing the NAFTA Low Value statement on customs documentation. - - - - - Specifies the NAFTA statement role. - - - - - - - Net cost method used. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The instructions indicating how to print the OP-900 form for hazardous materials packages. - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Identifies which reference type (from the package's customer references) is to be used as the source for the reference on this OP-900. - - - - - Specifies the usage and identification of customer supplied images to be used on this document. - - - - - Data field to be used when a name is to be printed in the document instead of (or in addition to) a signature image. - - - - - - - - - Position of operational instruction element. - - - - - Content corresponding to the operational instruction. - - - - - - - The oversize class types. - - - - - - - - - - Each instance of this data type represents the set of barcodes (of all types) which are associated with a specific package. - - - - - Binary-style barcodes for this package. - - - - - String-style barcodes for this package. - - - - - - - Package-level data required for labeling and/or movement. - - - - - Human-readable text for pre-January 2011 clients. - - - - - Human-readable content for use on a label. - - - - - The operational barcodes pertaining to the current package. - - - - - The FedEx internal code that represents the service and/or features of service for the current package moving under a FedEx Ground service. - - - - - - - Data for a package's rates, as calculated per a specific rate type. - - - - - Type used for this specific set of rate data. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - The weight that was used to calculate the rate. - - - - - The dimensional weight of this package (if greater than actual). - - - - - The oversize weight of this package (if the package is oversize). - - - - - The transportation charge only (prior to any discounts applied) for this package. - - - - - The sum of all discounts on this package. - - - - - This package's baseCharge - totalFreightDiscounts. - - - - - The sum of all surcharges on this package. - - - - - This package's netFreight + totalSurcharges (not including totalTaxes). - - - - - The sum of all taxes on this package. - - - - - This package's netFreight + totalSurcharges + totalTaxes. - - - - - The total sum of all rebates applied to this package. - - - - - All rate discounts that apply to this package. - - - - - All rebates that apply to this package. - - - - - All surcharges that apply to this package (either because of characteristics of the package itself, or because it is carrying per-shipment surcharges for the shipment of which it is a part). - - - - - All taxes applicable (or distributed to) this package. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - - - This class groups together for a single package all package-level rate data (across all rate types) as part of the response to a shipping request, which groups shipment-level data together and groups package-level data by package. - - - - - This rate type identifies which entry in the following array is considered as presenting the "actual" rates for the package. - - - - - The "list" net charge minus "actual" net charge. - - - - - Each element of this field provides package-level rate data for a specific rate type. - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Ground shipments only. - - - - - - - - - - - - - - - These special services are available at the package level for some or all service types. If the shipper is requesting a special service which requires additional data, the package special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment or package. - - - - - For use with FedEx Ground services only; COD must be present in shipment's special services. - - - - - Descriptive data required for a FedEx shipment containing dangerous materials. This element is required when SpecialServiceType.DANGEROUS_GOODS or HAZARDOUS_MATERIAL is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for a FedEx shipment containing dry ice. This element is required when SpecialServiceType.DRY_ICE is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx signature services. This element is required when SpecialServiceType.SIGNATURE_OPTION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Priority Alert service. This element is required when SpecialServiceType.PRIORITY_ALERT is present in the SpecialServiceTypes collection. - - - - - - - Identifies the collection of available FedEx or customer packaging options. - - - - - - - - - - - - - - - - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data for the monetary compensation given to FedEx for services rendered to the customer. - - - - - Identifies the method of payment for a service. See PaymentType for list of valid enumerated values. - - - - - Descriptive data identifying the party responsible for payment for a service. - - - - - - - Identifies the method of payment for a service. - - - - - - - - - - - - The descriptive data identifying the party responsible for payment for a service. - - - - - - - - This information describes how and when a pending shipment may be accessed for completion. - - - - - Only for pending shipment type of "EMAIL" - - - - - Only for pending shipment type of "EMAIL" - - - - - Only for pending shipment type of "EMAIL" - - - - - This element is currently not supported and is for the future use. - - - - - - - This information describes the kind of pending shipment being requested. - - - - - Identifies the type of FedEx pending shipment - - - - - Date after which the pending shipment will no longer be available for completion. - - - - - Only used with type of EMAIL. - - - - - - - Identifies the type of service for a pending shipment. - - - - - - - - - - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This class describes the pickup characteristics of a shipment (e.g. for use in a tag request). - - - - - - - - Identifies the type of Pickup request - - - - - Identifies the type of source for Pickup request - - - - - - - Identifies the type of source for pickup request service. - - - - - - - - - Identifies the type of pickup request service. - - - - - - - - - Identifies the type of pricing used for this shipment. - - - - - - - - - - - - - - - - - - - - Represents a reference identifier printed on Freight bills of lading - - - - - - - - - Identifies a particular reference identifier printed on a Freight bill of lading. - - - - - - - - - - - - - - - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - Empty unless error label behavior is PACKAGE_ERROR_LABELS and one or more errors occured during transaction processing. - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - - - - - - - - - Indicates the packaging type of the container used to package radioactive hazardous materials. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicates whether packaging type "EXCEPTED" or "EXCEPTED_PACKAGE" is for radioactive material in reportable quantity. - - - - - - - - - Indicates the reason that a dim divisor value was chose. - - - - - - - - - - - - Identifies a discount applied to the shipment. - - - - - Identifies the type of discount applied to the shipment. - - - - - - The amount of the discount applied to the shipment. - - - - - The percentage of the discount applied to the shipment. - - - - - - - The type of the discount. - - - - - - - - - - - - - Selects the value from a set of rate data to which the percentage is applied. - - - - - - - - - - - Identifies the type(s) of rates to be returned in the reply. - - - - - - - - - - Select the type of rate from which the element is to be selected. - - - - - - - - - The weight method used to calculate the rate. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies how the recipient is identified for customs purposes; the requirements on this information vary with destination country. - - - - - Specifies the kind of identification being used. - - - - - Contains the actual ID value, of the type specified above. - - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin - - - - - - - - - - Describes the vertical position of an item relative to another item. - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - - Specifies the declared value for carriage of the package. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the package. This field is only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case total weight and packageCount on the shipment will be used to determine this value. - - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - The descriptive data for the shipment being tendered to FedEx. - - - - - Identifies the date and time the package is tendered to FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the shipment based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). There is also a UTC offset component indicating the number of hours/mainutes from UTC (e.g 2006-06-26T17:00:00-0400 is defined form June 26, 2006 5:00 pm Eastern Time). - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. See DropoffType for list of valid enumerated values. - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - Identifies the total weight of the shipment being conveyed to FedEx.This is only applicable to International shipments and should only be used on the first package of a mutiple piece shipment.This value contains 1 explicit decimal position - - - - - Specifies the total declared value for carriage of the shipment. The declared value for carriage represents the maximum liability of FedEx in connection with a shipment, including, but not limited to, any loss, damage, delay, mis-delivery, nondelivery, misinformation, any failure to provide information, or mis-delivery of information relating to the shipment. - - - - - This attribute indicates the currency the caller requests to have used in all returned monetary values (when a choice is possible). - - - - - Descriptive data identifying the party responsible for shipping the package. Shipper and Origin should have the same address. - - - - - Descriptive data identifying the party receiving the package. - - - - - A unique identifier for a recipient location - - 10 - - - - - - Physical starting address for the shipment, if different from shipper's address. - - - - - Descriptive data indicating the method and means of payment to FedEx for providing shipping services. - - - - - Descriptive data regarding special services requested by the shipper for this shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Details specific to an Express freight shipment. - - - - - Data applicable to shipments using FEDEX_FREIGHT_ECONOMY and FEDEX_FREIGHT_PRIORITY services. - - - - - Used with Ground Home Delivery and Freight. - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - Customs clearance data, used for both international and intra-country shipping. - - - - - For use in "process tag" transaction. - - - - - Specifies the characteristics of a shipment pertaining to SmartPost services. - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - Details about the image format and printer type the label is to returned in. - - - - - Contains data used to create additional (non-label) shipping documents. - - - - - Specifies whether and what kind of rates the customer wishes to have quoted on this shipment. The reply will also be constrained by other data on the shipment and customer. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - Only used with multiple-transaction shipments, to identify the master package in a multi-piece shipment. - - - - - The total number of packages in the entire shipment (even when the shipment spans multiple transactions.) - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies the tracking number of the master associated with the return shipment. - - - - - - - - These values are used to control the availability of certain special services at the time when a customer uses the e-mail label link to create a return shipment. - - - - - - - - - Return Email Details - - - - - Phone number of the merchant - - - - - Identifies the allowed (merchant-authorized) special services which may be selected when the subsequent shipment is created. Only services represented in EMailLabelAllowedSpecialServiceType will be controlled by this list. - - - - - - - The instructions indicating how to print the return instructions( e.g. image type) Specifies characteristics of a shipping document to be produced. - - - - - - Specifies additional customer provided text to be inserted into the return document. - - - - - - - Information relating to a return shipment. - - - - - The type of return shipment that is being requested. - - - - - Return Merchant Authorization - - - - - Describes specific information about the email label for return shipment. - - - - - - - - The type of return shipment that is being requested. - - - - - - - - - - The "PAYOR..." rates are expressed in the currency identified in the payor's rate table(s). The "RATED..." rates are expressed in the currency of the origin country. Former "...COUNTER..." values have become "...RETAIL..." values, except for PAYOR_COUNTER and RATED_COUNTER, which have been removed. - - - - - - - - - - - - - - - - - - - - Shipping document type. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - June 2011 ITG 121203 IR-RMA number has been removed from this structure and added as a new customer reference type. The structure remains because of the reason field below. - - - - - The reason for the return. - - 60 - - - - - - - - Describes the rotation of an item from its default orientation. - - - - - - - - - - - - - - - - - - - Identifies the collection of available FedEx service options. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Specifies data structures that may be re-used multiple times with s single shipment. - - - - - Specifies the data that is common to dangerous goods packages in the shipment. This is populated when the shipment contains packages with identical dangerous goods commodities. - - - - - - - Shipment-level totals of dry ice data across all packages. - - - - - Total number of packages in the shipment that contain dry ice. - - - - - Total shipment dry ice weight for all packages. - - - - - - - Data for a single leg of a shipment's total/summary rates, as calculated per a specific rate type. - - - - - Human-readable text describing the shipment leg. - - - - - Origin for this leg. - - - - - Specifies the location id the origin of shipment leg. - - - - - Destination for this leg. - - - - - Specifies the location id the destination of shipment leg. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - - Identifies the type of dim divisor that was applied. - - - - - - - Sum of dimensional weights for all packages. - - - - - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - - - - - - - - - - - This is the state of the destination location ID, and is not necessarily the same as the postal state. - - - - - Expected/estimated date of delivery. - - - - - Expected/estimated day of week of delivery. - - - - - Delivery time, as published in Service Guide. - - - - - Committed date of delivery. - - - - - Committed day of week of delivery. - - - - - Standard transit time per origin, destination, and service. - - - - - Maximum expected transit time - - - - - Transit time based on customer eligibility. - - - - - Indicates that this shipment is not eligible for money back guarantee. - - - - - FedEx Ground delivery features for which this shipment may be eligible. - - - - - Text describing planned delivery. - - - - - - - - - - - - - - Data for a shipment's total/summary rates, as calculated per a specific rate type. The "total..." fields may differ from the sum of corresponding package data for Multiweight or Express MPS. - - - - - Type used for this specific set of rate data. - - - - - Indicates the rate scale used. - - - - - Indicates the rate zone used (based on origin and destination). - - - - - Identifies the type of pricing used for this shipment. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Specifies the currency exchange performed on financial amounts for this rate. - - - - - Indicates which special rating cases applied to this shipment. - - - - - The value used to calculate the weight based on the dimensions. - - - - - Identifies the type of dim divisor that was applied. - - - - - Specifies a fuel surcharge percentage. - - - - - The weight used to calculate these rates. - - - - - Sum of dimensional weights for all packages. - - - - - The total freight charge that was calculated for this package before surcharges, discounts and taxes. - - - - - The total discounts used in the rate calculation. - - - - - The freight charge minus discounts. - - - - - The total amount of all surcharges applied to this shipment. - - - - - This shipment's totalNetFreight + totalSurcharges (not including totalTaxes). - - - - - Total of the transportation-based taxes. - - - - - The net charge after applying all discounts and surcharges. - - - - - The total sum of all rebates applied to this shipment. - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - Identifies the Rate Details per each leg in a Freight Shipment - - - - - Rate data specific to FedEx Freight and FedEx National Freight services. - - - - - All rate discounts that apply to this shipment. - - - - - All rebates that apply to this shipment. - - - - - All surcharges that apply to this shipment. - - - - - All transportation-based taxes applicable to this shipment. - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The "order level" variable handling charges. - - - - - The total of all variable handling charges at both shipment (order) and package level. - - - - - - - This class groups together all shipment-level rate data (across all rate types) as part of the response to a shipping request, which groups shipment-level data together and groups package-level data by package. - - - - - This rate type identifies which entry in the following array is considered as presenting the "actual" rates for the shipment. - - - - - The "list" total net charge minus "actual" total net charge. - - - - - Each element of this field provides shipment-level rate totals for a specific rate type. - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Express shipments only. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These special services are available at the shipment level for some or all service types. If the shipper is requesting a special service which requires additional data (such as the COD amount), the shipment special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object below. - - - - - The types of all special services requested for the enclosing shipment (or other shipment-level transaction). - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. This element is required when SpecialServiceType.COD is present in the SpecialServiceTypes collection. - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. This element is required when SpecialServiceType.HOLD_AT_LOCATION is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for FedEx to provide email notification to the customer regarding the shipment. This element is required when SpecialServiceType.EMAIL_NOTIFICATION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Printed Return Label. This element is required when SpecialServiceType.PRINTED_RETURN_LABEL is present in the SpecialServiceTypes collection - - - - - This field should be populated for pending shipments (e.g. e-mail label) It is required by a PENDING_SHIPMENT special service type. - - - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - The descriptive data required for FedEx Home Delivery options. This element is required when SpecialServiceType.HOME_DELIVERY_PREMIUM is present in the SpecialServiceTypes collection - - - - - - Electronic Trade document references. - - - - - Specification for date or range of dates on which delivery is to be attempted. - - - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Shipping Document Type - - - - - Specifies how this document image/file is organized. - - - - - - The name under which a STORED or DEFERRED document is written. - - - - - Specifies the image type of this shipping document. - - - - - Specifies the image resolution in DPI (dots per inch). - - - - - Can be zero for documents whose disposition implies that no content is included. - - - - - One or more document parts which make up a single logical document, such as multiple pages of a single form. - - - - - - - Each occurrence of this class specifies a particular way in which a kind of shipping document is to be produced and provided. - - - - - Values in this field specify how to create and return the document. - - - - - Specifies how to organize all documents of this type. - - - - - Specifies how to e-mail document images. - - - - - Specifies how a queued document is to be printed. - - - - - - - Specifies how to return a shipping document to the caller. - - - - - - - - - - - - - - Specifies how to e-mail shipping documents. - - - - - Provides the roles and email addresses for e-mail recipients. - - - - - Identifies the convention by which documents are to be grouped as e-mail attachments. - - - - - - - - - - - - - Specifies an individual recipient of e-mailed shipping document(s). - - - - - Identifies the relationship of this recipient in the shipment. - - - - - Address to which the document is to be sent. - - - - - - - Specifies characteristics of a shipping document to be produced. - - - - - Specifies how to create, organize, and return the document. - - - - - Specifies how far down the page to move the beginning of the image; allows for printing on letterhead and other pre-printed stock. - - - - - - - For those shipping document types which have both a "form" and "instructions" component (e.g. NAFTA Certificate of Origin and General Agency Agreement), this field indicates whether to provide the instructions. - - - - - Governs the language to be used for this individual document, independently from other content returned for the same shipment. - - - - - Identifies the individual document specified by the client. - - - - - - - Specifies how to organize all shipping documents of the same type. - - - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - - - - A single part of a shipping document, such as one page of a multiple-page document whose format requires a separate image per page. - - - - - The one-origin position of this part within a document. - - - - - Graphic or printer commands for this image within a document. - - - - - - - Specifies printing options for a shipping document. - - - - - Provides environment-specific printer identification. - - - - - - - Contains all data required for additional (non-label) shipping documents to be produced in conjunction with a specific shipment. - - - - - Indicates the types of shipping documents requested by the shipper. - - - - - - - Specifies the production of each package-level custom document (the same specification is used for all packages). - - - - - Specifies the production of a shipment-level custom document. - - - - - - This element is currently not supported and is for the future use. (Details pertaining to the GAA.) - - - - - - Specifies the production of the OP-900 document for hazardous materials packages. - - - - - Specifies the production of the 1421c document for dangerous goods shipment. - - - - - Specifies the production of the OP-900 document for hazardous materials. - - - - - Specifies the production of the return instructions document. - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - - - - - The descriptive data required for FedEx delivery signature services. - - - - - Identifies the delivery signature services option selected by the customer for this shipment. See OptionType for the list of valid values. - - - - - Identifies the delivery signature release authorization number. - - 10 - - - - - - - - Identifies the delivery signature services options offered by FedEx. - - - - - - - - - - - - These values are mutually exclusive; at most one of them can be attached to a SmartPost shipment. - - - - - - - - - - - - - - - - - - - - - Data required for shipments handled under the SMART_POST and GROUND_SMART_POST service types. - - - - - - - - - The CustomerManifestId is used to group Smart Post packages onto a manifest for each trailer that is being prepared. If you do not have multiple trailers this field can be omitted. If you have multiple trailers, you - must assign the same Manifest Id to each SmartPost package as determined by its trailer. In other words, all packages on a trailer must have the same Customer Manifest Id. The manifest Id must be unique to your account number for a minimum of 6 months - and cannot exceed 8 characters in length. We recommend you use the day of year + the trailer id (this could simply be a sequential number for that trailer). So if you had 3 trailers that you started loading on Feb 10 - the 3 manifest ids would be 041001, 041002, 041003 (in this case we used leading zeros on the trailer numbers). - - - - - - - - Special circumstance rating used for this shipment. - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - Identifies each surcharge applied to the shipment. - - - - - The type of surcharge applied to the shipment. - - - - - - - The amount of the surcharge applied to the shipment. - - - - - - - - - - - - - The type of the surcharge. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies each tax applied to the shipment. - - - - - The type of tax applied to the shipment. - - - - - - The amount of the tax applied to the shipment. - - - - - - - The type of the tax. - - - - - - - - - - - - - - Specifice the kind of tax or miscellaneous charge being reported on a Commercial Invoice. - - - - - - - - - - - - - The descriptive data for taxpayer identification information. - - - - - Identifies the category of the taxpayer identification number. See TinType for the list of values. - - - - - Identifies the taxpayer identification number. - - 15 - - - - - - Identifies the usage of Tax Identification Number in Shipment processing - - - - - - - - Required for dutiable international express or ground shipment. This field is not applicable to an international PIB (document) or a non-document which does not require a commercial invoice express shipment. - CFR_OR_CPT (Cost and Freight/Carriage Paid TO) - CIF_OR_CIP (Cost Insurance and Freight/Carraige Insurance Paid) - DDP (Delivered Duty Paid) - DDU (Delivered Duty Unpaid) - EXW (Ex Works) - FOB_OR_FCA (Free On Board/Free Carrier) - - - - - - - - - - - - - - - - Identifies the category of the taxpayer identification number. - - - - - - - - - - - - - - - - For use with SmartPost tracking IDs only - - - - - - - - TrackingIdType - - - - - - - - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the set of valid shipment transit time values. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to validate a shipment. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Documents the kind and quantity of an individual hazardous commodity in a package. - - - - - Identifies and describes an individual hazardous commodity. - - - - - Specifies the amount of the commodity in alternate units. - - - - - The mass points are a calculation used by ADR regulations for measuring the risk of a particular hazardous commodity. - - - - - Customer-provided specifications for handling individual commodities. - - - - - - - Identifies and describes an individual hazardous commodity. For 201001 load, this is based on data from the FedEx Ground Hazardous Materials Shipping Guide. - - - - - Regulatory identifier for a commodity (e.g. "UN ID" value). - - - - - In conjunction with the regulatory identifier, this field uniquely identifies a specific hazardous materials commodity. - - - - - - - - Fully-expanded descriptive text for a hazardous commodity. - - - - - - - - Coded indications for special requirements or constraints. - - - - - - - - - - - - Specifies the concept of a container used to package dangerous goods commodities. - - - - - Indicates that the quantity of the dangerous goods packaged is permissible for shipping. This is used to ensure that the dangerous goods commodities do not exceed the net quantity per package restrictions. - - - - - Documents the kinds and quantities of all hazardous commodities in the current package. - - - - - - - This definition of variable handling charge detail is intended for use in Jan 2011 corp load. - - - - - - Used with Variable handling charge type of FIXED_VALUE. - Contains the amount to be added to the freight charge. - Contains 2 explicit decimal positions with a total max length of 10 including the decimal. - - - - - - Actual percentage (10 means 10%, which is a mutiplier of 0.1) - - - - - Select the value from a set of rate data to which the percentage is applied. - - - - - Select the type of rate from which the element is to be selected. - - - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The variable handling charge amount calculated based on the requested variable handling charge detail. - - - - - - - The calculated varibale handling charge plus the net charge. - - - - - - - Three-dimensional volume/cubic measurement. - - - - - - - - - Units of three-dimensional volume/cubic measure. - - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - Identifies the unit of measure associated with a weight value. See the list of enumerated types for valid values. - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/fedex/wsdl/test_server_wsdl/ShipService_v7.wsdl b/fedex/wsdl/test_server_wsdl/ShipService_v7.wsdl deleted file mode 100755 index 49437e5..0000000 --- a/fedex/wsdl/test_server_wsdl/ShipService_v7.wsdl +++ /dev/null @@ -1,4656 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the type of additional labels. - - - - - - - - - - - - - - - The descriptive data for a physical location. - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - 35 - - - - - - Name of city, town, etc. - - - 35 - 20 - - - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - 14 - - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. This element is required if both the City and StateOrProvinceCode are not present. - - 16 - - - - - - Relevant only to addresses in Puerto Rico. In Puerto Rico, multiple addresses within the same ZIP code can have the same house number and street name. When this is the case, the urbanization code is needed to distinguish them. - - 100 - - - - - - Identification of a country. - - 2 - - - - - - Indicates whether this address is residential (as opposed to commercial). - - - - - - - - - - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to Cancel a Pending shipment. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The FedEx account number assigned to the customer initiating the request. - - 12 - - - - - - Identifies the unique client device submitting the request. This number is assigned by FedEx and identifies the unique device from which the request is originating. - - 10 - - - - - - - Governs any future language/translations used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - Identifies what freight charges should be added to the COD collect amount. - - - - - - - - - - - - - - - - - - - - - Identifies the type of funds FedEx should collect upon package delivery. - - - - - - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. - - - - - Identifies if freight charges are to be added to the COD amount. This element determines which freight charges should be added to the COD collect amount. See CodAddTransportationChargesType for the list of valid enumerated values. - - - - - Identifies the type of funds FedEx should collect upon package delivery. See CodCollectionType for the list of valid enumerated values. - - - - - Descriptive data about the recipient of the COD shipment. - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - Indicates which type of reference information to include on the COD return shipping label. - - - - - - - - - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service. - - - - - Currently not supported. - - TBD - - - - - - The description of the FedEx service type used for the COD return shipment. Currently not supported. - - 70 - - - - - - The description of the packaging used for the COD return shipment. - - 40 - - - - - - Currently not supported. - - TBD - - - - - - Currently not supported. - - - - - Currently not supported. - - - - - The CodRoutingDetail element will contain the COD return tracking number and form id. In the case of a COD multiple piece shipment these will need to be inserted in the request for the last piece of the multiple piece shipment. - The service commitment is the only other element of the RoutingDetail that is used for a CodRoutingDetail. - - - - - - Contains the data which form the Astra and 2DCommon barcodes that print on the COD return label. - - - - - The label image or printer commands to print the label. - - - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through FedEx System. Customers are responsible for printing their own Commercial Invoice. Commercial Invoice support consists of a maximum of 99 commodity line items. - - - - - Commercial Invoice comments to be uploaded to customs. - - 444 - - - - - - Format: Two explicit decimal positions max length 19 including decimal. - Required if Terms Of Sale is CFR or CIF. - This charge should be added to the total customs value amount. - - - - - - Format: Two explicit decimal positions max length 19 including decimal. - This charge should be added to the total customs value amount. - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - Customer assigned invoice number. - - 15 - - - - - - Defines the terms of the sale. - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - ? - - - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Name of this commodity. - - - - - Total number of pieces of this commodity - - - - - Complete and accurate description of this commodity. - - 450 - - - - - - Country code where commodity contents were produced or manufactured in their final form. - - 2 - - - - - - - Unique alpha/numeric representing commodity item. - At least one occurrence is required for US Export shipments if the Customs Value is greater than $2500 or if a valid US Export license is required. - - - 14 - - - - - - Total weight of this commodity. 1 explicit decimal position. Max length 11 including decimal. - - - - - Number of units of a commodity in total number of pieces for this line item. Max length is 9 - - - - - Unit of measure used to express the quantity of this commodity line item. - - 3 - - - - - - Contains only additional quantitative information other than weight and quantity to calculate duties and taxes. - - - - - Value of each unit in Quantity. Six explicit decimal positions, Max length 18 including decimal. - - - - - Total customs value for this line item. - It should equal the commodity unit quantity times commodity unit value. - Six explicit decimal positions, max length 18 including decimal. - - - - - - Defines additional characteristic of commodity used to calculate duties and taxes - - - - - Applicable to US export shipping only. - - 12 - - - - - - Date of expiration. Must be at least 1 day into future. - The date that the Commerce Export License expires. Export License commodities may not be exported from the U.S. on an expired license. - Applicable to US Export shipping only. - Required only if commodity is shipped on commerce export license, and Export License Number is supplied. - - - - - - An identifying mark or number used on the packaging of a shipment to help customers identify a particular shipment. - - - 15 - - - - - - All data required for this commodity in NAFTA Certificate of Origin. - - - - - - - - - The package sequence number of this package in a multiple piece shipment. - - - - - The Tracking number and form id for this package. - - - - - Used with request containing PACKAGE_GROUPS, to identify which group of identical packages was used to produce a reply item. - - - - - Oversize class for this package. - - - - - The rating information for this package. Note, this is a courtesy rate and may be different from what is invoiced. - - - - - The data that is used to from the Astra and 2DCommon barcodes for the label.. - - - - - The textual description of the special service applied to the package. - - - - - The label image or printer commands to print the label. - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Information about the COD return shipment. - - - - - The actual signature option applied to this shipment. This could be different than the signature option requested if a conflict occured with other service features in the shipment. - - - - - - - - - Indicates whether or not this is a US Domestic shipment. - - - - - Indicates the carrier that will be used to deliver this shipment. - - - - - The master tracking number and form id of this multiple piece shipment. This information is to be provided for each subsequent of a multiple piece shipment. - - - - - Description of the FedEx service used for this shipment. Currently not supported. - - 70 - - - - - - Description of the packaging used for this shipment. Currently not supported. - - 40 - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The code indicating the Ground service type and any special services associated with this shipment. Currently not supported. - - - - - Access Details about PendingShipment information. - - - - - Only used in the reply to tag requests. - - - - - Provides reply information specific to SmartPost shipments. - - - - - The rating information for this shipment. Note, this is a courtesy rate and may be different from what is invoiced. - - - - - Information about the COD return shipment. - - - - - Indicates whether or not this shipment is eligible for a money back guarantee. - - - - - General field for exporting-country-specific export data (e.g. B13A for CA, FTSR Exemption or AES Citation for US. - - - - - - All shipment-level shipping documents (other than labels and barcodes). - - - - - Package level details about this package. - - - - - - - - - - - - Provides reply information specific to a tag request. - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - 1 of 12 possible zones to position data. - - - - - The identifiying text for the data in this zone. - - - - - A reference to a field in either the request or reply to print in this zone following the header. - - - - - A literal value to print after the header in this zone. - - - - - - - The descriptive data for a point-of-contact person. - - - - - Identifies the contact person's name. - - 35 - - - - - - Identifies the contact person's title. Not currently used. - - - - - Identifies the contact person's company name. - - 35 - - - - - - Identifies the contact person's phone number. - - 15 - - - - - - Identifies the contact person's pager number. - - 15 - - - - - - Identifies the contact person's fax machine phone number. - - 15 - - - - - - Identifies the contact person's email address. - - 120 - - - - - - - - - - - - - - Create Pending Shipment Request - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - The descriptive data identifying the client submitting the transaction. - - - - - The descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Reply to the Close Request transaction. The Close Reply bring back the ASCII data buffer which will be used to print the Close Manifest. The Manifest is essential at the time of pickup. - - - - - Identifies the highest severity encountered when executing the request; in order from high to low: FAILURE, ERROR, WARNING, NOTE, SUCCESS. - - - - - The descriptive data detailing the status of a sumbitted transaction. - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Currency exchange rate information. - - - - - The currency type being converted from. - - - - - The currency type being converted to. - - - - - The resulting amount. - - - - - - - Content Record. - - - - - Part Number. - - - - - Item Number. - - - - - Received Quantity. - - - - - Description. - - - - - - - Reference information to be associated with this package. - - - - - The reference type to be associated with this reference data. - - - - - - - - The types of references available for use. - - - - - - - - - - - - - - Allows customer-specified control of label content. - - - - - If omitted, no doc tab will be produced (i.e. default = former NONE type). - - - - - Defines any custom content to print on the label. - - - - - Defines additional data to print in the Configurable portion of the label, this allows you to print the same type information on the label that can also be printed on the doc tab. - - - - - Data to exclude from printing on the label. - - - - - - - - - - - - - - - - - - - - - - - - - - Valid values for CustomLabelCoordinateUnits - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Printer-specific font name for use with thermal printer labels. - - - - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - - - - The descriptive data required for a FedEx shipment containing dangerous goods (hazardous materials). - - - - - Identifies whether or not the products being shipped are required to be accessible during delivery. - - - - - Shipment is packaged/documented for movement ONLY on cargo aircraft. - - - - - - - - - - - - - The beginning date in a date range. - - - - - The end date in a date range. - - - - - - - Valid values for DayofWeekType - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to delete a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The timestamp of the shipment request. - - - - - Identifies the FedEx tracking number of the package being cancelled. - - - - - Determines the type of deletion to be performed in relation to package level vs shipment level. - - - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Express Location Identifier. - - - - - The date FedEx will attempt to pick up the shipment from the Sender. - - - - - - Also known as Pickup Confirmation Number or Dispatch Number - - - - - - - Valid values for DeletionControlType - - - - - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - List of applicable Statment types. - - - - - Countries this shipment is destined for. - - - - - Department of State End User. - - - - - - - Used to indicate whether the Destination Control Statement is of type Department of Commerce, Department of State or both. - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - - - - - - - - - - - - - - - The DocTabContentType options available. - - - - - The DocTabContentType should be set to ZONE001 to specify additional Zone details. - - - - - The DocTabContentType should be set to BARCODED to specify additional BarCoded details. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Zone number can be between 1 and 12. - - - - - Header value on this zone. - - - - - Reference path to the element in the request/reply whose value should be printed on this zone. - - - - - Free form-text to be printed in this zone. - - - - - Justification for the text printed on this zone. - - - - - - - - - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. - - - - - - - - - - - - Describes the special services the merchant will allow on a return shipment. - - - - - - - - - Describes specific information about the email label shipment. - - - - - Notification email will be sent to this email address - - - - - Message to be sent in the notification email - - - - - - - The descriptive data required for FedEx to provide email notification to the customer regarding the shipment. - - - - - Identifies the message text to be sent in the email notification. - - 120 - - - - - - The descriptive data element for the collection of email recipients. - - - - - - - A unique format can be specified for each email address indicated. The format will apply to notification emails sent to a particular email address. - - - - - - - - - - The descriptive data for a FedEx email notification recipient. - - - - - Identifies the email notification recipient type. See EMailNotificationRecipientType for a list of valid enumerated values. - - - - - Identifies the email address of the notification recipient. - - 120 - - - - - - Identifies if an email notification should be sent to the recipient when the package is shipped. - - - - - Identifies if an email notification should be sent to the recipient when an exception occurs during package movement from origin to destination. - - - - - Identifies if an email notification should be sent to the recipient when the package is delivered. - - - - - A unique format can be specified for each email address indicated. The format will apply to notification emails sent to a particular email address.. - - - - - Indicates the language the notification is expressed in. - - - - - - - Identifies the set of valid email notification recipient types. For SHIPPER, RECIPIENT and BROKER the email address asssociated with their definitions will be used, any email address sent with the email notification for these three email notification recipient types will be ignored. - - - - - - - - - - - Country specific details of an International shipment. - - - - - Specifies which filing option is being exercised by the customer. - Required for non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands. - - - - - - Required only if B13AFilingOption is one of the following: - FILED_ELECTRONICALLY - MANUALLY_ATTACHED - SUMMARY_REPORTING - If B13AFilingOption = NOT_REQUIRED, this field should contain a valid B13A Exception Number. - - - 50 - - - - - - This field is applicable only to Canada export non-document shipments of any value to any destination. No special characters allowed. - - 10 - - - - - - Department of Commerce/Department of State information about this shipment. - - - - - - - Details specific to an Express freight shipment. - - - - - Indicates whether or nor a packing list is enclosed. - - - - - Total shipment pieces. - e.g. 3 boxes and 3 pallets of 100 pieces each = Shippers Load and Count of 303. - Applicable to International Priority Freight and International Economy Freight. - Values must be in the range of 1 - 99999 - - - - - - Required for International Freight shipping. Values must be 8- 12 characters in length. - - 12 - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - to be included in the OP-950 (Hazardous Materials Certificate) returned in Close reply - - - - - which broad class (as established by the United States DOT) the contents of this shipment falls into; The user should be aware that these (up to three) 50-character elements will actually be formatted on the certificate in a 25-character-wide column on up to six lines; Up to 25 characters of the first element will appear on the first line, and any additional characters starting with the 26th will appear on a second line. The first 25 of the second element, if it exists, will appear on a third line, and any additional characters starting with the 26th will appear on the fourth line. The first 25 characters of the third element will appear on a fifth line, and any additional characters starting with the 26th will appear on a sixth line. - - 50 - - - - - - which broad class (as established by the United States Department of Transportation) the contents of this shipment falls into. - - 25 - - - - - - ID Number (UN or NA number), including prefix. - - 11 - - - - - - Type of D.O.T. diamond hazard label, or "Ltd. Qty.", or Exemption Number. - - 50 - - - - - - materials in certain classes, the Packing Group signifies the degree of hazard. - - 3 - - - - - - Quantity (in the given unites) of dangerous goods in shipment. - - - - - - - - - - Units in which the Quantity is expressed. - - 4 - - - - - - 24-hour emergency response contact phone number. - - 15 - - - - - - 24-hour emergency response contact name. - - 50 - - - - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. - - - - - Identifies a telephone number. - - 15 - - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data required by FedEx for home delivery services. - - - - - The type of Home Delivery Premium service being requested. - - - - - Required for Date Certain Home Delivery. - - - - - Required for Date Certain and Appointment Home Delivery. - - 15 - - - - - - - - The type of Home Delivery Premium service being requested. - - - - - - - - - - - - Descriptive data identifying the Broker responsible for the shipment. - Required if BROKER_SELECT_OPTION is requested in Special Services. - - - - - - Applicable only for Commercial Invoice. If the consignee and importer are not the same, the Following importer fields are required. - Importer/Contact/PersonName - Importer/Contact/CompanyName - Importer/Contact/PhoneNumber - Importer/Address/StreetLine[0] - Importer/Address/City - Importer/Address/StateOrProvinceCode - if Importer Country Code is US or CA - Importer/Address/PostalCode - if Importer Country Code is US or CA - Importer/Address/CountryCode - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - Indicates how payment of duties for the shipment will be made. - - - - - Indicates whether this shipment contains documents only or non-documents. - - - - - The total customs value for the shipment. This total will rrepresent th esum of the values of all commodities, and may include freight, miscellaneous, and insurance charges. Must contain 2 explicit decimal positions with a max length of 17 including the decimal. For Express International MPS, the Total Customs Value is in the master transaction and all child transactions - - - - - Documents amount paid to third party for coverage of shipment content. - - - - - CommercialInvoice element is required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial Invoice through FedEx System. Customers are responsible for printing their own Commercial Invoice. Commercial Invoice support consists of a maximum of 20 commodity line items. - - - - - For international multiple piece shipments, commodity information must be passed in the Master and on each child transaction. - If this shipment cotains more than four commodities line items, the four highest valued should be included in the first 4 occurances for this request. - - - - - - Country specific details of an International shipment. - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin. - - - - - - - The type of International shipment. - - - - - - - - - Specifies the type of label to be returned. - - - - - - - - - Names for data elements / areas which may be suppressed from printing on labels. - - - - - - - - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - - - - - Description of shipping label to be returned in the reply - - - - - Specify type of label to be returned - - - - - Specifies the image format used for a shipping document. - - - - - For thermal printer lables this indicates the size of the label and the location of the doc tab if present. - - - - - This indicates if the top or bottom of the label comes out of the printer first. - - - - - If present, this contact and address information will replace the return address information on the label. - - - - - Allows customer-specified control of label content. - - - - - - - Specifies the image format used for a shipping document. - - - - - - - - - - - - For thermal printer labels this indicates the size of the label and the location of the doc tab if present. - - - - - - - - - - - - - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Governs any future language/translations used for human-readable text. - - - - - Identifies the language to use for human-readable messages. - - 2 - - - - - - Identifies the locale (i.e. country code) associated with the language. - - 2 - - - - - - - - Identifies which type minimum charge was applied. - - - - - - - - - - - - The descriptive data for the medium of exchange for FedEx services. - - - - - Identifies the currency of the monetary amount. - - 3 - - - - - - Identifies the monetary amount. - - - - - - - - - - This element is currently not supported and is for the future use. (The descriptive data regarding NAFTA COO.) - - - - - - - - - - - - - - - Indicates which Party (if any) from the shipment is to be used as the source of importer data on the NAFTA COO form. - - - - - - - - - - - - - - - - - - - - ? - - - - - - - This element is currently not supported and is for the future use. - - - - - Defined by NAFTA regulations. - - - - - Defined by NAFTA regulations. - - - - - Identification of which producer is associated with this commodity (if multiple producers are used in a single shipment). - - - - - - - - - - Date range over which RVC net cost was calculated. - - - - - - - Net cost method used. - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - - - - - - See instructions for NAFTA Certificate of Origin for code definitions. - - - - - - - - - - - This element is currently not supported and is for the future use. - - - - - - - - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - The severity of this notification. this can indicate success or failure or some other information about the request such as errors or notes. - - - - - Indicates the source of the notification. Combined with Code, it uniqely identifies this message. - - - - - A code that represents this notification. Combined with Source, it uniqely identifies this message. - - 8 - - - - - - Text that explains this notification. - - 255 - - - - - - A translated message. The translation is based on the Localization element of the ClientDetail element of the request. Not currently supported - - - - - If the message used parameter replacement to be specific as to the meaning of the message, this is the list of parameters that were used. - - - - - - - - - Name identifiying the type of the data in the element 'Value' - - - - - The value that was used as the replacement parameter. - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - The oversize class types. - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as binary data (i.e. not ASCII text). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - Each instance of this data type represents the set of barcodes (of all types) which are associated with a specific package. - - - - - Binary-style barcodes for this package. - - - - - String-style barcodes for this package. - - - - - - - - - The type of rates this information contains either account based or list rates. - - - - - The method used to calculate the weight to be used in rating the package. - - - - - The method used to calculate the weight to be used in rating the package. - - - - - The weight that was used to calculate the rate. - - - - - The dimensional weight that was calculated for this package. - - - - - The oversize weight that was used in the rate calculation. - - - - - The freight charge that was calculated for this package before surcharges, discounts and taxes.. - - - - - The total discounts used in the rate calculation. - - - - - The base charge minus discounts. - - - - - The total amount of all surcharges applied to this package. - - - - - - The total sum of all taxes applied to this package. - - - - - The the charge for this package including surcharges, discounts and taxes. - - - - - The total sum of all rebates applied to this package. - - - - - A list of discounts that were applied to this package. - - - - - - A list of the surcharges applied to this package. - - - - - A list of the taxes applied to this package. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - - - Package level rate information. - - - - - Identifies which entry in the PackageRateDetails array is considered as presenting the actual rates for the package. - - - - - The difference between account based rates and list rates. Only returned when list rates are requested. - - - - - Each element of this field provides package-level rate data for a specific rate type. - - - - - - - Descriptive data regarding special services requested by the shipper for a shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Identifies the collection of special service types requested by the shipper. See SpecialServiceTypes for the list of valid enumerated types. - - - - - The COD amount that must be collected upon delivery of a package shipped using the COD special service. - - - - - Descriptive data required for a FedEx shipment containing dangerous materials. This element is required when SpecialServiceType.DANGEROUS_GOODS or HAZARDOUS_MATERIAL is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for a FedEx shipment containing dry ice. This element is required when SpecialServiceType.DRY_ICE is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx signature services. This element is required when SpecialServiceType.SIGNATURE_OPTION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Priority Alert service. This element is required when SpecialServiceType.PRIORITY_ALERT is present in the SpecialServiceTypes collection. - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Ground shipments only. - - - - - - - - - - - - - Identifies the collection of available FedEx or customer packaging options. - - - - - - - - - - - - - - The descriptive data for a person or company entitiy doing business with FedEx. - - - - - Identifies the FedEx account number assigned to the customer. - - 12 - - - - - - Descriptive data for taxpayer identification information. - - - - - Descriptive data identifying the point-of-contact person. - - - - - The descriptive data for a physical location. - - - - - - - The descriptive data for the monetary compensation given to FedEx for services rendered to the customer. - - - - - Identifies the method of payment for a service. See PaymentType for list of valid enumerated values. - - - - - Descriptive data identifying the party responsible for payment for a service. - - - - - - - Identifies the method of payment for a service. - - - - - - - - - - - The descriptive data identifying the party responsible for payment for a service. - - - - - Identifies the FedEx account number assigned to the payor. - - 12 - - - - - - Identifies the country of the payor. - - 2 - - - - - - - - Descriptive data for FedEx pending shipment - - - - - Provides the url for accessing email label. - - - - - User id. - - - - - Password. - - - - - This element is currently not supported and is for the future use. - - - - - - - The descriptive data for FedEx pending shipment - - - - - Identifies the type of FedEx pending shipment - - - - - Date when the pending shipment expires. - - - - - Descriptive data about notification email - - - - - - - Identifies the type of service for a pending shipment. - - - - - - - - - - - - - Identifies the type of Pickup request - - - - - Identifies the type of source for Pickup request - - - - - - - Identifies the type of source for pickup request service. - - - - - - - - - Identifies the type of pickup request service. - - - - - - - - - Identifies the type of pricing used for this shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The reply payload. All of the returned information about this shipment/package. - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to ship a package. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Test for the Commercial Invoice. Note that Sold is not a valid Purpose for a Proforma Invoice. - - - - - - - - - - - - - Identifies a discount applied to the shipment. - - - - - Identifies the type of discount applied to the shipment. - - - - - - The amount of the discount applied to the shipment. - - - - - The percentage of the discount applied to the shipment. - - - - - - - The type of the discount. - - - - - - - - - - - The weight method used to calculate the rate. - - - - - - - - - - - - - - - - - Identifies the type(s) of rates to be returned in the reply. - - - - - - - - - Type of Brazilian taxpayer identifier provided in Recipient/TaxPayerIdentification/Number. For shipments bound for Brazil this overrides the value in Recipient/TaxPayerIdentification/TinType - - - - - - - - - - FOOD_OR_PERISHABLE is required by FDA/BTA; must be true for food/perishable items coming to US or PR from non-US/non-PR origin - - - - - - - - - - The descriptive data for the shipment being tendered to FedEx. - - - - - Identifies the date and time the package is tendered to FedEx. Both the date and time portions of the string are expected to be used. The date should not be a past date or a date more than 10 days in the future. The time is the local time of the shipment based on the shipper's time zone. The date component must be in the format: YYYY-MM-DD (e.g. 2006-06-26). The time component must be in the format: HH:MM:SS using a 24 hour clock (e.g. 11:00 a.m. is 11:00:00, whereas 5:00 p.m. is 17:00:00). The date and time parts are separated by the letter T (e.g. 2006-06-26T17:00:00). There is also a UTC offset component indicating the number of hours/mainutes from UTC (e.g 2006-06-26T17:00:00-0400 is defined form June 26, 2006 5:00 pm Eastern Time). - - - - - Identifies the method by which the package is to be tendered to FedEx. This element does not dispatch a courier for package pickup. See DropoffType for list of valid enumerated values. - - - - - Identifies the FedEx service to use in shipping the package. See ServiceType for list of valid enumerated values. - - - - - Identifies the packaging used by the requestor for the package. See PackagingType for list of valid enumerated values. - - - - - Identifies the total weight of the shipment being conveyed to FedEx.This is only applicable to International shipments and should only be used on the first package of a mutiple piece shipment.This value contains 1 explicit decimal position - - - - - Total insured amount. - - - - - Descriptive data identifying the party responsible for shipping the package. Shipper and Origin should have the same address. - - - - - Descriptive data identifying the party receiving the package. - - - - - A unique identifier for a recipient location - - 10 - - - - - - Physical starting address for the shipment, if different from Shipper Address. - - - - - Descriptive data indicating the method and means of payment to FedEx for providing shipping services. - - - - - Descriptive data regarding special services requested by the shipper for this shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Details specific to an Express freight shipment. - - - - - Used with Ground Home Delivery and Freight. - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - Information about this package that only applies to an international (export) shipment. - - - - - - - If true, only the shipper/payor will have visibility of this shipment. - - - - - Details about the image format and printer type the label is to returned in. - - - - - Details such as shipping document types, NAFTA information, CI information, and GAA information. - - - - - Indicates the type of rates to be returned. - - - - - Specifies whether the customer wishes to have Estimated Duties and Taxes provided with the rate quotation on this shipment. Only applies with shipments moving under international services. - - - - - Used when requesting child pieces in a multiple piece shipment. The master tracking information will be returned in reply from the first package requested for a multiple piece shipment. That master tracking information is then inserted into the requests for each additional package requested for that multiple pice shipment. - - - - - Only used with multi-piece COD shipments sent in multiple transactions. Required on last transaction only. - - - - - For a multiple piece shipment this is the total number of packages in the shipment. - - - - - Specifies whether packages are described individually,in groups, or summarized in a single description for total-piece-total-weight. This field controls which fields of the RequestedPackageLineItem will be used, and how many occurrences are expected. - - - - - One or more package-attribute descriptions, each of which describes an individual package, a group of identical packages, or (for the total-piece-total-weight case) common characteristics all packages in the shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - Return Email Details - - - - - Phone number of the merchant - - - - - Allowed Special service type - - - - - - - - - - - - - - - - - - Information relating to a return shipment. - - - - - The type of return shipment that is being requested. - - - - - Return Merchant Authorization - - - - - Describes specific information about the email label for return shipment. - - - - - - - The type of return shipment that is being requested. - - - - - - - - - - Shipping document type. - - - - - - - - - - - - - - - - - - - - - - - Return Merchant Authorization - - - - - The RMA number. - - 20 - - - - - - The reason for the return. - - 60 - - - - - - - - The tracking number information and the data to form the Astra barcode for the label. - - - - - The tracking number information for the shipment. - - - - - - - The textual description of the special service applied to the package. - - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The routing information detail for this shipment. - - - - - The tracking number information and the data to form the Astra barcode for the label. - - - - - - - Identifies the collection of available FedEx service options. - - - - - - - - - - - - - - - - - - - - - - - - All package-level shipping documents (other than labels and barcodes). - - - - - Shipping Document Type - - - - - Number of copies to print. - - - - - One or more document parts which make up a single logical document, such as - multiple pages of a single form. - - - - - - - - Format of shipping documents - - - - - - - - - - - - - - - - - - - - - - One or more document parts which make up a single logical document, such as - multiple pages of a single form. - - - - - - The one-origin position of this part within a document. - - - - - Graphic or printer commands for this image within a document. - - - - - - - Description of shipping documents - - - - - Specify type of documents - - - - - ? - - - - - ? - - - - - ? - - - - - This element is currently not supported and is for the future use. (Details pertaining to the GAA.) - - - - - ? - - - - - - - Specifies the type of paper (stock) on which a document will be printed. - - - - - - - - - - - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - - - - - Shipment level rate information. Currently this is the same as the package level rate information. - - - - - The type used for this specific set of rate data. - - - - - The FedEx rate scale used to calculate these rates. - - 5 - - - - - - The FedEx rate zone used to calculate these rates. - - 1 - - - - - - Identifies the type of pricing used for this shipment. - - - - - Indicates which weight was used. - - - - - INTERNAL FEDEX USE ONLY. - - - - - Currency exchange rate information. - - - - - Special circumstance rating used for this shipment. - - - - - The value used to calculate the weight based on the dimensions. - - - - - Specifies a fuel surcharge percentage. - - - - - The weight used to calculate these rates. - - - - - The dimensional weith used to calculate these rates, if applicible. - - - - - The total freight charge that was calculated for this package before surcharges, discounts and taxes. - - - - - The total discounts used in the rate calculation. - - - - - The freight charge minus discounts. - - - - - The total amount of all surcharges applied to this shipment. - - - - - - The total amount of all taxes applied to this shipment. Currently not supported. - - - - - The net charge after applying all discounts and surcharges. - - - - - The total sum of all rebates applied to this shipment. - - - - - Total of all values under this shipment's dutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment. - - - - - This shipment's totalNetCharge + totalDutiesAndTaxes; only provided if estimated duties and taxes were calculated for this shipment AND duties, taxes and transportation charges are all paid by the same sender's account. - - - - - - - - - All commodity-based duties and taxes applicable to this shipment. - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The total of the package and shipment level variable handling charges. - - - - - - - - - - - - - - - - - - - - - - Shipment level rate information. - - - - - Identifies which entry in the ShipmentRateDetails array is considered as presenting the actual rates for the shipment. - - - - - The difference between account based rates and list rates. Only returned when list rates are requested. - - - - - Each element of this field provides shipment-level rate data for a specific rate type. - - - - - - - - - This indicates the highest level of severity of all the notifications returned in this reply - - - - - The descriptive data regarding the results of the submitted transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - - - Information about the routing, origin, destination and delivery of a shipment. - - - - - The prefix portion of the URSA (Universal Routing and Sort Aid) code. - - 2 - - - - - - The suffix portion of the URSA code. - - 5 - - - - - - The identifier of the origin location of the shipment. Express only. - - 5 - - - - - - - The identifier of the destination location of the shipment. Express only. - - 5 - - - - - - - The state or province code of the destination of the shipment. - - 14 - - - - - - The date the shipment is expected to be delivered. - - - - - The day of the week the shipment is expected to be delivered. Express only. - - - - - The date the shipment is committed to be delivered. - - - - - The day of the week the shipment is committed to be delivered. Express only. - - - - - Currently not supported. - - - - - Text describing planned delivery. - - - - - Currently not supported. - - TBD - - - - - - The postal code of the destination of the shipment. - - 16 - - - - - - The state or province code of the destination of the shipment. - - 14 - - - - - - The country code of the destination of the shipment. - - 2 - - - - - - The identifier for the airport of the destination of the shipment. - - 4 - - - - - - - - Descriptive data regarding special services requested by the shipper for a shipment. If the shipper is requesting a special service which requires additional data (e.g. COD), the special service type must be present in the specialServiceTypes collection, and the supporting detail must be provided in the appropriate sub-object. For example, to request COD, "COD" must be included in the SpecialServiceTypes collection and the CodDetail object must contain the required data. - - - - - Identifies the collection of special service types requested by the shipper. See SpecialServiceTypes for the list of valid enumerated types. - - - - - Descriptive data required for a FedEx COD (Collect-On-Delivery) shipment. This element is required when SpecialServiceType.COD is present in the SpecialServiceTypes collection. - - - - - The COD amount (after any accumulations) that must be collected upon delivery of a shipment shipped using the COD special service. - - - - - Descriptive data required for a FedEx shipment that is to be held at the destination FedEx location for pickup by the recipient. This element is required when SpecialServiceType.HOLD_AT_LOCATION is present in the SpecialServiceTypes collection. - - - - - Descriptive data required for FedEx to provide email notification to the customer regarding the shipment. This element is required when SpecialServiceType.EMAIL_NOTIFICATION is present in the SpecialServiceTypes collection. - - - - - The descriptive data required for FedEx Printed Return Label. This element is required when SpecialServiceType.PRINTED_RETURN_LABEL is present in the SpecialServiceTypes collection - - - - - The descriptive data required for FedEx Pending shipment. This element is required when SpecialServiceType.PENDING_SHIPMENT is present in the SpecialServiceTypes collection - - - - - Number of packages in this shipment which contain dry ice and the total weight of the dry ice for this shipment. - - - - - The descriptive data required for FedEx Home Delivery options. This element is required when SpecialServiceType.HOME_DELIVERY_PREMIUM is present in the SpecialServiceTypes collection - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies the collection of special service offered by FedEx. BROKER_SELECT_OPTION should be used for Express shipments only. - - - - - - - - - - - - - - - - - - - - - The descriptive data required for FedEx delivery signature services. - - - - - Identifies the delivery signature services option selected by the customer for this shipment. See OptionType for the list of valid values. - - - - - Identifies the delivery signature release authorization number. - - 10 - - - - - - - - Identifies the delivery signature services options offered by FedEx. - - - - - - - - - - - - - - - - - - - - - - - - The CustomerManifestId is used to group Smart Post packages onto a manifest for each trailer that is being prepared. If you do not have multiple trailers this field can be omitted. If however you - have multiple trailers a manifest Id must be assigned to each Smart Post package determined by the trailer it is being loaded onto. The manifest Id must be unique to your account number for a minimum of 6 months - and cannot exceed 8 characters in length. We recommend you use the day of year + the trailer id (this could simply be a sequential number for that trailer). So if you had 3 trailers that you started loading on Feb 10 - the 3 manifest ids would be 041001, 041002, 041003 (in this case we used leading zeros on the trailer numbers). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Special circumstance rating used for this shipment. - - - - - - - - - Identifies each surcharge applied to the shipment. - - - - - The type of surcharge applied to the shipment. - - - - - - - The amount of the surcharge applied to the shipment. - - - - - - - The type of the surcharge. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Identifies each tax applied to the shipment. - - - - - The type of tax applied to the shipment. - - - - - - The amount of the tax applied to the shipment. - - - - - - - The descriptive data for taxpayer identification information. - - - - - Identifies the category of the taxpayer identification number. See TinType for the list of values. - - - - - Identifies the taxpayer identification number. - - 15 - - - - - - - - The type of the tax. - - - - - - - - - - - - - Required for dutiable international express or ground shipment. This field is not applicable to an international PIB (document) or a non-document which does not require a commercial invoice express shipment. - CFR_OR_CPT (Cost and Freight/Carriage Paid TO) - CIF_OR_CIP (Cost Insurance and Freight/Carraige Insurance Paid) - DDP (Delivered Duty Paid) - DDU (Delivered Duty Unpaid) - EXW (Ex Works) - FOB_OR_FCA (Free On Board/Free Carrier) - - - - - - - - - - - - - - Identifies the category of the taxpayer identification number. - - - - - - - - - - - - - - - - TrackingIdType - - - - - - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies a customer-supplied unique identifier for this transaction. It is returned in the reply message to aid in matching requests to replies. - - 40 - - - - - - Governs any future language/translations applied to the data payload(contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - Identifies the set of valid shipment transit time values. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Descriptive data sent to FedEx by a customer in order to validate a shipment. - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Descriptive data for this customer transaction. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Descriptive data about the shipment being sent by the requestor. - - - - - - - Details about how to calculate variable handling charges at the shipment level. - - - - - The type of handling charge to be calculated and returned in the reply. - - - - - Used with Variable handling charge type of FIXED_VALUE. - Contains the amount to be added to the freight charge. - Contains 2 explicit decimal positions with a total max length of 10 including the decimal. - - - - - - Used with Variable handling charge types PERCENTAGE_OF_BASE, PERCENTAGE_OF_NET or PERCETAGE_OF_NET_EXCL_TAXES. - Used to calculate the amount to be added to the freight charge. - Contains 2 explicit decimal positions. - - - - - - - - The variable handling charges calculated based on the type variable handling charges requested. - - - - - The variable handling charge amount calculated based on the requested variable handling charge detail. - - - - - The calculated varibale handling charge plus the net charge. - - - - - - - The type of handling charge to be calculated and returned in the reply. - - - - - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. For this release this value should be set to 6. - - - - - Identifies the service interface level. For this release this value should be set to 0. - - - - - Identifies the service code level. For this release this value should be set to 0. - - - - - - - The descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity. - - - - - Publicly known part of authentication key used for authentication. This value is provided by FedEx after registration. - - 16 - - - - - - Secret part of authentication key used for authentication. This value is provided by FedEx after registration. - - 25 - - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. See WeightUnits for the list of valid enumerated values. - - - - - Identifies the weight value of the package/shipment. Contains 1 explicit decimal position - - - - - - - - - - - - Identifies the unit of measure associated with a weight value. See the list of enumerated types for valid values. - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - Customer-declared value, with data type and legal values depending on excise condition, used in defining the taxable value of the item. - - - - - - - Specifies the types of Estimated Duties and Taxes to be included in a rate quotation for an international shipment. - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - - This class rationalizes RequestedPackage and RequestedPackageSummary from previous interfaces. The way in which it is uses within a RequestedShipment depends on the RequestedPackageDetailType value specified for that shipment. - - - - - Used only with INDIVIDUAL_PACKAGE, as a unique identifier of each requested package. - - - - - Used only with PACKAGE_GROUPS, as a unique identifier of each group of identical packages. - - - - - Used only with PACKAGE_GROUPS, as a count of packages within a group of identical packages. - - - - - ? - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalInsuredValue and packageCount on the shipment will be used to determine this value. - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. Ignored for PACKAGE_SUMMARY, in which case totalweight and packageCount on the shipment will be used to determine this value. - - - - - ? - - - - - Provides additional detail on how the customer has physically packaged this item. As of June 2009, required for packages moving under international and SmartPost services. - - - - - Human-readable text describing the package. - - - - - ? - - - - - ? - - - - - Only used for INDIVIDUAL_PACKAGES and PACKAGE_GROUPS. - - - - - - - This enumeration rationalizes the former FedEx Express international "admissibility package" types (based on ANSI X.12) and the FedEx Freight packaging types. The values represented are those common to both carriers. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - ? - - - - - - - ? - - - - - - - - - - ? - - - - - - - - - - - ? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/fedex/wsdl/test_server_wsdl/TrackService_v5.wsdl b/fedex/wsdl/test_server_wsdl/TrackService_v5.wsdl deleted file mode 100755 index 2c9f815..0000000 --- a/fedex/wsdl/test_server_wsdl/TrackService_v5.wsdl +++ /dev/null @@ -1,1510 +0,0 @@ - - - - - - - - - - - - - - Descriptive data for a physical location. May be used as an actual physical address (place to which one could go), or as a container of "address parts" which should be handled as a unit (such as a city-state-ZIP combination within the US). - - - - - Combination of number, street name, etc. At least one line is required for a valid physical address; empty lines should not be included. - - - - - Name of city, town, etc. - - - - - Identifying abbreviation for US state, Canada province, etc. Format and presence of this field will vary, depending on country. - - - - - Identification of a region (usually small) for mail/package delivery. Format and presence of this field will vary, depending on country. - - - - - Relevant only to addresses in Puerto Rico. - - - - - The two-letter code used to identify a country. - - - - - Indicates whether this address residential (as opposed to commercial). - - - - - - - Identifies where a tracking event occurs. - - - - - - - - - - - - - - - - - - - - - - - - - - - Identification of a FedEx operating company (transportation). - - - - - - - - - - - - - Descriptive data for the client submitting a transaction. - - - - - The FedEx account number associated with this transaction. - - - - - This number is assigned by FedEx and identifies the unique device from which the request is originating - - - - - Only used in transactions which require identification of the Fed Ex Office integrator. - - - - - The language to be used for human-readable Notification.localizedMessages in responses to the request containing this ClientDetail object. Different requests from the same client may contain different Localization data. (Contrast with TransactionDetail.localization, which governs data payload language/translation.) - - - - - - - The descriptive data for a point-of-contact person. - - - - - Identifies the contact person's name. - - - - - Identifies the contact person's title. - - - - - Identifies the company this contact is associated with. - - - - - Identifies the phone number associated with this contact. - - - - - Identifies the phone extension associated with this contact. - - - - - Identifies the pager number associated with this contact. - - - - - Identifies the fax number associated with this contact. - - - - - Identifies the email address associated with this contact. - - - - - - - - - - - - - The dimensions of this package and the unit type used for the measurements. - - - - - - - - - - - Driving or other transportation distances, distinct from dimension measurements. - - - - - Identifies the distance quantity. - - - - - Identifies the unit of measure for the distance value. - - - - - - - Identifies the collection of units of measure that can be associated with a distance value. - - - - - - - - - Information describing email notifications that will be sent in relation to events that occur during package movement - - - - - A message that will be included in the email notifications - - - - - Information describing the destination of the email, format of the email and events to be notified on - - - - - - - - - - - - - - - The format of the email - - - - - - - - - - - - Identifies the relationship this email recipient has to the shipment. - - - - - The email address to send the notification to - - - - - The types of email notifications being requested for this recipient. - - - - - The format of the email notification. - - - - - The language/locale to be used in this email notification. - - - - - - - - - - - - - - - CM = centimeters, IN = inches - - - - - - - - - Identifies the representation of human-readable text. - - - - - Two-letter code for language (e.g. EN, FR, etc.) - - - - - Two-letter code for the region (e.g. us, ca, etc..). - - - - - - - The descriptive data regarding the result of the submitted transaction. - - - - - The severity of this notification. This can indicate success or failure or some other information about the request. The values that can be returned are SUCCESS - Your transaction succeeded with no other applicable information. NOTE - Additional information that may be of interest to you about your transaction. WARNING - Additional information that you need to know about your transaction that you may need to take action on. ERROR - Information about an error that occurred while processing your transaction. FAILURE - FedEx was unable to process your transaction at this time due to a system failure. Please try again later - - - - - Indicates the source of this notification. Combined with the Code it uniquely identifies this notification - - - - - A code that represents this notification. Combined with the Source it uniquely identifies this notification. - - - - - Human-readable text that explains this notification. - - - - - The translated message. The language and locale specified in the ClientDetail. Localization are used to determine the representation. Currently only supported in a TrackReply. - - - - - A collection of name/value pairs that provide specific data to help the client determine the nature of an error (or warning, etc.) witout having to parse the message string. - - - - - - - - - Identifies the type of data contained in Value (e.g. SERVICE_TYPE, PACKAGE_SEQUENCE, etc..). - - - - - The value of the parameter (e.g. PRIORITY_OVERNIGHT, 2, etc..). - - - - - - - Identifies the set of severity values for a Notification. - - - - - - - - - - - - - - - - - - - - Identification for a FedEx operating company (transportation and non-transportation). - - - - - - - - The enumerated packaging type used for this package. - - - - - - - - - - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - FedEx assigned identifier for a package/shipment. - - - - - The date the package was shipped. - - - - - If the account number used to ship the package is provided in the request the shipper and recipient information is included on the letter or fax. - - - - - FedEx operating company that delivered the package. - - - - - Only country is used for elimination of duplicate tracking numbers. - - - - - - - - - - - - - - The service type of the package/shipment. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FedEx Signature Proof Of Delivery Fax reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - Confirmation of fax transmission. - - - - - - - FedEx Signature Proof Of Delivery Fax request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - Additional customer-supplied text to be added to the body of the letter. - - - - - Contact and address information about the person requesting the fax to be sent. - - - - - Contact and address information, including the fax number, about the person to receive the fax. - - - - - - - Identifies the set of SPOD image types. - - - - - - - - FedEx Signature Proof Of Delivery Letter reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Image of letter encoded in Base64 format. - - - - - Image of letter encoded in Base64 format. - - - - - - - FedEx Signature Proof Of Delivery Letter request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - Tracking number and additional shipment data used to identify a unique shipment for proof of delivery. - - - - - Additional customer-supplied text to be added to the body of the letter. - - - - - Identifies the set of SPOD image types. - - - - - If provided this information will be print on the letter. - - - - - - - Each instance of this data type represents a barcode whose content must be represented as ASCII text (i.e. not binary data). - - - - - The kind of barcode data in this instance. - - - - - The data content of this instance. - - - - - - - - - - - - - - - - - The delivery location at the delivered to address. - - - - - - - - - - - - - - - - Detailed tracking information about a particular package. - - - - - To report soft error on an individual track detail. - - - - - The FedEx package identifier. - - - - - - When duplicate tracking numbers exist this data is returned with summary information for each of the duplicates. The summary information is used to determine which of the duplicates the intended tracking number is. This identifier is used on a subsequent track request to retrieve the tracking data for the desired tracking number. - - - - - A code that identifies this type of status. This is the most recent status. - - - - - A human-readable description of this status. - - - - - Used to report the status of a piece of a multiple piece shipment which is no longer traveling with the rest of the packages in the shipment or has not been accounted for. - - - - - Used to convey information such as. 1. FedEx has received information about a package but has not yet taken possession of it. 2. FedEx has handed the package off to a third party for final delivery. 3. The package delivery has been cancelled - - - - - Identifies a FedEx operating company (transportation). - - - - - Identifies operating transportation company that is the specific to the carrier code. - - - - - Specifies the FXO production centre contact and address. - - - - - Other related identifiers for this package such as reference numbers. - - - - - Retained for legacy compatibility only. User/screen friendly description of the Service type (e.g. Priority Overnight). - - - - - Strict representation of the Service type (e.g. PRIORITY_OVERNIGHT). - - - - - The weight of this package. - - - - - Physical dimensions of the package. - - - - - The dimensional weight of the package. - - - - - The weight of the entire shipment. - - - - - Retained for legacy compatibility only. - - - - - Strict representation of the Packaging type (e.g. FEDEX_BOX, YOUR_PACKAGING). - - - - - The sequence number of this package in a shipment. This would be 2 if it was package number 2 of 4. - - - - - The number of packages in this shipment. - - - - - - - The address information for the shipper. - - - - - The address of the FedEx pickup location/facility. - - - - - Estimated package pickup time for shipments that haven't been picked up. - - - - - Time package was shipped/tendered over to FedEx. Time portion will be populated if available, otherwise will be set to midnight. - - - - - The distance from the origin to the destination. Returned for Custom Critical shipments. - - - - - Total distance package still has to travel. Returned for Custom Critical shipments. - - - - - The address this package is to be (or has been) delivered. - - - - - The address of the FedEx delivery location/facility. - - - - - Projected package delivery time based on ship time stamp, service and destination. Not populated if delivery has already occurred. - - - - - The time the package was actually delivered. - - - - - Actual address where package was delivered. Differs from destinationAddress, which indicates where the package was to be delivered; This field tells where delivery actually occurred (next door, at station, etc.) - - - - - Identifies the method of office order delivery. - - - - - Strict text indicating the delivery location at the delivered to address. - - - - - User/screen friendly representation of the DeliveryLocationType (delivery location at the delivered to address). Can be returned in localized text. - - - - - This is either the name of the person that signed for the package or "Signature not requested" or "Signature on file". - - - - - True if signed for by signature image is available. - - - - - The types of email notifications that are available for the package. - - - - - Returned for cargo shipments only when they are currently split across vehicles. - - - - - Indicates redirection eligibility as determined by tracking service, subject to refinement/override by redirect-to-hold service. - - - - - Event information for a tracking number. - - - - - - - FedEx scanning information about a package. - - - - - The time this event occurred. - - - - - Carrier's scan code. Pairs with EventDescription. - - - - - Literal description that pairs with the EventType. - - - - - Further defines the Scan Type code's specific type (e.g., DEX08 business closed). Pairs with StatusExceptionDescription. - - - - - Literal description that pairs with the StatusExceptionCode. - - - - - Address information of the station that is responsible for the scan. - - - - - Indicates where the arrival actually occurred. - - - - - - - The type of track to be performed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FedEx assigned identifier for a package/shipment. - - - - - When duplicate tracking numbers exist this data is returned with summary information for each of the duplicates. The summary information is used to determine which of the duplicates the intended tracking number is. This identifier is used on a subsequent track request to retrieve the tracking data for the desired tracking number. - - - - - Identification of a FedEx operating company (transportation). - - - - - The date the package was shipped (tendered to FedEx). - - - - - The destination address of this package. Only city, state/province, and country are returned. - - - - - Options available for a tracking notification recipient. - - - - - - - Options available for a tracking notification recipient. - - - - - The types of email notifications available for this recipient. - - - - - - - FedEx Track Notification reply. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - True if duplicate packages (more than one package with the same tracking number) have been found, the packages array contains information about each duplicate. Use this information to determine which of the tracking numbers is the one you need and resend your request using the tracking number and TrackingNumberUniqueIdentifier for that package. - - - - - True if additional packages remain to be retrieved. - - - - - Value that must be passed in a TrackNotification request to retrieve the next set of packages (when MoreDataAvailable = true). - - - - - Information about the notifications that are available for this tracking number. If there are duplicates the ship date and destination address information is returned for determining which TrackingNumberUniqueIdentifier to use on a subsequent request. - - - - - - - FedEx Track Notification request. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - The tracking number to which the notifications will be triggered from. - - - - - Indicates whether to return tracking information for all associated packages. - - - - - When the MoreDataAvailable field is true in a TrackNotificationReply the PagingToken must be sent in the subsequent TrackNotificationRequest to retrieve the next page of data. - - - - - Use this field when your original request informs you that there are duplicates of this tracking number. If you get duplicates you will also receive some information about each of the duplicate tracking numbers to enable you to chose one and resend that number along with the TrackingNumberUniqueId to get notifications for that tracking number. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - Included in the email notification identifying the requester of this notification. - - - - - Included in the email notification identifying the requester of this notification. - - - - - Who to send the email notifications to and for which events. The notificationRecipientType and NotifyOnShipment fields are not used in this request. - - - - - - - The type and value of the package identifier that is to be used to retrieve the tracking information for a package. - - - - - The value to be used to retrieve tracking information for a package. - - - - - The type of the Value to be used to retrieve tracking information for a package (e.g. SHIPPER_REFERENCE, PURCHASE_ORDER, TRACKING_NUMBER_OR_DOORTAG, etc..) . - - - - - - - Used to report the status of a piece of a multiple piece shipment which is no longer traveling with the rest of the packages in the shipment or has not been accounted for. - - - - - An identifier for this type of status. - - - - - A human-readable description of this status. - - - - - - - The descriptive data returned from a FedEx package tracking request. - - - - - This contains the severity type of the most severe Notification in the Notifications array. - - - - - Information about the request/reply such was the transaction successful or not, and any additional information relevant to the request and/or reply. There may be multiple Notifications in a reply. - - - - - Contains the CustomerTransactionDetail that is echoed back to the caller for matching requests and replies and a Localization element for defining the language/translation used in the reply data. - - - - - Contains the version of the reply being used. - - - - - True if duplicate packages (more than one package with the same tracking number) have been found, and only limited data will be provided for each one. - - - - - True if additional packages remain to be retrieved. - - - - - Value that must be passed in a TrackNotification request to retrieve the next set of packages (when MoreDataAvailable = true). - - - - - Contains detailed tracking information for the requested packages(s). - - - - - - - The descriptive data sent by a client to track a FedEx package. - - - - - Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). - - - - - Descriptive data identifying the client submitting the transaction. - - - - - Contains a free form field that is echoed back in the reply to match requests with replies and data that governs the data payload language/translations. - - - - - The version of the request being used. - - - - - The FedEx operating company (transportation) used for this package's delivery. - - - - - Identifies operating transportation company that is the specific to the carrier code. - - - - - The type and value of the package identifier that is to be used to retrieve the tracking information for a package or group of packages. - - - - - Used to distinguish duplicate FedEx tracking numbers. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - To narrow the search to a period in time the ShipDateRangeBegin and ShipDateRangeEnd can be used to help eliminate duplicates. - - - - - For tracking by references information either the account number or destination postal code and country must be provided. - - - - - For tracking by references information either the account number or destination postal code and country must be provided. - - - - - If false the reply will contain summary/profile data including current status. If true the reply contains profile + detailed scan activity for each package. - - - - - When the MoreData field = true in a TrackReply the PagingToken must be sent in the subsequent TrackRequest to retrieve the next page of data. - - - - - - - - - - - - - Used when a cargo shipment is split across vehicles. This is used to give the status of each part of the shipment. - - - - - The number of pieces in this part. - - - - - The date and time this status began. - - - - - A code that identifies this type of status. - - - - - A human-readable description of this status. - - - - - - - Descriptive data that governs data payload language/translations. The TransactionDetail from the request is echoed back to the caller in the corresponding reply. - - - - - Free form text to be echoed back in the reply. Used to match requests and replies. - - - - - Governs data payload language/translations (contrasted with ClientDetail.localization, which governs Notification.localizedMessage language selection). - - - - - - - The descriptive data for the heaviness of an object. - - - - - Identifies the unit of measure associated with a weight value. - - - - - Identifies the weight value of a package/shipment. - - - - - - - Identifies the collection of units of measure that can be associated with a weight value. - - - - - - - - - Used in authentication of the sender's identity. - - - - - Credential used to authenticate a specific software application. This value is provided by FedEx after registration. - - - - - - - Two part authentication string used for the sender's identity - - - - - Identifying part of authentication credential. This value is provided by FedEx after registration - - - - - Secret part of authentication key. This value is provided by FedEx after registration. - - - - - - - Identifies the version/level of a service operation expected by a caller (in each request) and performed by the callee (in each reply). - - - - - Identifies a system or sub-system which performs an operation. - - - - - Identifies the service business level. - - - - - Identifies the service interface level. - - - - - Identifies the service code level. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file