# Import Cut API

**URL:** <https://community.shotgridsoftware.com/t/import-cut-api/10338>\
**Category:** RV\
**Created:** [October 9, 2020, 6:24am UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338 "2020-10-09T06:24:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mharris](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/mharris/32/2644_2.png) [@mharris](https://community.shotgridsoftware.com/u/mharris)\
**Post date:** [October 9, 2020, 6:24am UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338/1 "2020-10-09T06:24:38Z")

</div>

Hello,

Is there any Python API support for the import cut tool in RV?

---

<div class="post-metadata">

**Author:** ![brandon.foster](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/brandon.foster/32/91_2.png) [@brandon.foster](https://community.shotgridsoftware.com/u/brandon.foster)\
**Post date:** [October 9, 2020, 1:21pm UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338/2 "2020-10-09T13:21:32Z")

</div>

Hey @mharris!

Outside of outlining the specifics of how the cut schema is organized on a per-entity and per-field basis, there are no API specific cut functions for ingesting/reading of cut info. You can read more about the cut schema here:

> **[Cut data model and schema](https://support.shotgunsoftware.com/hc/en-us/articles/222879527-Cut-data-model-and-schema)**
>
> Contents
> 
> Cut Field Details
> Cut Item Field Details
> 
> Shot fields
> Version fields
> 
> What about Shot fields?
> We have been tracking cut data in Shotgun—can I use that with the new review toolset?
> How can...

---

<div class="post-metadata">

**Author:** ![mharris](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/mharris/32/2644_2.png) [@mharris](https://community.shotgridsoftware.com/u/mharris)\
**Post date:** [October 9, 2020, 8:01pm UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338/3 "2020-10-09T20:01:30Z")

</div>

Hi @brandon.foster, I was thinking more along the lines of the Python commands built in to leverage off reading an EDL file and using the timing information to chop up a Sequence QuickTime file then automate creating the Shots.

---

<div class="post-metadata">

**Author:** ![Ahuge](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/ahuge/32/395_2.png) [@Ahuge](https://community.shotgridsoftware.com/u/Ahuge)\
**Post date:** [October 10, 2020, 7:05am UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338/4 "2020-10-10T07:05:48Z")

</div>

Have you looked into [OpenTimelineIO](https://github.com/PixarAnimationStudios/OpenTimelineIO) at all?

They have quite good support for most EDL formats as well as rv\_sessions and more!

---

<div class="post-metadata">

**Author:** ![brandon.foster](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/brandon.foster/32/91_2.png) [@brandon.foster](https://community.shotgridsoftware.com/u/brandon.foster)\
**Post date:** [October 12, 2020, 1:03pm UTC](https://community.shotgridsoftware.com/t/import-cut-api/10338/5 "2020-10-12T13:03:40Z")

</div>

Those sort of functions aren’t a part of the Shotgun API. @Ahuge’s suggestion sounds like the best way to go.