Explore how to integrate our API into your own funnel, integrating deeply with your Native UI
As a RABOT sales partner, the API allows you to build your own custom sales funnel for your Whitelabel tariff, or to integrate the price quote and order process into your own systems and sales processes.
A create:orders scope is required to be able to submit orders and subsequently get their status via the API
A tariffKey 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.
To create a price quote for a lead, in addition to your tariffKey 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
With this information, you can call the offer calculation endpoint.The API endpoint returns a response that details the different pricing components both on a monthly base (EUR/month) and depending on the consumption (ct/kWh), as well as the contract conditions associated with the tariff (e.g. minimum duration, cancellation period).
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.
Partners are responsible for collecting, validating, and securely storing all information required for order submission. Incorrect or incomplete data may cause the order to be blocked during the change process.Submitted order data must be retained in accordance with applicable legal and regulatory requirements.
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 tariffKey to 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 successful, the API returns a customer number and contract number, which uniquely identify the customer and order in the RABOT platform, and can be used in subsequent API calls, e.g. to check the status of the order processing.Before submitting the order via the API, you need to ensure that customers have received all the required contract and pricing information, accepted the terms and conditions (AGB), confirmed the email address and accepted the offer.Once the order is received by the RABOT platform, an order confirmation email will be sent out to the email address provided in the order.
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.
When an order is submitted, a User 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.
Unless otherwise stated, the password field should be submitted with null to enroll the user in the password setting email flow.
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 the offerDate parameter in the create new order call, and the API will automatically use the price that was valid on the given date.
The specific conditions under which you can use the offerDate feature, such as elegible tariffs and maximum offer validity depend on the partnership agreement. If you are unsure about these, please consult your Partner Manager contact to confirm.
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.
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.