A
create:orders scope is required to be able to submit orders and subsequently get their status via the APIQuery Available Tariffs
AtariffKey is a required parameter of the calculate offer price and create order calls. Send the get tariffs call to retrieve the list of available tariffs for your application.
example response body
Create a price quote
To create a price quote for a lead, in addition to yourtariffKey parameter, you need to provide the following required information in the Request Body to calculate the price quote:
- postcode of the delivery address - this will determine the applicable grid fees and other fees
- estimated yearly energy consumption - this will be used to calculate the estimated monthly cost
example response
Submit the order (contract draft)
When a lead has accepted the offer, you can use the API to submit the customer and order details to the RABOT platform with a create new order call. The following information is mandatory for the creation of an order (contract draft) in RABOT’s system (see Orders API reference for detailed call body breakdown):- a
tariffKeyto identify the requested product - customer identification and contact details.
- delivery address and meter identification details
- previous supplier BDEW code, desired change date and expected yearly consumption
- bank details (for SEPA mandate)
Depending on whether the order is a customer who is changing supplier or moving into a new home, different information is required for successful order processing.See the New Delivery Location Case for more detailed field requirements.See the Change of Supplier for more detailed field requirements.
If the customer email address submitted with the order does not exist in the RABOT platform yet, a new user account is automatically created. Please submit your order without ‘password’ set to ‘null’.The user account will be enrolled in a “set password” flow to create their password.
If you are a Whitelabel partner, the order confirmation and all other communications are branded based on the CI guidelines provided during initial kick-off.
example request body
example response body
Password Setting
When an order is submitted, aUser Account is created using the Email address provided in the call. Depending on your partnership agreement, the capability to set the password of the User Account is restricted to optimize the user experience.
Offer date (Ensuring correct energy tariff costs)
By default, when you submit a new order, the RABOT platform applies the prices and conditions that are applicable at the time of the API call. For fix price tariffs, this can be a problem, as prices might have changed significantly between the time that you requested the price quote from the API and presented it to customers, and the time you submit the order. In this case, customers could get an order confirmation showing different prices than what they ordered. To prevent this, include theofferDate parameter in the create new order call, and the API will automatically use the price that was valid on the given date.
Contract draft creation and the “Change process”
As you may have noticed, the term contract draft is almost inter-changeable with the term order. This is due to the submitted order transitioning to a contract draft in the RABOT platform once received. The details in the contract draft are subsequently used in the market communication during the change process. Additionally, these details are used to populate dynamic fields within RABOT’s email and transactional document communication. Below we will go into more detail about querying the order status. For a more detailed breakdown of the change process and the various statuses an order can have as well as action taken to resolve delays, please refer to our Change Process Detailed guide.The Change Process is particularly important for Whitelabel partners, however for RABOT Affilliate partners that have a commission compensation model for their sales staff, this is a relevant topic due to its impact on payout amounts and dates.
Check order status
After the order has been submitted successfully, you can use the get orders endpoint to follow the different processing states of the order. You can include the ‘filter.fromUpdatedAt’ (Format: YYYY-MM-DD) as a parameter to retrieve orders that have experienced a status update via market communication during the change process from the date you submit.example response body