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 additional information about the address processed by the SHARE systems as a key-value pair. Specifies the key for the address attribute. The value for the key for the address attribute. A reference id provided by the client. Descriptive data to be used in authentication of the sender's identity (and right to use FedEx web services). The client reference id for the validated address. Specifies the degree to SHARE service was able to cannonicalise the address provided, as per USPS standards and match it to an address already in the internal FedEx address repository. Additional attributes about the validated address from FedEx address respository.. 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. 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. 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. Specifies the address classification (business vs. residential) 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..). Specifies how different the address returned is from the address provided. This difference can be because the address is cannonialised to match the address specification standard set by USPS. The postal code specified in a form that is supported by USPS as base, secondary and tertiary. 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). Used in authentication of the sender's identity. This was renamed from cspCredential. 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.