{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/7ebffa5929fd453d8a8609d468dbe017\" frameborder=\"0\" width=\"2252\" height=\"1689\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1689,"width":2252,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1689,"thumbnail_width":2252,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/7ebffa5929fd453d8a8609d468dbe017-f4a34d704b062134.gif","duration":398.06,"title":"Understanding OneStream API Access and Audit Logging","description":"In this video, I explain how accessing OneStream through the REST API works, emphasizing that it mirrors the permissions you have within the application. I demonstrate cloning a member and show how changes are logged in the audit trail, ensuring all actions are tracked just like in the OneStream UI. I also walk through pushing an assembly and editing rules, highlighting that all modifications are made through the API without granting additional access. My goal is to clarify that this method maintains security while providing a programmatic way to interact with OneStream. Please review the examples I provided and let me know if you have any questions."}