Subject: Request for Authentication Process Clarification and Issue Reporting for API Data Retrieval

[ELHADIALLO]

Dear Revenera Community,

I am currently integrating the Usage Intelligence Reporting API into our system and have encountered a challenge with the authentication process, specifically regarding the expected header parameters for the API requests. In addition, I am using Python for the implementation, and I have encountered an error with the code "400.002.002" stating "Cookie Missing". Could you guide me on how to correctly set up the authentication headers, and also advise on the correct handling of cookies within Python to avoid this error?

The areas needing clarification are:

1. **Content-Type**: Should this be `application/json` for all requests?
2. **RUI-Client**: Should this be the name of our application?
3. **RUI-Client-Version**: Does this refer to the API version or our application's version?
4. **Origin**: Should we use `https://analytics.revenera.com` or our application's URL?

Your guidance on these matters would be greatly appreciated to ensure a smooth integration process.

Best regards,

[BhargavaNagaraj]

Hi @ELHADIALLO,

There is an additional step required, and we will update the documentation accordingly. Since most of our team is on holiday due to the region's public holiday schedule, we will be able to assist you by end of this week or early next week. In the meantime, could you please create a support ticket? https://community.flexera.com/t5/Usage-Intelligence-Knowledge/How-to-Create-a-Support-Ticket-for-Usage-Intelligence/ta-p/142952

Thank you,

Bhargava

[AkSharma]

Hi @ELHADIALLO,

We have updated the v3 API documentation with additional instructions required for authentication. 

Thanks

[jenseggerath]

Hi @AkSharma , hi @BhargavaNagaraj , 

The documentation is now good enough to get the authentication done and I was also able to download the raw data files, but it's still not a comprehensive documentation.

You didn't answer the OP's questions above, which probably every V3 API user has. The example values seem to work, but is this the parameterization you intended to get from everybody? What's the purpose of these fields then? 
And why does the /v3/request-csrf end point not have its own section under "Auth"?

Regards

Jens

[AAshok]

Hi @jenseggerath,

Thank you for your feedback. We are continuously working on improving the documentation and will update it with relevant explanations to address the unanswered questions. Your input is valuable, and we appreciate your patience as we strive to enhance our documentation.

Thanks