Service offered by data providers who wish to support ordering. A client uses this interface to send user order requests to the provider for fulfillment.

There are three major order operations: submit, cancel, and quote. A provider does not have to support all the operations and can configure which operations are supported using the provider policies on the ECHO API.

Submit: Submit is the minimum operation required to support ordering. After a user assembles an order on the client, the user submits the order to ECHO. ECHO then contacts the provider and submits the order to them.

Quote: Quote is an optional operation that a provider may implement. After a user assembles an order the user may request a quote for the order. ECHO then contacts the provider and requests a quote.

Cancel: Cancel is an optional operation that a provider may implement. After a user assembles an order in the client and has submitted the order, the user may request to cancel it. ECHO then contacts the provider and requests a cancellation.

This version of the API was introduced in ECHO 9 and therefore uses the ECHO 9 namespaces. There have been no changes to this API for ECHO 10 so there is currently no definition of this API in the ECHO 10 namespaces. ECHO 10 will continue to talk to the version 9 definition of this API. However, a new version of this API may be introduced in the future if changes are required.

Known Issues: The Order Fulfillment messages and types schema does not included the attribute elementFormDefault="qualified" which means that only the root element of the message needs to be in a namespace. All of the child elements should not have a namespace even though the schema defines a target namespace. This was an oversight in the original schema definition, however it cannot be changed now without breaking existing clients. This may be corrected in a future release. An example message is presented below. Refer to the XML Schema Part 0: Primer for more information on namespace handling.

An example SOAP response message required now because of the namespace issue:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
       <soapenv:Header/>
       <soapenv:Body>
          <order:SubmitResponse xmlns:order="http://echo.nasa.gov/v9/order/fulfillment">
             <SubmitAcknowledgment>
                <Acceptance>
                   <UpdateMechanism>AUTOMATIC</UpdateMechanism>
                   <ProviderOrderReceipt>
                      <EstimatedShipDate>2008-06-08T18:18:32.850Z</EstimatedShipDate>
                      <Pricing>
                         <TotalPrice>100.0</TotalPrice>
                         <DataPrice>25.0</DataPrice>
                         <MediaPrice>50.0</MediaPrice>
                         <ShippingFee>10.0</ShippingFee>
                         <HandlingFee>15.0</HandlingFee>
                         <Discount>0.0</Discount>
                         <QuantityOfMedia>3</QuantityOfMedia>
                         <AdditionalInformation>No discount is offered right now.</AdditionalInformation>
                      </Pricing>
                   </ProviderOrderReceipt>
                </Acceptance>
                <StatusInformation>Your order has been accepted. We will ship it ASAP.</StatusInformation>
                <ProviderTrackingId>1212517112850</ProviderTrackingId>
             </SubmitAcknowledgment>
          </order:SubmitResponse>
       </soapenv:Body>
    </soapenv:Envelope>
    

An example SOAP response message that may be required in the future when the namespace issue is resolved. This message is not currently considered valid even though the schemas have a target namespace defined:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
       <soapenv:Header/>
       <soapenv:Body>
          <order:SubmitResponse xmlns:order="http://echo.nasa.gov/v9/order/fulfillment" 
                             xmlns:types="http://echo.nasa.gov/v9/order/fulfillment/types">
             <order:SubmitAcknowledgment>
                <types:Acceptance>
                   <types:UpdateMechanism>AUTOMATIC</types:UpdateMechanism>
                   <types:ProviderOrderReceipt>
                      <types:EstimatedShipDate>2008-06-08T18:18:32.850Z</types:EstimatedShipDate>
                      <types:Pricing>
                         <types:TotalPrice>100.0</types:TotalPrice>
                         <types:DataPrice>25.0</types:DataPrice>
                         <types:MediaPrice>50.0</types:MediaPrice>
                         <types:ShippingFee>10.0</types:ShippingFee>
                         <types:HandlingFee>15.0</types:HandlingFee>
                         <types:Discount>0.0</types:Discount>
                         <types:QuantityOfMedia>3</types:QuantityOfMedia>
                         <types:AdditionalInformation>No discount is offered right now.</types:AdditionalInformation>
                      </types:Pricing>
                   </types:ProviderOrderReceipt>
                </types:Acceptance>
                <types:StatusInformation>Your order has been accepted. We will ship it ASAP.</types:StatusInformation>
                <types:ProviderTrackingId>1212517112850</types:ProviderTrackingId>
             </order:SubmitAcknowledgment>
          </order:SubmitResponse>
       </soapenv:Body>
    </soapenv:Envelope>