With a bulk request, several objects are created, processed or deleted with only one order.
The bulk jobs are accepted by the system, moved to a queue (Bulk Queue) and processed from there by the system. The system response contains a separate "result" block for each contained order.
In the case of large bulk orders, the system responses can become very large and slow down processing. When the default limit of 20 individual orders in a bulk order is reached, only a short system response is returned by the system confirming acceptance of the request. The details of the single orders are then sent by email. You can use the bulk_limit keyword to change the default value of 20 single orders.

Not all tasks allow a bulk request.

Example: bulk request DomainCreate

XML
 <request>
       <auth>
             <user>customer</user>
             <password>password</password>
             <context>4</context>
       </auth>
       <task>
             <code>0101</code>
             <ctid></ctid>
             <default>
                    <ownerc>9925345</ownerc>
                    <adminc>9925345</adminc>
                    <techc>9925345</techc>
                    <zonec>9925345</zonec>
                    <nserver>
                           <name>ns1.example.org</name>
                           <ip>172.16.100.1</ip>
                    </nserver>
                    <nserver>
                           <name></name>
                           <ip></ip>
                    </nserver>
                    <dns_checks>soa</dns_checks>
             </default>
             <domain>
                    <name>example.org</name>
             </domain>
             <domain>
                    <name>example.net</name>
             </domain>
             <domain>
                    <name>example.de.de</name>
                    <ownerc>6574839</ownerc>
                    <!--An owner is used here that differs from the default values.-->
             </domain>
             <reply_to>customer@example.com</reply_to>
       </task>
 </request>