Bathroom Planner iFrame Messages

iFrame messages support the communication between the planner and the embedding web site to provide openness and integration. This section describes iFrame messages that are listened by the planner (input) to react to parent window actions or emitted by the planner (output) to enable parent window to react.

 

For...	Inputs Messages	Outputs Messages
Authentication	Authentication TokenRefreshed Login	AuthenticationRequired, AuthenticationSucceeded, AuthenticationFailed, TokenExpired, LoginRequired, LoginSucceeded, LoginFailed
Application	SetUpSettings, DisplayNotification	Ready, CloseApp, ChangeNeedMapping ,AnalyticsAppStep
Open Save	SaveRequested, SnapshotRequested, LoadProject	SaveStarted, SaveSucceeded, ProjectSavingFailed, ProjectSavedRequestForPrint, SnapshotGenerated
Project	InfoRequested, ManualNotesRequested, TemplateInfoRequested	InfoRequestedProject, InfoRequestedUser, ManualNotesRequestedSucceeded, TemplateInfoRequestedSucceeded
Floorplan	MeasureServiceImport	MeasuringServiceButtonClicked
Help Center	HelpCenterRequested, BrokenRulesRequested, HelpCenterToolTipClicked, HelpCenterDesignTipClicked, HelpCenterCabinetComposerToolTipClicked, HelpCenterCabinetComposerDesignTipClicked	BrokenRulesGenerated , NeedHelpClicked, HelpCenterStart, HelpCenterStop
Price	ExternalPriceResponse	ProductListWithBOM, ProductListWithBOMExternal, PriceInfoButtonClicked, PriceInfoButtonClickedExternal, EditorPriceInfoButtonClicked, WorktopPriceInfoButtonClicked, WallPanelPriceInfoButtonClicked, ExternalPriceRequested
Product		SpecialProductInfoRequested, EcoFeeButtonClicked, WorktopTypesInfoRequested
Bill Of Material (BOM)	BOMRequested, LinearExportRequested	BOMComputationReady, ProductListWithBOMRequested, LinearExportGenerated,
Print 2D Plans	Compute2DPlans, CrossCutImagesRequested	PrintButtonClicked, ProjectSavedRequestForPrint, Plans2DStart, Plans2DStop, CrossCutImagesGenerated, CrossCutImagesNotSupported
Summary	DeliveryInfoGenerated, InstallationInfoGenerated	ContactForHelp, ShareProjectBOM, ShareProject, DeliveryInfoRequested, Images2DPlansRequested, InstallationInfoRequested, ServicesInfoRequested

iFrame Communication

To have an overview of the subject, we advise you to read window.postMessage documentation on the web.

➡️ Refer to PostMessage documentation 🔗

Every message received by the application or sent by the application through window.postMessage must be an object of this format:

Key	Type	Description
event	string	The event name is used as unique identifier for a given event.
content	*	Content sent with the event. It is optional and can be anything: integer, array, object...

Template

{
   event:"Login",
   content: 
   {
      token:"dez2fre589e" 
   }
}

Authentication

AuthenticationRequired

Output emitted when the application requests authentication parameters. Upon this request, the parent window must reply with an Authentication message.

Key	Type	Value/Template	Description
event	string	AuthenticationRequired	–
content	–	–	–

Authentication

Input received when authentication is requested by the message AuthenticationRequired, the parent window must reply with the following message.

Key	Type	Value	Description
event	string	Authentication	–
content	object	token distributionID	token: The legal entity token generated by the client website. distributionID: The specific distribution in the legal entity.

Template

{
 "token": string
 "distributionID": string
}

AuthenticationSucceeded

Output emitted by the application to acknowledge that authentication is successful.

Key	Type	Value/Template	Description
event	string	AuthenticationSucceeded	–
content	object	origin appID distributionID distributionParams	origin: The domain from which the message originated. appID: The application ID associated with the provided credentials. distributionID: The distribution ID associated with the provided credentials. distributionParams: The distribution-specific parameters, if any, of the distribution associated with the provided credentials.

Template

{
    "origin": string,
    "appID": string,
    "distributionID": string,
    "distributionParams": object
}

AuthenticationFailed

Output emitted by the application to inform that authentication has failed.

Key	Type	Value/Template	Description
event	string	AuthenticationFailed	–
content	object	httpCode id message	httpCode: The HTTP error code for the request. id: The error id message: The detailed error message.

Template

{
    "httpCode": HttpErrorCode,
    "id": string,
    "message": string
}

TokenExpired

Output emitted and sent to the parent window when a token is expired, subsequent calls to the web-services will fail with a 401 error.

Key	Type	Value/Template	Description
event	string	TokenExpired	–
content	object	null	–

TokenRefreshed

Input received from the parent window. This message is send by the parent window when receiving TokenExpired. This message provides a new valid token to the application to authentify subsequent calls to web services.

Key	Type	Value	Description
event	string	TokenRefreshed	–
content	object	token distributionID	token: The legal entity token generated by the client website. distributionID: The specific distribution in the legal entity.

Template

{
 "token": string,
 "distributionID": string
}

LoginRequired

Output emitted when an action requires a logged user and none is currently logged in the application, this message will be sent.

Key	Type	Value/Template	Description
event	string	LoginRequired	–
content	–	–	–

Login

Input received from the parent window when the user has successfully logged in and the user token is generated.

Key	Type	Value/Template	Description
event	string	Login	–
content	object	token	token: Token generated by client website.

Template

{
    "token": string
}

Note: is not acceptable to use the same userID and token for several users :

• for security and user privacy reasons,
• since the number of projects per user is limited to 1000.

LoginSucceeded

Output emitted when the application succeeded to log in the user (from a token for example), it will send this message.

Key	Type	Value/Template	Description
event	string	LoginSucceeded	–
content	–	–	–

LoginFailed

Output emitted when the application failed to log in the user (from a token for example), it will send this message.

Key	Type	Value/Template	Description
event	string	LoginFailed	–
content	–	–	–

Application

Ready

Output emitted by the planner. The application needs some time to be ready to listen to messages. Listen to this message and ensure that it has been emitted before sending any other iFrame message.

Key	Type	Value/Template	Description
event	string	Ready	–
content	–	–	–

SetUpSettings

Input request to set up a few information for the planner (especially default visual style of the kitchen and template filters).
Here is the list:

iFrame Version

First, you can set the iFrame version you want to use here. This version will drive the data structure that are sent through iFrame messages later in the application(e.g. the BOM, worktop export...). If the iframeVersion key is not given, the planner will use the latest available version.

Kitchen Default Style

You can set up the "style" of the kitchen. First you have to give a styleVersion key that indicates the planner in which version it should read the style from the iFrame message. If styleVersion is not given, it will use version 0 to keep backward compatibility. Below are the supported style versions and their data structure:

styleVersion = 0

In version 0, the kitchen style is a finite list of elements that you can define for styling. All these elements must be given at the root of the iFrame message content. Here is the exhaustive list of supported style parameters (/!\ match the case):
▪ For linears: "worktopID", "plinthID", "wallPanelID", "wallEdgeStripID", "corniceID" and "decostripID".
▪ For non-linears: "handleID", "frontID", "drawerFrontID", "legID", "fillerFrontID", leftCoverPanelID", "rightCoverPanelID", "topCoverPanelID" and "backCoverPanelID".

styleVersion = 1

In version 1, the kitchen style is dynamic for product parameters. You can add five keys at the root of the object: linearStyle, furnitureStyle, floorStyle, wallStyle and name. The first one will contain linear style (the only supported keys are: "worktop", "plinth", "wallPanel", "wallEdgeStrip", "cornice" and "decostrip"). The three next objects will contain any parameter name. For example: "handle", "drawerFront", "glassFront", "corniceOption", etc. The name attribute is an optional information used to identify the need-mapping style name chosen by the user.

Note (for the objects furnitureStyle, floorStyle and wallStyle):
▪ Listed parameters can be of any valid parameter type (boolean, integer, product, etc.), not necessarily product type.
▪ The parameter names are case sensitive.
▪ The value associated with each parameter must be an array of accepted values. The order matters as first values will be applied first if possible.
▪ furnitureStyle will affect every product in the planner, floorStyle will affect every products that touch the floor and wallStyle will affect every products that do not touch the floor.

styleVersion = 2

This version adds the support of the attribute ignoredParameters that can be used to blacklist some parameter names. These parameters will never be added to the global style when planning your kitchen.

Design Flow

You can set up the design flow needs for the user with the optional designFromScratch input. If this boolean is set to "true", the user will be asked if he/she wants to skip auto design step when clicking "next step" in step 1. On the other hand, if designFromScratch is "false", "next step" will go to step 2 in every case from step 1.

Template settings

There is the list of keys related to the template settings:

• templateTags
• nbMaxResultPerGroup
• nbMaxResultPerTemplate
• hasNeedMapping

templateTags is used to set up template filters. It defines groups of required and excluded tags to filter templates that the application will compute. To fit in a group, a template's tags must contain all tags defined in required array and must not contain any tags defined in excluded array. Each group will be computed in the same order as they are defined in the message and solutions are displayed as the same order.

Example of Template Tags:

[{
    required: ["I", "ovenInColumn"],
    excluded: ["integratedFridge"]
}, {
    required: ["L"],
    excluded: []
}]

❗Be careful with the following example: templateTags: { required : []; excluded: [] } with an empty array for "required" and "excluded".
This example means that no tag have been set, so the planner will not filter at all the complete list of active templates. In this case, all the active template files will be loaded in the planner. If 100 templates have been created, 100 templates will be loaded in the planner.
From a performance perspective, it is not recommended because it will impact the response time of displaying the results. We recommend to follow the guidelines (fill templateTags, nbMaxResultPerGroup, nbMaxResultPerTemplate) in this section and sort the templates by configuration in order to avoid the performance impact in the planner.

In the example before, it contains two groups of template tags. The first group defines a template must have the tags I and ovenInColumn and must not have the tag integratedFridge. The second group defines a template must have the tag L. The application will first compute and display solutions for templates which fit in first group then it compute templates for second group.
So if a template has tags ["I", "ovenInColumn", "freeFridge", "traditional"], it fits the first group but not the second group.
And if a template has tags ["L", "ovenInColumn"], it fits the second group but not the first group.

Note:

• An empty array in required means the templates don't need to require any tags. That's to say, all templates with any tags will match.
• An empty array in excluded means the templates don't need to exclude any tags. That's to say, all templates with any tags will match.
• The same tag should not appear both in required and excluded. You can not require a tag and exclude it at the same time.
• The string of template tags in required and excluded array are the free tags defined on the template when range maintainers create the template data. Range maintainers can put any string they want as the free tags. Make sure use the exact same string defined in free tags of template to make it works. See more details about template and template strategy

nbMaxResultPerGroup defines the maximum number of solution displayed for a given group of tags.

nbMaxResultPerTemplate defines the maximum number of solution displayed for a given template.

hasNeedMapping defines whether or not activate the need mapping in the application.

Here is a complete example of template setting. The image below shows the user's choice for the need mapping in the application:

As we can see, the user has the preference for "ovenUnderWorktop" and "freeStandingFridge" and no preference for the layout. So the data sent in iframe message should be like:

templateTags:
  [
    {"required": ["L", "ovenUnderWorktop", "freeStandingFridge"], "excluded": []},
    {"required": ["I", "ovenUnderWorktop", "freeStandingFridge"], "excluded": []},
    {"required": ["II", "ovenUnderWorktop", "freeStandingFridge"], "excluded": []},
    {"required": ["U", "ovenUnderWorktop", "freeStandingFridge"], "excluded": []}
  ],
nbMaxResultPerGroup: 5,
nbMaxResultPerTemplate: 1,

Here we define four groups in templateTags: each group contains "ovenUnderWorktop" and "freeStandingFridge" as required tags and a different layout tags ("L", "I", "II" and "U"). With this setting, template engine will calculate 5 templates per group, sorted following the order of the templateTags (groups) and will calculate 1 solution per template file provided and compliant with tags of the group:

Key	Type	Value/Template	Description
event	string	SetUpSettings	–
content	object	iframeVersion styleVersion params ending with "ID" linearStyle furnitureStyle floorStyle wallStyle name ignoredParameters designFromScratch templateTags nbMaxResultPerGroup nbMaxResultPerTemplate hasNeedMapping	iframeVersion(optional): Positive integer. If not given, defaults to latest supported version in the planner. styleVersion(optional): Positive integer. If not given, defaults to 0. params ending with "ID"(optional): See the above note about kitchen styling. Only taken into account if styleVersion is 0. linearStyle(optional): See the above note about kitchen styling. Only taken into account if styleVersion is 1 or more. furnitureStyle: See the above note about kitchen styling. Only taken into account if styleVersion is 1 or more. floorStyle(optional): See the above note about kitchen styling. Only taken into account if styleVersion is 1 or more. wallStyle(optional): See the above note about kitchen styling. Only taken into account if styleVersion is 1 or more. name(optional): See the above note about kitchen styling. ignoredParameters(optional): See the above note about kitchen styling. Only taken into account if styleVersion is 2 or more. designFromScratch(optional): Boolean telling if the user should be proposed to skip auto design step. templateTags (optional): Array containing objects containing: required: Array of string excluded: Array of string nbMaxResultPerGroup(optional): Positive integer. nbMaxResultPerTemplate(optional): Positive integer. hasNeedMapping (optional): Boolean to activate or not the need mapping into the application.

Template

{
   iframeVersion: integer,
   styleVersion: integer,
   handleID: string,
   baseCabinetFrontID: string,
   wallCabinetFrontID: string,
   drawerFrontID: string,
   fillerFrontID: string,
   plinthID: string,
   legID: string,
   worktopID: string,
   wallPanelID: string,
   wallEdgeStripID: string,
   corniceID: string,
   decostripID: string,
   linearStyle: {
      worktop: string,
      plinth: string,
      …
   },
   furnitureStyle: {
      handle: [string],
      front: [string],
      …
   },
   floorStyle: {
      handle: [string],
      front: [string],
      …
   },
   wallStyle: {
      handle: [string],
      front: [string],
      …
   },
   name: string,
   ignoredParameters: [string],
   designFromScratch: boolean,
   templateTags: [ 
      {
         required: [string],
         excluded: [string]
      }
   ],
  nbMaxResultPerTemplate: integer,
  nbMaxResultPerGroup: integer,
  hasNeedMapping: boolean  
}

Note: This message can be sent at any point while the application is used. Style information received will override any current style and apply itself to current project. Template filters will be modified. If the user is on the auto-design step, template computing will be restarted.

CloseApp

Output emitted when the user clicks on the cross button to close the application.

Key	Type	Value/Template	Description
event	string	CloseApp	–
content	–	–	–

DisplayNotification

Input request used to display a notification in the planner. It can be send at any time during the planner session (i.e. any step). It will display a default-style notification with a close button. The notification will remain on screen until the user clicks the close button, as shown below.

Template

{
    event:"Test_DisplayNotification",
    content:
        {
            "text":"Your project has been approved, action = \"display\"",
            "action":"display"
        }
} 

Also, this message can be used to display the project lifecycle after opening a project (if used along with the project lifecycle API).

Key	Type	Value/Template	Description
event	string	DisplayNotification	Used to request the display of a notification in the planner.
content	object	text type persistent close action	text(Mandatory): Message to display in the notification. type: Type of notification, it could be "default", "success", "error". If not precised, the default value is "default". persistent: If set to true: autoclose is disabled and close button is added. Its default value is true. close: If "content.persistent" is set to true, this string is used as the close button alt text. Its default value is the translation value for key "common.close" action: If a notification with the same action is already in DOM: no new notification will be created. Its default value is "display-notif-iframe".

Template

{
    "text": string,
    "type": string,
    "persistent": boolean,
    "close": string,
    "action": string
}

ChangeNeedMapping

Output emitted when end user clicks the link "My kitchen needs" in the second step of the kitchen design. It allows the integration developer to display a pop in to refine the kitchen preferences used to compute the automatic proposals.

Key	Type	Value/Template	Description
event	string	ChangeNeedMapping	–
content	object	setupParams	object containing infos about the settings used when the project was created. It holds the following keys (See SetUpSetting for more information about their maning): templateTags nbMaxResultPerGroup nbMaxResultPerTemplate styleVersion linearStyle furnitureStyle floorStyle wallStyle name

Template

{
  setupParams: {
    templateTags: [
      {
        required: [string],
        excluded: [string]
      }
    ],
    nbMaxResultPerTemplate: integer,
    nbMaxResultPerGroup: integer,
    styleVersion: integer,
    linearStyle: {
      worktop: string,
      plinth: string,
      …
    },
    furnitureStyle: {
      handle: [string],
      front: [string],
      …
    },
    floorStyle: {
      handle: [string],
      front: [string],
      …
    },
    wallStyle: {
      handle: [string],
      front: [string],
      …
    }
    name: string
  }
}

AnalyticsAppStep

Output emitted by the planner in the each step.
By listening to this event, the integration developer is notified of the current active step of the planner. For example, step1, step2 , step3 or step4. The step provided in the message can be used by the integration developer for further usage.

Key	Type	Value/Template	Description
event	string	AnalyticsAppStep	–
content	object	step	Object containing information about the current active step in the planner

Open Save

SaveRequested

Input request that triggers the save of a project in the application. SaveStarted is then sent back when the save process begins and SaveSucceeded is sent when the save process ends with success.

Key	Type	Value/Template	Description
event	string	SaveRequested	–
content	–	–	–

SaveStarted

Output emitted when the planner is starting the project save.

Key	Type	Value/Template	Description
event	string	SaveStarted	–
content	object	id bom	id: The UUID of the project. bom: Contains the project BOM. Refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

SaveSucceeded

Output emitted when the project is saved in the planner, with additional information about the saved project.

Key	Type	Value/Template	Description
event	string	SaveSucceeded	–
content	object	id name description	id: The UUID of the saved project. name: The name of the saved project. description: The description of the saved project.

ProjectSavingFailed

Output emitted when the project is try to save and failed in the planner, with additional information about the project.

Key	Type	Value/Template	Description
event	string	ProjectSavingFailed	–
content	object	reason	reason: The reason by which saving of the project failed.

Template

{
    id: "UUIDXX-XXX",
    name: "My Kitchen Project",
    description: "Project for my new house"
}

SnapshotRequested

Input request that triggers the generation of a current view snapshot. SnapshotGenerated event will be thrown at the end.

Key	Type	Value/Template	Description
event	string	SnapshotRequested	–
content	–	–	–

SnapshotGenerated

Output emitted when the computation of the snapshot has finished.

Key	Type	Value/Template	Description
event	string	SnapshotGenerated	–
content	object	name image	name: "Snapshot" string. image: Contains a jpeg image of the snapshot as a base-64 encoded string. It can be set directly to an img tag by doing "img.src = image".

Template

{
  "name": string,
  "image": string
 }

LoadProject

For performance reasons, it is recommended if applicable, to start the planner by providing the project ID as an URL parameter. This message should be used only for other scenarios.

Input request for project load in kitchen application.

Key	Type	Value/Template	Description
event	string	LoadProject	–
content	object	id	UUID of the project in the ByMe platform. It can also be an integer.

Template

{
  "id": "4144F45E-B9DA-35C0-90CE-60B9AA5DA418"
}

Project

InfoRequested

Input request for some information from the application. Requested information depends on the content provided.

Key	Type	Value/Template	Description
event	string	InfoRequested	–
content	string	Project User	Project: Requests information about the currect project. User: Requests information about the current user.

InfoRequestedProject

Output emitted after an input message InfoRequested with parameter value Project is sent.

Key	Type	Value/Template	Description
event	string	InfoRequestedProject	–
content	object	projectID projectName projectDesc ProjectDateCreation ProjectDateUpdate	projectID: ID of the project. projectName: Name of the project. projectDesc: Description of the project. ProjectDateCreation: Creation date of the project. ProjectDateUpdate: Update date of the project.

Template

{
    "projectID": number or null
    "projectName": string or undefined
    "projectDesc": string or undefined
    "ProjectDateCreation": string or undefined
    "ProjectDateUpdate": string or undefined
}

Note: If this user is not logged the response will be null.

InfoRequestedUser

Output emitted after an input message InfoRequested with parameter value User is sent.

Key	Type	Value/Template	Description
event	string	InfoRequestedUser	–
content	object	userID	userID: ID of the user.

Template

{
  "userID": number or null
}

ManualNotesRequested

Input request for the manual notes of the current project.

Key	Type	Value/Template	Description
event	string	ManualNotesRequested	–
content	–	–	–

ManualNotesRequestedSucceeded

Output emitted that contains the manual notes of the current project.

Key	Type	Value/Template	Description
event	string	ManualNotesRequestedSucceeded	–
content	string	Notes	Manual notes of the current project.

TemplateInfoRequested

Input request for statistical information about template.

Key	Type	Value/Template	Description
event	string	TemplateInfoRequested	–
content	–	–	–

TemplateInfoRequestedSucceeded

Output emitted after a TemplateInfoRequested is sent.

Key	Type	Value/Template	Description
event	string	TemplateInfoRequestedSucceeded	–
content	object	lastSelectedTemplateUUID nbSolutionPerTemplate	lastSelectedTemplateUUID: Current template uuid selected by the user, can be null if the user did not choose a template nbSolutionPerTemplate as an object. nbSolutionPerTemplate: Each key is a template uuid and the associate value is the number of solution generated by the template in the user project.

Template

{
    "lastSelectedTemplateUUID": string,
    "nbSolutionPerTemplate": {
        "templateUUID": integer
            ....
    }
}

Floorplan

MeasuringServiceButtonClicked

Output emitted on clicking "Use Measure Service" menu item, allowing integration developer to display a pop in to manage the selection of the floorplan to be imported in the planner.

Key	Type	Value/Template	Description
event	string	MeasuringServiceButtonClicked	–
content	–	–	–

Note: For "Use Measure Service" button to be visible, floorPlanImport.planMeasure parameter must be enabled in application distribution.

MeasureServiceImport

Input request for planner to replace the current floorplan by the floorplan described in the JSON provided.

Key	Type	Value/Template	Description
event	string	MeasureServiceImport	–
content	object	JSON	Refer to Floor Layout Format for a complete definition and sample of floor plan description.

See also Configure the Measurement Service.

Note: The planner only listens to this event in the floorplan step. Sending this event at any other step will not have any effect. It is advised to send this event in reaction to MeasuringServiceButtonClicked, as the user is ensured to be in the floorplan step.

Help Center

HelpCenterRequested

Input request for opening the Help Center in Floor Plan step, Design step, Worktop Editor layer and Cabinet Composer layer.

Key	Type	Value/Template	Description
event	string	HelpCenterRequested	–
content	–	–	–

Note: The planner only listens to this event in the steps where a sliding help center is present. That includes the floorplan, design, worktop editor and wall-panel editor steps.

BrokenRulesRequested

Input request for broken business rules list such as recommendation and warnings.

Key	Type	Value/Template	Description
event	string	BrokenRulesRequested	Used to request broken business rules list in the current project.
content	object	stateShown	stateShown: step in which help center is opened, received with [HelpCenterStart]. Optional, Required when broken rule of specific step is requested.

BrokenRulesGenerated

Output emitted after a BrokenRulesRequested, containing the list of broken business rules in the projects, is sent.

Key	Type	Value/Template	Description
event	string	BrokenRulesGenerated	Used to get retrieve all the broken business rules computed in the current project.
content	object	List of broken business rules in the project	JSON object with all the broken business rules categorized with criticality level (i.e. list of rules with criticality level such as "critical", "warning" and "recommendation"). Each broken business rule has following properties in it: title: Business rule title. message: Business rule error message level: Criticality level of the business rule. failureRuleID: Business rule ID. currentValue: Business rule error message current value.

Template

{
    "critical": [{
        title: string,
        message: string,
        level: "critical",
    failureRuleID: number,
    currentValue: string
    }…],

    "warning": [{
        title: string,
        message: string,
        level: "warning",
    failureRuleID: number,
    currentValue: string
    }…],

    "recommendation": [{
        title: string,
        message: string,
        level: "recommendation",
    failureRuleID: number,
    currentValue: string
    }…]
}

NeedHelpClicked

Output emitted when user clicks on "Need more help?" link in help center in floorplan and design step. It can be used by the integration developers to display any kind of help to the consumer. Refer to Need More help.

Key	Type	Value/Template	Description
event	string	NeedHelpClicked	Additional assistance from help center in floorplan and design step.
content	–	–	–

HelpCenterStart

Output emitted when user enters Floor Plan step, Design step and Cabinet Composer layer.

Key	Type	Value/Template	Description
event	string	HelpCenterStart	–
content	object	entryPointEvent stateShown tooltips	entryPointEvent: the entryPoint for the Help center. Globalcheck, CustomWorktop,CustomWallPanel etc. stateShown: state where the user wants to open the help center. tooltips: Contains the details of tooltips displayed.

Template

{
    "entryPointEvent": "GlobalCheck",
    "stateShown": "Floorplan",
    "tooltips": [
        {
            "action": string,
            "message": string
        },
        ...
    ]
}

HelpCenterStop

Output emitted when user leaves Floor Plan step, Design step and Cabinet Composer layer.

Key	Type	Value/Template	Description
event	string	HelpCenterStop	–
content	–	–	–

HelpCenterToolTipClicked

Input receieved when a tooltip is clicked in Help Center in Floor Plan step, Design step.

Key	Type	Value/Template	Description
event	string	HelpCenterToolTipClicked	–
content	object	action	action: tooltip action clicked.

Template

{
    "action":"select_item"
}

HelpCenterDesignTipClicked

Input receieved when a design tip is clicked in Help Center in Floor Plan step, Design step.

Key	Type	Value/Template	Description
event	string	HelpCenterDesignTipClicked	–
content	object	stateShown failureRuleID	stateShown: state in which help center is opened, received with HelpCenterStart. failureRuleID: id of the failed rule received with BrokenRulesGenerated

Template

{
  "failureRuleID":0,
  "stateShown":"DetailedDesign"
}

HelpCenterCabinetComposerToolTipClicked

Input receieved when a tooltip is clicked in Help Center in Cabinet Composer layer.

Key	Type	Value/Template	Description
event	string	HelpCenterCabinetComposerToolTipClicked	–
content	object	action	action: tooltip action clicked.

Template

{
    "action":"select_item"
}

HelpCenterCabinetComposerDesignTipClicked

Input receieved when a design tip is clicked in Help Center in Cabinet Composer layer.

Key	Type	Value/Template	Description
event	string	HelpCenterCabinetComposerDesignTipClicked	–
content	object	stateShown failureRuleID	stateShown: state in which help center is opened, received with HelpCenterStart. failureRuleID: id of the failed rule received with BrokenRulesGenerated

Template

{
  "failureRuleID":0,
  "stateShown":"DetailedDesign"
}

Price

ProductListWithBOM

Output emitted when the end user clicks on the "Item List" button. The Bill Of Material provided in this message has to used by integration developer to build the "Item List" pop in with the proper presentation and grouping of products included in the project.

Key	Type	Value/Template	Description
event	string	ProductListWithBOM	–
content	object	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

ProductListWithBOMExternal

Output emitted when the end user clicks on the "Item List" button if application distribution parameter externalPrice is set to true. It can be used by the integration developers to retrieve the price calculated by the external price engine along with the bom.

Key	Type	Value/Template	Description
event	string	ProductListWithBOMExternal	–
content	object	bom externalPrice	bom: Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version. externalPrice: the external price object returned by the external price engine if application distribution parameter externalPrice is set to true.

PriceInfoButtonClicked

Output emitted when the user clicks on price info icon (i) in the step 2 - pick a layout, step 3 - design your kitchen, and step 4 - summary. It can be used by the integration developers to display a price break down or detailled price information pop in.

Key	Type	Value/Template	Description
event	string	PriceInfoButtonClicked	–
content	–	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

PriceInfoButtonClickedExternal

Output emitted when the user clicks on price info icon (i) in the step 2 - pick a layout, step 3 - design your kitchen, and step 4 - summary if application distribution parameter externalPrice is set to true. It can be used by the integration developers to retrieve the price calculated by the external price engine along with the bom.

Key	Type	Value/Template	Description
event	string	PriceInfoButtonClickedExternal	–
content	–	bom externalPrice	bom: Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version. externalPrice: the external price object returned by the external price engine if application distribution parameter externalPrice is set to true.

EditorPriceInfoButtonClicked

Output emitted when the user clicks on price info icon (i) in the editor. Used in worktop editor, wall panel editor, wall edge strip editor, and cabinet editor. It can be used by the integration developers to display a price break down or detailled price information pop in.

Key	Type	Value/Template	Description
event	string	EditorPriceInfoButtonClicked	–
content	object	bom from externalPrice	bom: Contains Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version. from: Indicates from which editor the price info comes from; The possible values for the from are: "WorktopEditor", "WallPanelEditor", "WallEdgeStripEditor" and "CabinetEditor". For example, if in the cabinet editor, the value of from will be "CabinetEditor". externalPrice(optional): the external price object returned by the external price engine if application distribution parameter externalPrice is set to true.

Template

{
"bom": "BOM",
"from":"CabinetEditor"
}

WorktopPriceInfoButtonClicked

⚠️ DEPRECATED message replaced by EditorPriceInfoButtonClicked.

Output emitted when the user clicks on price info icon (i) in the worktop editor. It can be used by the integration developers to display a price break down pop in.

Key	Type	Value/Template	Description
event	string	WorktopPriceInfoButtonClicked	–
content	–	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

WallPanelPriceInfoButtonClicked

⚠️ DEPRECATED message replaced by EditorPriceInfoButtonClicked.

Output emitted when the user clicks on price info icon (i) in the wallpanel editor. It can be used by the integration developers to display a price break down pop in.

Key	Type	Value/Template	Description
event	string	WallPanelPriceInfoButtonClicked	–
content	–	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

ExternalPriceRequested

It is possible to use an external price engine to compute the kitchen price, and this feature is controlled by the parameter externalPrice in application distribution.

Output emitted by the planner after each BOM computation when using an external price engine.
By listening to this event, the integration developer can implement the business logic of the kitchen price computation based on the BOM. The computed price info has to be sent back to the planner with the message ExternalPriceResponse.

Note: the BOM sent in this message does not always represents the entire user project. When the user uses the worktop editor for example, the price has to be that of the worktops only. Thus the BOM sent in this message only contains worktop items in this example.

Key	Type	Value/Template	Description
event	string	ExternalPriceRequested	–
content	object	bom	bom: Contains Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

ExternalPriceResponse

Input received by the planner after the kitchen price is computed by the client integration (see ExternalPriceRequested).

This message has to contain all the necessary informations for the planner to display the price. It must be a JSON object as described below.

Key	Type	Value/Template	Description
event	string	ExternalPriceResponse	–
content	object	pricable totalPrice	pricable: boolean that tells if the BOM sent via ExternalPriceRequested can be priced. Setting false will result in the planner displaying an error message instead of the price. totalPrice: a JSON object containing the following keys: - regular: regular price (number) - current: current price (number) - discountType: type of discount (string) - startDate: date from which the kitchen price becomes available (string). Must be a valid date string input for the Date.parse() js function. - endDate: date after which the kitchen price is no longer available (string). Must be a valid date string input for the Date.parse() js function. For more information about the totalPrice attribute, see the BOM documentation

Template

{
  "event": "ExternalPriceResponse",
  "content": {
    "pricable": true,
    "totalPrice": {
        "regular": 6500,
        "current": 6250,
        "discountType": "membership",
        "startDate": null,
        "endDate": "2021-12-05T00:00:00.000Z"
    }
  }
}

Product

SpecialProductInfoRequested

Output emitted if the user clicks the information icon (i) of a product. It can be used by the integration developer to display a customized product information pop in.

Key	Type	Value/Template	Description
event	string	SpecialProductInfoRequested	–
content	object	BomProductSelected	BomProductSelected: JSON BOM of the selected product.

Template

{
    "BomProductSelected": jsonBomobject
}

See also Product Information.

EcoFeeButtonClicked

Output emitted in design step, when the user opens the product catalog, an eco-fee link is visible with products having eco-fee pricing option, as shown below.

On clicking "eco-fee" link, an iFrame EcoFeeButtonClicked is sent, allowing kitchen retailer to show the information about eco-fee.The Bill of Material (BOM) of the selected product is included in the message.

Key	Type	Value/Template	Description
event	string	EcoFeeButtonClicked	–
content	object	bomProductSelected	bomProductSelected: JSON BOM of the selected product.

Template

{
    "bomProductSelected": jsonBomobject
}

WorktopTypesInfoRequested

Output emitted if the user clicks on the Edit worktop or Edit wall panel pop-in links ("Learn more about worktop types" or "Learn more about wall panel types") as shown below. Can be used by integration developer to display more information on worktops/wall-panel types.

Note: The event is called WorktopTypesInfoRequested even for the wall-panel pop-in.

Key	Type	Value/Template	Description
event	string	WorktopTypesInfoRequested	–
content	–	–	–

Bill Of Material (BOM)

BOMComputationReady

Output emitted at the first time when the BOM is able to be computed by the planner (e.g. after opening a project).

Key	Type	Value/Template	Description
event	string	BOMComputationReady	–
content	–	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

BOMRequested

Input request for a BOM generation. Listen to ProductListWithBOMRequested message afterwards.

Key	Type	Value/Template	Description
event	string	BOMRequested	–
content	–	–	–

ProductListWithBOMRequested

Output emitted after receiving BOMRequested message. Kitchen planner will send this message (same content as ProductListWithBOM message).

Key	Type	Value/Template	Description
event	string	ProductListWithBOMRequested	–
content	object	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

LinearExportRequested

Input request for manufacturing export information of the desired linears. The linear types exported are controlled by parameters.

Key	Type	Value/Template	Description
event	string	LinearExportRequested	–
content	object	worktop wallPanel wallEdgeStrip	worktop: Compute the worktop export or not. wallPanel: Compute the wall panel export or not. wallEdgeStrip: Compute the wall edge strip export or not.

Note: The planner does not listen to this event in the auto-design step (step 2). If you send it during this step, the planner will not replay anything.

Template

{
 "worktop": true,
 "wallPanel": true,
 "wallEdgeStrip": false
}

LinearExportGenerated

Output response generated after LinearExportRequested is sent.

Key	Type	Value/Template	Description
event	string	LinearExportGenerated	–
content	object	version exportWorktop exportWallpanel exportWallEdgeStrip	version(optional): The iFrame version (Cf. SetUpSettings). exportWorktop(optional): The manufacturing export object corresponding to the worktops in the room. Only present if worktop export was required. exportWallpanel(optional): The manufacturing export object corresponding to the wall panels in the room. Only present if wall panel export was required. exportWallEdgeStrip(optional): The manufacturing export object corresponding to the wall edge strips in the room. Only present if wall edge strip export was required.

Template

{
    "version": 0,
    "exportWorktop": {
        ...
     },
    "exportWallpanel": {
        ... 
    },
    "exportWallEdgeStrip": {
    ...
    }
}

Print 2D Plans

Refer to Print for guidance on how to implement the print command.

PrintButtonClicked

Output emitted if the user clicks "Print" button.

Key	Type	Value/Template	Description
event	string	PrintButtonClicked	–
content	–	–	–

ProjectSavedRequestForPrint

Output emitted when the user clicks the "Print" button and when the project is already saved. By listening to this event, the integration developer can display the print layer.

Key	Type	Value/Template	Description
event	string	ProjectSavedRequestForPrint	–
content	–	–	–

Compute2DPlans

Input request for computation of the 2D plans. The desired 2D plan version can be specified. If the version key is not given, the planner will use the latest available version. Note that the 2D plans version is not same as the iFrame version.

➡️ Refer to 2D Plans Information 🔗 for more details about the parameters

There are two ways to configure the 2D plans:

Global Configuration

This is the easiest way to configure the 2D Plans if all the requested plans have the same configuration

Key	Type	Value/Template	Description
event	string	Compute2DPlans	–
content	object	version topPlans facePlans groundFurnitureTopPlans wallFurnituresTopPlans worktopPlans wallpanelPlans wallEdgeStripPlans showExteriors showFurniture showFurnitureDimension showDepthDimension showWallDimension showFullIslandDimension showNumbering showCutouts showFronts tagsToShow tagsToHide tagsToMeasure roomsOnly saveWithProject resol scale imageWidth imageHeight	version: Positive integer(>=0). topPlans: 0 or 1, compute top plans. (default value: 0) facePlans: 0 or 1, compute face plans. (default value: 0) groundFurnitureTopPlans:0 or 1, compute top plans with furniture on the ground. (default value: 0) wallFurnituresTopPlans: 0 or 1, compute top plans with furniture not touching the ground. (default value: 0) worktopPlans: 0 or 1, compute worktop plans from top. (default value: 0) wallpanelPlans: 0 or 1, compute wallpanel plans by face. (default value: 0) wallEdgeStripPlans: 0 or 1, compute wall edge strip plans from top. (default value: 0) showExteriors: 0 or 1, draws the exteriors. (default value: 1) showFurniture: 0 or 1, draws the furniture. (default value: 1) showFurnitureDimension: 0 or 1, draws the furniture dimensions. (default value: 0) showDepthDimension: 0 or 1, draws the furniture depth dimensions. (default value: 0) showWallDimension : 0 or 1, draws the wall and bay dimensions. (default value: 0) showFullIslandDimension : 0 or 1, draws 2 positioning dimensions on islands instead of just one. (default value: 0) showNumbering: 0 or 1, draws the furniture numbers. (default value: 0) showCutouts: 0 or 1, draws the cutouts in wortops and wallpanels plans (default value: 1). showFronts: 0 or 1, draws the front and handles of the cabinets (default value: 1). tagsToShow: a list of product tags to show in the 2D Plans tagsToHide: a list of product tags to hide in the 2D Plans tagsToMeasure: a list of product tags to measure in the 2D Plans roomsOnly: 0 or 1, draws a Plan for Each Room that contains Cabinets (default value: 1). saveWithProject: 0 or 1, save with current project. (default value: 0) resol: Resolution in PPI. (default value: 300) scale: Scale of the plan when printed at the current resol (20 means 1/20 scale) (default value: 20). imageWidth: Width of the 2D plans in pixels. imageHeight: Height of the 2D plans in pixels.

Example:

{
    version: 1,
    topPlans: 1,
    saveWithProject: 1,
    showExteriors: 1,
    showFurniture: 1,
    showFurnitureDimension: 1,
    showWallDimension: 1,
    showNumbering: 1,
    showFronts: 1,
    roomsOnly: 1,
    resol: 300,
    imageWidth: 2244,
    imageHeight: 1772
}

Multiple Configurations

This allows the generation of different 2D plans configurations. For example, it is possible to generate the same view twice, but with different visible elements on each view

Key	Type	Value/Template	Description
event	string	Compute2DPlans	–
content	object	version saveWithProject configs	version: Positive integer(>=0). saveWithProject: 0 or 1, save with current project. (default value: 0) configs: a list of configuration objects

Possible parameters for a configuration:

Name	Mandatory	Type	Possible Values	Description
typePlan	yes	string	"Top" "Face" "TopGround" "TopWall" "Worktop" "WallPanel" "WallEdgeStrip"	the type of plan to compute
showExteriors	–	num	0 or 1	draws the exteriors. (default value: 1)
showFurniture	–	num	0 or 1	draws the furniture. (default value: 1)
showFurnitureDimension	–	num	0 or 1	draws the furniture dimensions. (default value: 0)
showDepthDimension	–	num	0 or 1	draws the furniture depth dimensions. (default value: 0)
showWallDimension	–	num	0 or 1	draws the wall and bay dimensions. (default value: 0)
showNumbering	–	num	0 or 1	draws the furniture numbers. (default value: 0)
showCutouts	–	num	0 or 1	draws the cutouts in wortops and wallpanels plans (default value: 1)
showFronts	–	num	0 or 1	draws the front and handles of the cabinets (default value: 1)
tagsToShow	–	Array<num>	[...]	a list of product tags to show in the 2D Plans
tagsToHide	–	Array<num>	[...]	a list of product tags to hide in the 2D Plans
tagsToMeasure	–	Array<num>	[...]	a list of product tags to measure in the 2D Plans
roomsOnly	–	num	0 or 1	draws a plan for each room that contains cabinets (default value: 1)
resol	–	num	1 - 1000	Resolution in PPI. (default value: 300)
scale	–	num	0 or 1	Scale of the plan when printed at the current resol (20 means 1/20 scale) (default value: 20)
imageWidth	–	num	0 or 1	Width of the 2D plans in pixels
imageHeight	–	num	0 or 1	Height of the 2D plans in pixels

Example :

{
    version: 1,
    saveWithProject: 1,
    configs: [
        {
            typePlan: "Top",
            showExteriors: 1,
            showFurniture: 1,
            showFurnitureDimension: 1,
            showWallDimension: 1,
            showNumbering: 1,
            showCutouts: 1,
            showFronts: 1,
            roomsOnly: 1,
            resol: 300,
            scale: 20,
            imageWidth: 2244,
            imageHeight: 1772
        },
        ...
    ]
}

Here is the formula giving the distance in pixels, from the scale and resolution parameters:

Npixels = dist/scale * resol/25.4
Npixels: The number of pixels
dist: The distance in mm
scale: The value of the scale parameter
resol: The value of the resolution parameter
Example: For scale = 20 and resol = 300 ⇒ 1000 mm = 590 pixels

Note: If imageWidth and imageHeight is defined, the scale value is ignored in order to fit into an image of these dimensions.

Plans2DStart

Output emitted when the computation of the 2D plans starts.

Key	Type	Value/Template	Description
event	string	Plans2DStart	–
content	–	–	–

Plans2DStop

Output emitted when the computation of the 2D plans is finished.

Key	Type	Value/Template	Description
event	string	Plans2DStop	–
content	object	name unitSystem type image numbers version config	A list of plans 2D. name: Either "TopPlan n" or "FacePlan n" where "n" is a number. unitSystem: "metrics" or "imperial". type: Represents the type of 2D plan. image: Contains a jpeg image of the plan as a base-64 encoded string. (can be set directly to an img by doing "img.src = image"). numbers: A sorted array of integers matching the furniture/board numbers appearing in the 2D plan. version: Specifies the version of the 2D plans data structure. To get the 2D plans at a specific version, see Inputs/2DPlans. config: the config used to generate the 2D Plan

Template

[
  {
    "name": string
    "unitSystem": string
    "type": string
    "image": string
    "numbers": array
    "version": number
    "config": 
    {
      typePlan: "Top",
      showExteriors: 1,
      showFurniture: 1,
      showFurnitureDimension: 1,
      showWallDimension: 1,
      showNumbering: 1,
      showCutouts: 1,
      showFronts: 1,
      roomsOnly: 1,
      resol: 300,
      scale: 20,
      imageWidth: 2244,
      imageHeight: 1772
    }
  },
  ...
]

CrossCutImagesRequested

Input request for the crosscut (section) images of all the pieces of furniture of the current project.

You must specify a width and a maximum height that will apply for all rendered images (see notes below).

You can specify the version you want to use here. If the version key is not given, the planner will use the latest available version. Note that the crosscut images version is not same as the iFrame version.

Key	Type	Value/Template	Description
event	string	CrossCutImagesRequested	–
content	object	version saveWithProject imagesWidth imagesMaxHeight enableSameScale enableGraduations lineWidth textSize	version: A positive integer (>= 0). saveWithProject: True to save the atlas with the project. False by default. imagesWidth(MANDATORY): The width in pixels of the rendered images. imagesMaxHeight(MANDATORY): The maximum height of the rendered images. enableSameScale: True if all furnitures in cross cut images have the same scale. False if they occupy the more space they can in the image. enableGraduations: True to display graduations scale. lineWidth: Define the line width of furniture and linear. Expressed in pixels. textSize: Define the text size of the text expressing the graduations scale. Expressed in pixels.

Template

{
     "version": integer,
     "saveWithProject": boolean,
     "imagesWidth": integer,
     "imagesMaxHeight": integer,
     "enableSameScale": boolean,
     "enableGraduations": boolean,
     "lineWidth": integer,
     "textSize": integer    
}

Note:
▪ The height of the rendered images will depend on the width/height ratio of each cabinet.
▪ If the height is higher than imagesMaxHeight, it will be fixed to imagesMaxHeight and white areas will be added left and right of the image to preserve ratio.
▪ In every case, the width of each rendered image will be equal to imagesWidth.
▪ To add graduations next to a furniture, the furniture must contains an assembly component tagged as ‘Box' with the closed tag: ByMeAPI.ClosedTags.Boxes.

Note: The planner only listens to this event in the following steps :
▪ Floorplan step
▪ Design step
▪ Summary step
If sent in any other step, the planner will replay with a CrossCutImagesNotSupported message.

CrossCutImagesGenerated

Output response generated after CrossCutImagesRequested is sent.

The generated cross-cut images are placed in a big image (an atlas).
A mapping table allows linking a specific image with its position in the atlas.

Version: 1

Key	Type	Value/Template	Description
event	string	CrossCutImagesGenerated	–
content	object	version atlasImage mapping front & cross nomenclatureNumber xOffset yOffset width height	version: Specifies the version of the crosscut images data structure. To get crosscut images at a specific version, see Inputs/CrossCutImagesRequested. atlasImage: Base64 URL of the atlas image. mapping: JSON object that contains the location of each image in the atlas. The keys of this object are the nomenclature numbers of the cabinets (this eases the retrival of 1 specific cabinet's images). front & cross: Each cabinet has 2 images: The front view and the cross-cut view. For each image: nomenclatureNumber: The unique number that identifies the piece of furniture. It is the same number as the one in the BOM or in the 2D plans. xOffset: The X position of the image in the atlas (origin is top left). yOffset: The Y position of the image in the atlas (origin is top left). width: The width in pixels of the image. height: The height in pixels of the image.

Template

{
    "version": 1,
    "atlasImage": string,
    "mapping": {
        1: {
            "front": { 
                "nomenclatureNumber": integer
                "xOffset": integer
                "yOffset": integer
                "width": integer
                "height": integer
            },
            "cross": { 
                "nomenclatureNumber": integer
                "xOffset": integer
                "yOffset": integer
                "width": integer
                "height": integer
            }
        },
        ...
    }
}

Note:
▪ For versions>=1, if the atlas is saved as a project media (see CrossCutImagesRequested), the "mapping" object is stored in the metadata of the image.
▪ For Filler Piece, only the Front view will be generated. To be considered as a Filler Piece, the catalog element must have the one of the following "close-tag": "Filler strip" - "Filler strip angle" - "Free standing filler strip".
▪ For freestanding appliance, no images (neither Front view nor Cross Cut View) will be generated. To be considered as a freestanding appliance, the catalog element must have the following option: "layout = "freeStanding".

Version: 0 deprecated

Key	Type	Value/Template	Description
event	string	CrossCutImagesGenerated	–
content	object	version frontImages crossCutImages Image nomenclatureNumber width height	version: Specifies the version of the crosscut images data structure. To get crosscut images at a specific version, see Inputs/CrossCutImagesRequested. frontImages: JSON object that contains all information about front images. The keys of this object are the nomenclature numbers of the cabinets (this eases the retrival of 1 specific cabinet's images). crossCutImages: JSON object that contains all information about cross-cut images. The keys of this object are the nomenclature numbers of the cabinets (this eases the retrival of 1 specific cabinet's images). For each image: Image: Base64 URL of the image. nomenclatureNumber: The unique number that identifies the piece of furniture. It is the same number as the one in the BOM or in the 2D plans. width: The width in pixels of the image. height: The height in pixels of the image.

Template

{
    "version": 0,
    "frontImages": {
        1: {
            "image": string,
            "nomenclatureNumber": integer
            "width": integer
            "height": integer
        },
        ...
    },
    "crossCutImages": {
        1: {
            "image": string,
            "nomenclatureNumber": integer
            "width": integer
            "height": integer
        },
        ...
    },

}

CrossCutImagesNotSupported

Output response generated when the request CrossCutImagesRequested has been sent in a forbidden state. The only states that will allow to generate the cross cut image response are: "Floor plan", "DesignYourRoom" and "Summary".

Summary

ContactForHelp

Deprecated. The button is removed. The integration developer can provide this capabilities in "Proceed" flow or in help center. See ShareProjectBOM or NeedHelpClicked.

Output emitted when the user clicks "Contact a co-worker" button in the summary step. By listening to this event, the integration developer can display a pop in and implement the business logic of the kitchen retailer for contacting a co-worker.

Key	Type	Value/Template	Description
event	string	ContactForHelp	–
content	object	token drawingID	Token: Token of the user to know who ask help. drawingID: ID of the current project.

Template

{
  "token": string,
  "drawingID": number
} 

ShareProjectBOM

Output emitted when the user clicks "Proceed" button in Summary step. By listening to this event, the integration developer can implement the next steps of the consumer journey with the kitchen retailer. It can be purchase of the kitchen or an appointment with a co-worker in store.

Key	Type	Value/Template	Description
event	string	ShareProjectBOM	–
content	string	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

ShareProject

Output emitted when the user clicks "Share" button. By listening to this event, the integration developer can display a pop in and implement the business logic of the kitchen retailer for sharing options.

Key	Type	Value/Template	Description
event	string	ShareProject	–
content	object	projectID image	projectID: ID of the project. image: Project snapshot or HQ rendering image encoded in base64.

Template

{
  projectID: "DE211A64-1AF0-4231-86EF-C49E0C4447F5",
  image: "data:image/jpeg;base64,SxDeddd..."
} 

Note: For "Share" button to be visible, sharing parameter must be enabled in application distribution.
Also, before the iFrame message, a log-in + save action will be asked if user not logged in and/or project not saved.

See also Share project.

DeliveryInfoRequested

The display of delivery date in step 4 - Summary and the corresponding iFrame messages mechanism is controlled by the parameter delivery in application distribution.

Output emitted by the planner in the step 4 - Summary.
By listening to this event, the integration developer can implement the business logic of the kitchen retailer for computing the delivery date and price. The BOM provided in the message can be used to check on another system if all products are available. The computed delivery date and delivery price(optional) have to be sent back to the planner with the message DeliveryInfoGenerated.

Key	Type	Value/Template	Description
event	string	DeliveryInfoRequested	–
content	string	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

DeliveryInfoGenerated

Input received by the planner when user enters step 4 - Summary, when it receives the message DeliveryInfoRequested. The content of this message is computed by integration website, and it displays delivery date and price in the planner.

Key	Type	Value/Template	Description
event	string	DeliveryInfoGenerated	–
content	string	"Thu 16th Jul"	Delivery date to be displayed to the customer .
content	string	"€ 99"	Delivery price to be displayed to the customer. It is optional to display deliver price.

Note: The planner only listens to this event in the finalize step. Sending this event at any other step will not have any effect.

InstallationInfoRequested

The display of Installtion Service in step 4 - Summary and the corresponding iFrame messages mechanism is controlled by the parameter installation in application distribution.

Output emitted by the planner in the step 4 - Summary.
By listening to this event, the integration developer can implement the business logic of the kitchen retailer for computing the installation date. The BOM provided in the message can be used to check on another system if all products are available. The computed installation date and price(optional) has to be sent back to the planner with the message InstallationInfoGenerated.

Key	Type	Value/Template	Description
event	string	InstallationInfoRequested	–
content	string	BOM	Product List, refer to Bill of Material Reference for a complete description of BOM in JSON format. See also SetUpSettings to set the BOM version.

InstallationInfoGenerated

Input received by the planner when user enters step 4 - Summary, when it receives the message InstallationInfoRequested, the planner displays this content as installation date and price.

Key	Type	Value/Template	Description
event	string	InstallationInfoGenerated	–
content	string	"Thu 16th Jul"	Installation date to be displayed to the customer.
content	string	"€ 2120"	Installation price to be displayed to the customer. It is optional to display installation price.

Note: The planner only listens to this event in the finalize step. Sending this event at any other step will not have any effect.

ServicesInfoRequested

The display of the Service module in step 4 - Summary and the corresponding iFrame messages mechanism is controlled by the parameter servicesInfo in application distribution.

Output emitted by the planner in step 4 - Summary.
By listening to this event, the integration developer can implement the business logic of the kitchen retailers to add custom information. This will be most commonly used for services but could be for any other reason (book an appointment, book home measure, request brochure, find a local store, etc)

Key	Type	Value/Template	Description
event	string	ServicesInfoRequested	–
content	–	–	–

Images2DPlansRequested

Output emitted when the user clicks on "View all" button in Summary step, which allows the integration developers to display the project's medias layer.

Key	Type	Value/Template	Description
event	string	Images2DPlansRequested	–
content	object	plan2DAvailable plans2D images	plan2DAvailable: Boolean, indicates whether the generation of 2D plans is available or not (It should be the same value as 2dplans defined in application distribution) plans2D: an array of generated 2D plans. Each item in plans2D contains following properties: name: the name of the 2D plan url: Base64 url of the image images: an array of project medias. Each item in images contains following properties: id: the id of the project media creationDate: the creation date of the project media url: the url of the project media name: the name of the project media metadata: the metadata of the project media typeMediaID: the type of project media (possible values are: "HQRendering" and "Rendering360")

Template

{
  "event": "Images2DPlansRequested",
  "content": {
    "plan2DAvailable": true,
    "plans2D": [
        {
          "name": "TopPlan 1",
          "url": "data:image/jpeg;base64,SxDeddd..."
        },
    ],
    "images": [
      {
        "id": 75327,
        "creationDate": "2020-08-08T12:43:04.000Z",
        "url": "https://...",
        "name": null,
        "typeMediaID": "HQRendering",
        "metadata": {
          "media": "",
          "quality": "High"
        }
      },
    ]
  }
}