Profiles

Site profiles contain information about their housing, lifestyle and equipment. This data enables access to personalized features, such as Similar home comparison or Usage breakdown.

Details on the expected information to be sent

General profile data

Here is a subset of profile information that has the most impact on the accuracy of our features.

Information	Description
`Site identifier`	IDs associated with the site generated at the end of the subscription process
`Source`	Profile origin (submitted by the provider or updated by the site)
`Application date`	Profile effective start date
`Generation date`	Generation date of the profile
`Housing type`	Type of housing (apartment, house, other)
`Housing area`	Surface of the housing in square meter
`Principal heating system type`	Energy used for main heating
`Sanitary hot water type`	Energy used for domestic hot water
`Residence type`	Type of residence (principal, secondary)
`Construction date`	Year of building construction
`Number of occupants`	Number of occupants between 1 and 14

Extended profile data

To go further, profiles are customizable. Datanumia handle over 70 profile attributes: depending on your preferences, we can configure the profile to include the following information:

Housing: secondary heating, pool, etc.
Lifestyle: room temperature, weekend absences, shutters, etc.
Housing equipment: cooking appliances, audiovisual equipment, lighting, air conditioning, etc.
Electric vehicle: make, model, number of kilometers traveled, etc.

Profiles collection process

The profile initialization for a site should occur after the site subscription. This data may change throughout the site lifecycle, so it can also be modified after initialization in order to provide accurate services. Depending on the processing volumes and the operating mode of our clients, two types of collection processes to add or modify profiles are offered via API: mass collection and unitary collection.

Mass collection

This method enables bulk collection of profiles of multiple sites. Once an archive has been sent, it is possible to track its processing through a dedicated service. The bulk method includes three endpoints :

POST profiles import: allows you to submit a profiles archive for processing
GET profiles import: returns a list of jobs between two dates, with their statuses and an overview of the OK/KO operations
GET profiles import (job-id): allows you to monitor the processing of an archive through its statuses and the detailed report containing the OK/KO operations

Specific behavior

All valid data is integrated. Invalid data does not cause blocking issues
This method allows you to initialize or edit a large volumetry of profiles, but the data submitted for a site via this method will override and replace its existing profile data.

Example of a JSON file

{
  "profiles": [
    {
      "siteId": "site-3000",
      "source": "SCORE",
      "beginTs": "2021-07-21T22:00:00Z",
      "generationTs": "2022-05-17T14:28:37Z",
      "housingType": "Appartement",
      "surfaceInSqMeter": 89.5,
      "principalHeatingSystemType": "Electricite",
      "sanitaryHotWaterType": "Electricite",
      "residenceType": "Principale",
      "constructionDate": 2004,
      "noOfOccupants": 4
    }
  ]
}

Introduction

Offer catalog

Manage your users

Home Basic

Home Coaching

Home Energy Management

Home Interfaces

Details on the expected information to be sent

General profile data

Extended profile data

Profiles collection process

Mass collection

Specific behavior

Example of a JSON file

Introduction

Offer catalog

Manage your users

Home Basic

Home Coaching

Home Energy Management

Home Interfaces

​Details on the expected information to be sent

​General profile data

​Extended profile data

​Profiles collection process

​Mass collection

​Specific behavior

​Example of a JSON file

Details on the expected information to be sent

General profile data

Extended profile data

Profiles collection process

Mass collection

Specific behavior

Example of a JSON file