UI SDK - Vanilla Javascript integration
SDK library integration
The Amberflo UI Kit SDK is a Vanilla Javascript development kit for our customers to be able to consume and make use of principal Amberflo views, for one of their customers, on their own site.
The SDK is a UI Kit wrapper, using the React UI Kit behind the scenes. This SDK will internally use React.JS, but does not require the customer to have a React project.
The SDK is responsible of making the API calls and rendering the components on a destination <div> on the final HTML code.
๐ Requisites
These are some of the languages where the SDK can be used: in React, Javascript, Angular, Vue.
1.Include the script in the <head> of your site:
๐ Make sure to use to the latest available version in the script (e.g.: 1.0.30). You can check versions under Releases section.
2. Retrieve your session token to access Amberflo API endpoints. With that session id, you will need to make a new instance of the AmberfloSDK included on the script above. To do that, you will have to add this code snippet under the first script tag you added:
๐Replace {{YOUR_SESSION_TOKEN}} with the token you got. For example, if you received a session token that was 1234abcd, you would instantiate the Amberflo SDK like so: amberflo = new AmberfloSDK("1234abcd"). To know more about how to get your session token read Get Session Token section.
3. Since sessions can expire, on your new instance of AmberfloSDK there is a method to set the new sessionId. You can call it anytime to amberflo.setSessionId("{{YOUR_NEW_SESSION_TOKEN}}");. The app will continue to work the same with the same ID.
4. To add a new Amberflo view, you will need to place a <div> on your code, with the class amberflo and a data-amberflo-type attribute to setup the element. This data-amberflo-type attribute is responsible for rendering the different views that we support.
It's also possible to customize the components by adding a specific color, choose to show the widget container and its title, the font size, font family, and even a custom font. To do that, use the following attributes:
- data-amberflo-colors Set a HEX code or string value of the primary color of your brand. We will automatically create a palette based on that color for all the components. By default it will use Amberflo colors.
- data-amberflo-font-size Enter a number, this is the base font size, since not all part of this view has the same font size, all internal components will calculate the percentage to show the desired font size for each internal view. Default value is 16, which is the default font size for all Amberflo components.
- data-amberflo-font-family This is a comma-separated name of fonts, it can be any font that is already supported and imported on your site. The browser will try to use the first font on that list, but if for some reason the font is not available, it will fall back to the right until a font is available. This is not common, but it could happen so we recommend having more than one font in the list.
- data-amberflo-font-custom If the font you are trying to use is not supported by the browser, nor one already added by you, you could use this prop to import a custom google font to your app. Besides importing the font, you need to specify the font name on the attributedata-amberflo-font-family.
- data-amberflo-with-container It receives a string saying "true" or "false", if true, it will show the container around the widget, similar to the ones on our app
- data-amberflo-with-title It receives a string saying "true" or "false", if true, it will show the title of the widget, it requires that the container is visible
- data-amberflo-title It receives a string specifying a custom title for the widget, if not provided, will use the widget default title
All the styles attributes above are optional, if none is provided, it will use Amberflo design system.
Some views may require to use of other attributes. Attributes can be updated programmatically at any time to render a different view or state. For example, you can render a Usage Table with a meter, and when you click a button, change that attribute to render the same view but with a different meter.
You must create a session token to interact with Amberflo, either directly with the API or through the AmberfloSDK.
To do so, you can retrieve it from an endpoint on your server using the browserโs fetch function on the client side. This is generally the best approach when your client side is a single-page application, especially if itโs built with a modern frontend framework such as React.
For more information check Create a session๏ปฟ
This example shows how to create the server endpoint that serves the client secret:
๐ The above example is in Node.js.
You can get X-API-KEY from the Amberflo site inside Settings -> Account Configurations -> API keys.
You can also get the customerIdfrom Amberflo site inside Customers โ Click on one customer โ Copy Customer ID.
This example demonstrate how to fetch the session token with JavaScript in the client side:
As you look through the Available Views๏ปฟ, you will notice some views have available events (e.g. on the Usage Table view, there is a datechange event which will fire when you change the date in the date picker). This gives you the ability to do additional things after an event has fired within the view.
Here is an example of how to use an event using the datechange event with the Usage Table view:
There are a few Views that display invoice-related data (i.e. Invoices List and Invoice Details). There are invoice-related settings a user can update at Amberflo | Settings | Invoice which affect how invoices are displayed through in these views.
The current available option/settings are:
- Displaying cached invoices
- Invoice data displayed will either be cached data or real-time data.
- Cached data is used to speed up how quickly invoice data can be retrieved.
- Group product items on invoices
- We list all product items and allow user to create categories to group on the invoices.
๏ปฟ
๐ Releases
01/19/2024 - Version 1.0.30 01/16/2024 - Version 1.0.29 01/10/2024 - Version 1.0.28 08/04/2023 - Version 1.0.27 08/04/2023 - Version 1.0.26 07/12/2023 - Version 1.0.25 02/06/2023 - Version 1.0.24 01/09/2023 - Version 1.0.23 12/27/2022 - Version 1.0.22 12/20/2022 - Version 1.0.21 12/15/2022 - Version 1.0.20 12/08/2022 - Version 1.0.19 11/24/2022 - Version 1.0.18 10/20/2022 - Version 1.0.17 10/12/2022 - Version 1.0.16 10/04/2022 - Version 1.0.15 09/14/2022 - Version 1.0.14 09/12/2022 - Version 1.0.13 09/01/2022 - Version 1.0.12 08/29/2022 - Version 1.0.11 07/29/2022 - Version 1.0.10 07/12/2022 - Version 1.0.9 07/07/2022 - Version 1.0.8 07/06/2022 - Version 1.0.7 06/07/2022 - Version 1.0.6 05/09/2022 - Version 1.0.5 05/07/2022 - Version 1.0.4 04/26/2022 - Version 1.0.3 04/21/2022 - Version 1.0.2 04/20/2022 - Version 1.0.1 04/13/2022 - Version 1.0.0
๏ปฟ
Attribute | Value |
---|---|
data-amberflo-type | usage-table |
data-amberflo-meters | Comma separated meters apiNames you want to see on the table. e.g.: ApiCalls,cluster_count,cluster_instance_hours,cluster_partitions,cluster_reads,cluster_storage,cluster_writes,CpuHours,DataVolumeGb,number_of_runs |
๏ปฟ | ๏ปฟ |
Example:
๏ปฟ
Example
Example
Example
Example
Example
Example
Example
๏ปฟ
Make sure that the data-amberflo-return-url page, includes the Amberflo script, and also is instantiated, the as you did for the page where this component is hosted.
Add the script:
And make sure you instantiate it:
Example:
- Inside the dashboard copy the publishable key. Check the image below for reference:
Appendix 1: Full Code Example
๏ปฟ