---
title: How are we doing it?
slug: how-are-we-doing-it
description: Learn how to seamlessly integrate xAPI into Hype with this comprehensive document. Discover three effective methods for organizing xAPI statements before they are sent to a Learning Record Store (LRS), including using an export script, leveraging the HTML
docTags: 
createdAt: 2022-04-12T08:30:30.000Z
---

The integration of xAPI into Hype takes the form of an extension. Sometimes other applications may call it a plugin, but Max Ziebell calls his work extensions, which is more appropriate. It opens up the functionality of Hype into other worlds.

Currently we are using three methods to organise the xAPI statement before it's sent to a Learning Record Store(LRS).

**Method 1:** You load an export script into Hype that give you taylored options in the 'actions' panel to create your xAPI statement. We will show you how to do this later.

::Image[]{src="https://api.archbee.com/api/optimize/g-TEMWDtkenjdIIxVVk08/1YlBsPxo4U3MEQtFHn7mZ_exportscriptexample.png" size="26" width="546" height="1076" position="center" showCaption="false"}

**Method 2:** You use the HTML attributes panel in the 'information' tab to organise your xAPI statements. More about this later.

::Image[]{src="https://api.archbee.com/api/optimize/g-TEMWDtkenjdIIxVVk08/Vj86InP-KBC8BgTiumgQD_attributesexample.png" size="26" width="528" height="1226" position="center" showCaption="false"}

**Method 3:** The third method of sending a statement is with a function. A function can be trigered anywhere in a Hype project. In a timeline, or in the Actons tab of Hype. It can look something like this:

```javascript
	
	HypeXAPI.sendStatementByConfig({
		verb: 'attempted',
		object: 'solo-hang-gliding',
		result:'knowledge-check_1' ,
	    context:'strategy101',
	});


```



Before we show you how to actually export a statement, we need to show you how to organise your xAPI data.