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). 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 (EAS 100) Apartment number not found for this address. (EAS 101) Address requires apartment number. (EAS 102) Address normalized - abbreviations applied. (EAS 103) Dropped data. (EAS 104) Address requires box number. (EAS 200) Match - no changes applied to input address. (EAS 201) Address modified to achieve match. (EAS 202) Match to street range. (EAS 203) Match to box number. (EAS 204) Match to Rural Route (RR) / Highway Contract (HC) address. (EAS 205) Match to city (non-US, non-Canada). (EAS 206) Match to postal code only (non-street) (EAS 207) Need box number for Rural Route / Highway Contract (HC) match. (EAS 208) Formatting performed for country (non-US, non-Canada). (EAS 209) Match to military address (e.g. APO/FPO). (EAS 210) Match to general delivery. (EAS 211) Address exceeded 35 character plug-in limit. (EAS 212) Unable to append non-address; data 35 character limit imposed. (EAS 300) Insufficient data for address verification. (EAS 301) Address (house or box number) not found. (EAS 303) Postal code not found. (EAS 305) Invalid country. (EAS 400) Service unavailable for request address. 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.) 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 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 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 the initial FedEx Web Service release this value should be set to 1. Identifies the service interface level. For the initial FedEx Web Service release this value should be set to 0. Identifies the service code level. For the initial FedEx Web Service release this value should be set to 0. Identifies the set of severity values for a Notification. 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. TBD 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. TBD Name identifiying the type of the data in the element 'Value' The value that was used as the replacement parameter. 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).