Leaf Provider Connection Link

Overview

Leaf's Provider Connection Link is a widget that you can install with minimal setup and a few lines of code. This widget enables your customers to connect their existing provider accounts, which associates it with their Leaf User.

Get started

1. Sign in with a Leaf account

You will need a Leaf account. If you don't have one yet, you can create one by contacting Leaf support.

2. Get to know the Leaf user entity

All control of connected providers is done at the Leaf user level (usually it represents the user of your application), so it's important to know more about it here.

3. Create the user application tokens

Since the connection is at Leaf user level, the widget uses a different authentication method. We will required to create an API key for each Leaf user. This will ensure that the Leaf user only accesses its own resources.

The endpoints to manage those application tokens are here.

Set up

To use the widget you will need to enable the providers. Don't worry, you only need to set it up once.

John Deere

To enable John Deere as a provider in the widget you need your application already registed with John Deere. You can find more info on how to create a developer account here.

Redirect URI

The first step is to add our widget URL in the "Redirect URI" section:

https://widget.withleaf.io

In the My applications page, select your application and edit it to add the URL here

Application info

To allow the users to authenticate with John Deere, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/JohnDeere/{appName}/{clientEnvironment}

For John Deere, it is necessary to inform the:

• clientKey (Application Id)
• clientSecret (Secret)

You can set the appName and the clientEnvironmentas the environment your application is enabled on John Deere: STAGE or PRODUCTION.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "clientKey": "string", "clientSecret": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/JohnDeere/LeafWidget/PRODUCTION'

Climate FieldView

To enable Climate FieldView as a provider in the widget you need your application credentials from Climate. You can find more info on how to create a developer account here.

Application info

To allow the users to authenticate with Climate FieldView, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/ClimateFieldView/{appName}

For Climate FieldView, it is necessary to inform the:

• apiKey
• clientId
• clientSecret

You can set the appName.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "apiKey": "string", "clientId": "string", "clientSecret": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/ClimateFieldView/LeafWidget'

CNHi

To enable CNHi as a provider in the widget you need your application credentials from CNHi. You can find more info on how to create a developer account here.

OAuth Callback URL

The first step is to add our widget URL in the "App OAuth Callback URL(s)" section:

https://widget.withleaf.io

In the Developer Dashboard page, select your application and edit it to add the URL here

Application info

To allow the users to authenticate with CNHi, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/CNHI/{appName}/{clientEnvironment}

For CNHi, it is necessary to inform the:

• clientId (Client Id)
• clientSecret (Client Secret)
• subscriptionKey (Primary SubscriptionKey)

You can set the appName and the clientEnvironment as the environment your application is enabled on CNHi: STAGE or PRODUCTION.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "clientId": "string", "clientSecret": "string", "subscriptionKey": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/CNHI/LeafWidget/PRODUCTION'

AgLeader

To enable AgLeader as a provider in the widget you need your application credentials from AgLeader. You can find more info on how to create a developer account here.

Redirection URL

The first step is to add our widget URL in the "Redirection URL" property:

https://widget.withleaf.io

In the Consumer Keys page, select your application and click in the "Edit Consumer Key Profile" option to edit it add the URL here

Application info

To allow the users to authenticate with AgLeader, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/AgLeader/{appName}

For AgLeader, it is necessary to inform the:

• privateKey
• publicKey

You can set the appName.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "privateKey": "string", "publicKey": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/AgLeader/LeafWidget'

Trimble

To enable Trimble as a provider in the widget you need your application credentials from Trimble. You can find more info on how to create a developer account here.

Authentication Callback URL

The first step is make sure our widget URL is registered in the "Authentication Callback URLs" section. It may be necessary to contact Trimble to request the change.

https://widget.withleaf.io

Application info

To allow the users to authenticate with Trimble, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/Trimble/{appName}

For Trimble, it is necessary to inform the:

• applicationName
• clientId
• clientSecret

You can set the appName.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "applicationName": "string", "clientId": "string", "clientSecret": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/Trimble/LeafWidget'

Raven Slingshot

To enable Raven Slingshot as a provider in the widget you need your apiKey and sharedSecret from Raven. You can find more info on creating a developer account here.

Application info

To allow the users to authenticate with Raven Slingshot, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/RavenSlingshot/{appName}

For Slingshot, it is necessary to inform the:

• apiKey
• sharedSecret

You can set the appName.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "apiKey": "string", "sharedSecret": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/RavenSlingshot/LeafWidget'

tip

Remember your user will still need to provide the Access Key during the authentication process.

Stara

To enable Stara as a provider in the widget you need your developer user and pwd from Stara. You can find more info on creating a developer account here.

info

Stara is not yet available in Link Angular

Application info

To allow the users to authenticate with Stara, you will need to send your application info to this endpoint  POST /usermanagement/api/app-keys/Stara/{appName}

For Stara, it is necessary to inform the:

• user
• pwd

You can set the appName.

Here is a request example:

• cURL
• Python
• JavaScript

curl -X POST \

-H 'Authorization: Bearer YOUR_TOKEN' \

-d '{ "user": "string", "pwd": "string" }'

'https://api.withleaf.io/services/usermanagement/api/app-keys/Stara/LeafWidget'

Tutorial

Angular

tip

Here you can run a live use case demo! It will only be necessary to replace your information in the .html component.

To add this Leaf widget in an Angular application, you can use the @withleaf/leaf-link-angular library, which is a JavaScript library that provides all Leaf UI Widgets. Here are the general steps to get started:

1. Install the @withleaf/leaf-link-angular package using npm:

npm i @withleaf/leaf-link-angular

2. Import the library in your component or module file:

import { ProvidersModule } from '@withleaf/leaf-link-angular';

3. Add the component to the HTML. Make sure you already created the Leaf user API key (apiKey); you need to specify both the Leaf User API Key and the Leaf User ID (leafUser) in the required properties in the HTML component. Check all the properties available on the reference here.

<div class="content" role="main">

<providers

apiKey="Your_API_Key"

leafUser="Your_Leaf_User"

title="Your_Title"

companyName="Your_Company_Name"

companyLogo="Your_Company_Logo"

></providers>

</div>

React

tip

Here you can run a live use case demo! It will only be necessary to replace your information in the App.tsx file.

To add this Leaf widget in a React application, you can use the @withleaf/leaf-link-react library, which is a JavaScript library that provides all Leaf UI Widgets. Here are the general steps to get started:

1. Install the @withleaf/leaf-link-react package using npm:

npm i @withleaf/leaf-link-react

2. Import the component in your *.tsx file:

import { Providers } from '@withleaf/leaf-link-react';

3. Add the component to the *.tsx file. Make sure you already created the Leaf user API key (apiKey); you need to specify both the Leaf User API Key and the Leaf User ID (leafUser) in the required properties in the tsx component. Check all the properties available on the reference here.

function App() {

return (

<Providers

isDarkMode={true/false}

companyName={companyName}

companyLogo={companyLogoUrl}

leafUser={leafUserId}

apiKey={apiKey}

/>

);

}

Reference

Property Overview

Name	Type	Summary
apiKey	String	The authentication API Key
companyLogoUrl	String	Customization: a link to the company logo
companyName	String	Customization: the name of the company
isDarkMode	Boolean	Enable/disable the dark mode
leafUser	String	The Leaf User ID
locale	String	Forces the widget language
title	String	The title of the widget
showSearchbar	String	Show/hide the search bar
title	String	The title of the widget

Property Details

apiKey

The apiKey is the authentication key that will allow the use of the widget. It can be created and managed here.

companyLogoUrl

The URL to the company logo. It will be displayed in the landing screen. It can be a PNG, JPEG or SVG.

companyName

The company name. It will be displayed in the landing screen and in each reference about the customer.

isDarkMode

Toggles dark mode on and off. The default value is false.

leafUser

The Leaf User ID. Check this page for more info about the Leaf User.

locale

By default, the widget sets the language based on the user's browser configuration, but to force a language, use this property with one of the possible values: en_US, pt_BR, es_ES, or fr_FR.

showSearchbar

Shows/hides the search bar for providers available for integration. The default is true, so the search bar will be displayed.

title

The title displayed in the widget. The default is "Select your integration".
Customized texts will not be automatically translated.

Hooks Overview

Leaf Link also have hooks that can improve the developer experience when using the widgets.

Name	Type	Description
providersConnected	Array<{ provider: string; createdTime: string }>	Provide the array of the provider connected and also the createdTime - available after finish the connection process
providerWidgetStatus	{ code: number; message: string }	Provide the status code and the message from the current widget Status

Hooks Details

providersConnected

Provides the array of the providers connected with the createdTime. It will be available after finish the connection process.

providerWidgetStatus

Provides the status code and the message from the current widget status:

Status Codes

Code	Message
-1	Error
0	Started
1	Done

How to use it

Angular

Use the getWidgetStatus property to reference a function in your component.

<div>

<providers

[apiKey]="apiKey"

[leafUser]="leafUser"

[companyName]="companyName"

[companyLogo]="companyLogo"

(getWidgetStatus)="yourFunctionNameHere($event)">

</providers>

</div>

From the component, you can get the status and the providers connected in the referenced function.

import { Component } from '@angular/core';

@Component({

selector: 'app-root',

templateUrl: './app.component.html',

styleUrls: ['./app.component.css']

})

export class AppComponent {

apiKey: string = 'apiKey';

leafUser: string = 'leafUserId';

companyName: string = 'companyName';

companyLogo: string = 'companyLogo';

yourFunctionNameHere(value: any) {

console.log(value.providersConnected);

console.log(value.providerWidgetStatus);

}

}

React

import { Leaf } from '@withleaf/leaf-link-react';

{ Leaf } import is the context that handle with the providers data.

Considering you have a custom component that need to handle or just receive the data updates from Provider Widget:

import { useLeaf } from '@withleaf/leaf-link-react';

export const MyComponent = () => {

// Import the states from the hook

const { providerWidgetStatus, providersConnected } = useLeaf();

return (

<>

<div>

<p data-testid='hook-title' style={{fontSize: '22px',}}>

{' '}

Hook State Example

</p>

<p data-testid='status'>

<span style={{fontWeight: 'bold', }} >

Status Code:

</span>{' '}

{providerWidgetStatus.code} |{' '}

<span style={{ fontWeight: 'bold', }} >

Status Message:

</span>{' '}

{providerWidgetStatus.message}

</p>

</div>

<hr />

<div>

{providersConnected.length === 0 ? (

<p>Providers List is empty</p>

) : (

<>

{providersConnected.map((provider, index) => (

<>

<p data-testid={`${provider.provider}-testid`}>

{' '}

Provider: <span>{provider.provider}</span>

</p>

<p>

{' '}

Created Time: <span>{provider.createdTime}</span>

</p>

</>

))}

</>

)}

</div>

</>

);

};

Then, wrap your component in the hook as a children

import { Leaf, Providers } from '@withleaf/leaf-link-react'

const Example = () => {

return (

<Leaf>

<MyComponent />

<Providers

isDarkMode={true}

companyName={'My Company Name'}

companyLogo={'url'}

leafUser={'myLeafUser'}

apiKey={'myApiKey'}

locale={'locale'}

/>

</Leaf>

);

};

From your top-level component can pass the current data to all components below, no matter how deep.

This variables will be updated every time the Provider update the steps i.e move from one step to other.

Tips

The way that the developer get the updated value from the hook can be different depending the of the application, personal preferences or the way it is architected. We suggest the following with useMemo but it can be also implemented with useEffect. useMemo runs the function and caches its result, which will only be recomputed if any value in the dependency array changes. It helps optimize performance by avoiding unnecessary recalculations.

Example

useMemo(() => {

//Something you want to update, as a state from the component.

}, [providerConnected, providerWidgetStatus])