Skip to main content

Datadis

User Registration Process for DATADIS Partners​

This article explains the user registration process in the DATADIS platform for partners, allowing external users to register through a link in external applications or from the DATADIS private area.

To become a DATADIS partner, a formal agreement must be signed between the company and DATADIS. These are the main sections of the registration process:

Main Sections of the Registration Process​

1. Registration via External Call​

External applications can call a registration service that redirects users to a DATADIS registration page. There are three registration methods, depending on the type of document:

  • Digital Certificate: For users with DNI/NIE.
  • DNI/NIE + CUPS: Requires an image of the document and a valid CUPS code.
  • CIF + CUPS: Exclusive for CIF, requiring the associated CUPS.

The document is validated before the user is registered. Both GET and POST requests are supported, and success and error codes are provided to guide the process.

2. Registration Confirmation​

Allows verification of whether a user is already registered via a query. This option, executable after registration, prevents duplication and system overload.

3. Console Monitoring for Registration Status​

DATADIS provides status annotations in the browser console, allowing external applications to monitor the registration progress.

  • NOT_UPLOADED : Integration created, but user not yet uploaded to Datadis.
  • NOT_HOLDER : No supply points found in Datadis after 7 days.
  • WAITING_SUPPLIES : Datadis has supplies, but they don’t match the house in Clevergy.
  • CONNECTED : Supply point found and linked successfully.
  • DISCONNECTED : Datadis stops sending data from a previously connected house.

4. Registration in the Private Area:​

A partner can register users in the private area after performing the necessary validations. The flows are:

  • DNI/NIE + CUPS: For individuals, requiring the document and CUPS.
  • CIF + CUPS: For organizations, requiring entity information and CUPS.

5. Integration with External Applications:​

The document includes an HTML code example to execute registration calls and check the user status.