Importing models from a different Django project
Wouldn't there be security issues at letting an external site dictate what your db's structure looks like? A problem of any kind (or a man in the middle attack) could completely modify (or destroy) your database without you doing anything.
I'd say it's better to have API versions than what you're asking for. I'd prefer to have 2 concurrent versions running at the same time, to let the time for the API consumers to update their schemas, than force automatic updates of their schemas and data. And in general, if possible, I'd only use a single API version, taking care to always keep a compatibility with older implementations.
But I'm just saying that for general public API, I don't know how open your API should be and how close your developpements (API and consumer) are, so I may be completely out of your scope!
I am setting up a public API for my app. I want to segregate my API code from my application code, so I am putting it in a new django project and am using "Django REST Framework" to build the scaffolding for the public API services.
I'm struggling with how to keep models in sync between my main application project, and this new Django project for the API... product development may continue in the application project that necessitates models changes, and I'd like those models changes to be propagated to the API project. 
Is there a way to point to, or import, models from a different Django project?