# Audio Analysis API

### Introducing Emotion-Logic Cloud Services

Emotion-Logic offers Cloud Services as a convenient alternative to self-hosting, making it easier than ever to implement our genuine emotion detection technology. With Emotion-Logic Cloud Services, you gain access to our advanced emotion detection system without the need to install or manage Docker containers on your own servers.

### Why Choose Emotion-Logic Cloud Services?

  
**Fast Deployment**

Get started quickly without complex installation processes or server setup.

**Hassle-Free Server Management**

We handle server management, maintenance, and updates, allowing you to focus on your core projects and applications.

**Perfect for Testing, Development, and Small-Scale Use**

Ideal for experimenting with our technology, developing new applications, or supporting small-scale use cases.

**Pay-Per-Use Pricing**

While the cost per test may be higher than self-hosting, our pay-per-test pricing model ensures you only pay for what you use, making it a cost-effective solution for many projects.


### Getting Started

  
To begin using Emotion-Logic Cloud Services, simply create an account on our platform, start a new project, and create the application you need. A set of API keys and passwords will be automatically generated for you. This streamlined process provides seamless access to our cloud-based API, enabling you to integrate our genuine emotion detection technology effortlessly into your projects.

###    
API Options for Flexible Emotion Detection

  
Emotion-Logic offers a variety of API options to suit different needs, ensuring that our genuine emotion detection technology is adaptable for a wide range of use cases:

**Pre-Recorded File Analysis**

Analyze specific conversations or feedback from a single audio file.

**Questionnaire (Multi-File Structure) Analysis**

Process multiple questionnaires or survey responses, delivering emotion detection insights for each file.

**Streaming Voice Analysis**

Enable real-time emotion detection for live interactions or voice-controlled devices.  
   
**Explore "Analyze Now" APIs for Advanced Applications**  
For more complex use cases, our "Analyze Now" APIs—including FeelGPT, AppTone, and the Emotional Diamond Video Maker—combine Layered Voice Analysis (LVA), Speech-to-Text (S2T), and Generative AI to deliver a complete 360-degree analysis. These APIs require an API User to be created and provide enhanced capabilities for deeper emotional insights, textual context integration, and generative interpretations.

   
These versatile options make it easy to integrate Emotion-Logic into diverse applications, enabling more engaging, emotionally aware user experiences while supporting advanced business needs.

[Pre recorded files API requests](https://emlo.cloud/documentation/api-requests)

[API response examples](https://emlo.cloud/documentation/api-response)

[Realtime analysis (streaming)](https://emlo.cloud/documentation/realtime-analysis)

[Analyze Now AP](https://emlo.cloud/documentation/analyze_now_api)

## Pre-recorded audio analysis requests

## Offline analysis requests

[Analyzing an uploaded media file](https://emlo.cloud/documentation/analysis-request-upload-file)

[Analyzing a media file by URL](https://emlo.cloud/documentation/audio-analysis-request-with-url "Analyzing a media file by URL")

[Test analysis request](https://emlo.cloud/documentation/test-analysis-request "Test analysis request") (Questionnaire set of recordings)

# Analysis request with an uploaded file

This route accepts a file on a form data and returns analysis results.

**Docker URI:** http://\[docket-ip\]/analysis/analyzeFile **Cloud URI:** https://cloud.emlo.cloud/analysis/analyzeFile **Method:** POST

<table border="1" id="bkmrk-header-value-comment"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>Header</td><td>Value</td><td>Comment</td></tr><tr><td>Content-Type</td><td>multipart/form-data</td><td> </td></tr></tbody></table>

**Common request params**

<table border="1" id="bkmrk-parameter-is-mandato"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>**Parameter**</td><td>**Is Mandatory**</td><td>**Comment**</td></tr><tr><td>file</td><td>Yes</td><td>A file to upload for analysis

</td></tr><tr><td>outputType</td><td>No</td><td>Analysis output format. Can be either "json" or "text"

**json** - most common and useful for code integration. This is the default response format

**text** - CSV-like response.

</td></tr><tr><td><div><div>sensitivity</div></div></td><td>yes</td><td>May be "normal", "low" or "high".

Normal Sensitivity: Ideal for general use, providing a balanced approach to risk assessment.  
High Sensitivity: Recommended for scenarios where identifying potential risks, even subtle ones, is crucial. However, it may result in a higher detection of false positives.  
Low Sensitivity: Suitable for scenarios where only pronounced risks are of interest, hence reducing the chance of false positives.

</td></tr><tr><td><div><div>dummyResponse</div></div></td><td>No</td><td>For development purpose. If "true", the response will contain dummy values, and the request will not be charged

</td></tr><tr><td><div><div>segments</div></div></td><td>No</td><td>By default, the analysis process divids the audio file into segments of 0.4 to 2.0 seconds length. It is possible to pass an array of segments-timestamps, and the analysis will follow these timestamps when dividing the audio.

The "**segments**" attribute is a JSON string wich represents an array of elements, where each element has a "start" and "end" attribute.

**channel** : The channel number in the audio

**start** : the offset-timestamp of the segment start time

**end** : the offset-timestamp of the segment end time

Example: <span data-offset-key="ndbk-0-0"><span data-text="true">\[</span></span><span data-offset-key="ndbk-1-0"><span data-text="true">{"channel": 0,"start" : 0.6,"end" : 2.5</span></span><span data-offset-key="ndbk-2-0"><span data-text="true">},</span></span><span data-offset-key="ndbk-3-0"><span data-text="true">{"channel": 0,"start" : 3,"end" : 3.5</span></span><span data-offset-key="ndbk-4-0"><span data-text="true">}\]</span></span>

</td></tr><tr><td><div><div>requestId</div></div></td><td>No</td><td>A string, up to 36 characters long. The requestId sent back to the client on the response, so clients can associate the response to the request

</td></tr><tr><td><div><div>backgroundNoise</div></div></td><td>No</td><td>0 - Auto backbground noise calculation (same as not sending this param)

Any other number - the background noise value to use for analysis

</td></tr></tbody></table>

**Additional parameters for cloud-specific request**

<table border="1" id="bkmrk-parameter-is-mandato-1"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>**Parameter**</td><td>**Is Mandatory**</td><td>**Comment**</td></tr><tr><td>apiKey</td><td>On cloud-requests only</td><td>For cloud-request only. This is the application API key created on the platfrom

</td></tr><tr><td>apiKeyPassword</td><td>On cloud-requests only</td><td>For cloud-request only. This is the application API key password created on the platfrom

</td></tr><tr><td>consentObtainedFromDataSubject</td><td>On cloud-requests only</td><td>For cloud-request only. must be true.

The meaning of this param is that you got permission from the tested person to be analyzed

</td></tr><tr><td><div><div>useSpeechToText</div></div></td><td>No</td><td>If "true", and the application allowed for speech-to-text service, a speech-to-text will be executed for this request (extra cost will be applied)

</td></tr></tbody></table>

**Example for analysis request to EMLO cloud**

**[![Captura de Pantalla 2025-03-11 a la(s) 10.11.28 a.m..png](https://docs.ado-tech.com/uploads/images/gallery/2025-03/scaled-1680-/igXj2qn8TBTiccUN-captura-de-pantalla-2025-03-11-a-las-10-11-28-a-m.png)](https://docs.ado-tech.com/uploads/images/gallery/2025-03/igXj2qn8TBTiccUN-captura-de-pantalla-2025-03-11-a-las-10-11-28-a-m.png)**

# Questionnaire-based risk assessment

This route provides risk assessment based on a set of topics to analyze.

Each file in the request may be associated with one or more topics, and for each topic, a question may have a different weight.

**Docker URI**: http://\[docket-ip\]/analysis/analyzeTest  
**Cloud URI**: https://cloud.emlo.cloud/analysis/analyzeTest  
**Method**: POST

<table border="1" id="bkmrk-header-value-comment-1"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>Header</td><td>Value</td><td>Comment</td></tr><tr><td>Content-Type</td><td>application/json</td><td> </td></tr></tbody></table>

**Common request params**

<table border="1" id="bkmrk-parameter-is-mandato-2"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>**Parameter**</td><td>**Is Mandatory**</td><td>**Comment**</td></tr><tr><td>url</td><td>Yes</td><td>The URL of the file to be analyzed. This URL must be accessible from the docker

</td></tr><tr><td>outputType</td><td>No</td><td>Analysis output format. Can be either "json" or "text"

**json** - most common and useful for code integration. This is the default response format

**text** - CSV-like response.

</td></tr><tr><td>sensitivity</td><td>Yes</td><td>May be "normal", "high" or "low".

Normal Sensitivity: Ideal for general use, providing a balanced approach to risk assessment.  
High Sensitivity: Recommended for scenarios where identifying potential risks, even subtle ones, is crucial. However, it may result in a higher detection of false positives.  
Low Sensitivity: Suitable for scenarios where only pronounced risks are of interest, hence reducing the chance of false positives.

</td></tr><tr><td>dummyResponse</td><td>No</td><td>For development purpose. If "true", the response will contain dummy values, and the request will not be charged

</td></tr><tr><td>segments</td><td>No</td><td>By default, the analysis processs divids the audio file into segments of 0.4 to 2.0 seconds length. It is possible to pass an array of segments-timestamps, and the analysis will follow these timestamps when dividing the audio.

The "**segments**" attribute is an array of elements, where each element has a "start" and "end" attribute.

**channel** : The channel number in the audio

**start** : the offset-timestamp of the segment start time

**end** : the offset-timestamp of the segment end time

</td></tr><tr><td>requestId</td><td>No</td><td>A string, up to 36 characters long. The requestId sent back to the client on the response, so clients can associate the response to the request

</td></tr></tbody></table>

**The questionnaire section of the request includes the "***isPersonality***" flag that can be set as** *"true"* **or** *"false"* **and has effect in HR applications datasets.**

Use "true" to mark a question for inclusion into the personality assessment set, and into the Strengths/Challanges analysis section available in the HR datasets.

**Example for analysis request to the docker**

**[![Captura de Pantalla 2025-03-11 a la(s) 10.13.46 a.m..png](https://docs.ado-tech.com/uploads/images/gallery/2025-03/scaled-1680-/PTYLI3JXWaaT0UHT-captura-de-pantalla-2025-03-11-a-las-10-13-46-a-m.png)](https://docs.ado-tech.com/uploads/images/gallery/2025-03/PTYLI3JXWaaT0UHT-captura-de-pantalla-2025-03-11-a-las-10-13-46-a-m.png)**

**Additional parameters for cloud-specific request**

<table border="1" id="bkmrk-parameter-is-mandato-3"><colgroup><col></col><col></col><col></col></colgroup><tbody><tr><td>**Parameter**</td><td>**Is Mandatory**</td><td>**Comment**</td></tr><tr><td>apiKey</td><td>On cloud-requests only</td><td>For cloud-request only. This is the application API key created on the platfrom

</td></tr><tr><td>apiKeyPassword</td><td>On cloud-requests only</td><td>For cloud-request only. This is the application API key password created on the platfrom

</td></tr><tr><td>consentObtainedFromDataSubject</td><td>On cloud-requests only</td><td>For cloud-request only. must be true.

The meaning of this param is that you got permission from the tested person to be analyzed

</td></tr><tr><td><div><div>useSpeechToText</div></div></td><td>No</td><td>If "true", and the application allowed for speech-to-text service, a speech-to-text will be executed for this request (extra cost will be applied)

</td></tr></tbody></table>

**Example for analysis request to EMLO cloud**

**[![Captura de Pantalla 2025-03-11 a la(s) 10.14.36 a.m..png](https://docs.ado-tech.com/uploads/images/gallery/2025-03/scaled-1680-/wcXxfugqMA0FQVIo-captura-de-pantalla-2025-03-11-a-las-10-14-36-a-m.png)](https://docs.ado-tech.com/uploads/images/gallery/2025-03/wcXxfugqMA0FQVIo-captura-de-pantalla-2025-03-11-a-las-10-14-36-a-m.png)**