restrict concurrent access to api

I am running into an issue of having lots of "Invalid Conversation Token" and "Conversation Out-of-Sync" due to concurrent usage.

Typically, this eventually works out with retries but would be much more expedient/efficient to restrict concurrent access to the api with a locking mechanism.

I am using django so I am leaning towards a fast implementation by storing totals and authenticators in a database with the django orm, using cache locks, and letting retries work out the kinks that accompany possible lock evictions with a cache backend.

Is concurrent access restriction out of the scope of this project?