<?xml version="1.0" encoding="utf-8"?>
<response>
<registrationkey>
<keydata>Remotely generated key #1</keydata>
<keydata>Remotely generated key #2</keydata>
<keydata>Remotely generated key #3</keydata>
</registrationkey>
</response>

Note: number of keydata fields should coincide with the actual number of registration keys being sent. Our system expects to receive the number of keys as specified in the keycount tag of the request xml.

When sending multiple key parts for a single order, a label should be used in the keydata tag. The example below is for sending a 2-part key, quantity purchased 2:

<?xml version="1.0" encoding="utf-8"?>
<response>
<registrationkey>
            <keydata keynumber="1" keypart="1">Registration key 1, part 1</keydata>
            <keydata keynumber="1" keypart="2">Registration key 1, part 2</keydata>
            <keydata keynumber="2" keypart="1">Registration key 2, part 1</keydata>
            <keydata keynumber="2" keypart="2">Registration key 2, part 2</keydata>
</registrationkey>
</response>

Note: If "Use one key" is checked under the product fulfillment section in the Add/Edit Products interface, only 1 key is expected to be returned from your key generator. If "Use one key" is checked the value of the keycount tag in the request XML will be one.

If there is an error, you can send an error message and code, like this:

<?xml version="1.0" encoding="utf-8"?>
<response>
<registrationkey>
<errorcode>2</errorcode>
<errormessage>There is a problem with the email address
you provided. It must match the email address provided when the
quotation was requested.</errormessage>
</registrationkey>
</response>

This will queue the order and display an error message in the System Error Report.