Creating delicious APIs for Django apps since 2010. v1.0.0-beta
Python Shell
Clone or download
Pull request Compare This branch is 3 commits ahead, 656 commits behind django-tastypie:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


django-tastypie fork

Fork created for CCG, so we can build eggs containing newer features than the latest release in a controlled manner.

Whenever you want to create a new version, just add the '.ccg.YYYYMMDD' to the version number in and then create a new tag for the release.

Example: version number was '0.9.12-alpha'

It changed to '0.9.12-alpha.ccg.20121019' for our first release.

Then tag with:

$ git tag -a v0.9.12-alpha.ccg.20121019
$ git push --tags

You can download your tarball from Github Tags and build a binary egg in your VM, then upload_egg it to our repo.


Creating delicious APIs for Django apps since 2010.

Currently in beta (v0.9.11) but being used actively in production on several sites.




What's It Look Like?

A basic example looks like:

# myapp/
# ============
from tastypie.resources import ModelResource
from myapp.models import Entry

class EntryResource(ModelResource):
    class Meta:
        queryset = Entry.objects.all()

# =======
from django.conf.urls.defaults import *
from tastypie.api import Api
from myapp.api import EntryResource

v1_api = Api(api_name='v1')

urlpatterns = patterns('',
    # The normal jazz here then...
    (r'^api/', include(v1_api.urls)),

That gets you a fully working, read-write API for the Entry model that supports all CRUD operations in a RESTful way. JSON/XML/YAML support is already there, and it's easy to add related data/authentication/caching.

You can find more in the documentation at

Why Tastypie?

There are other, better known API frameworks out there for Django. You need to assess the options available and decide for yourself. That said, here are some common reasons for tastypie.

  • You need an API that is RESTful and uses HTTP well.
  • You want to support deep relations.
  • You DON'T want to have to write your own serializer to make the output right.
  • You want an API framework that has little magic, very flexible and maps well to the problem domain.
  • You want/need XML serialization that is treated equally to JSON (and YAML is there too).
  • You want to support my perceived NIH syndrome, which is less about NIH and more about trying to help out friends/coworkers.

Reference Material

Commercial Support

If you're using Tastypie in a commercial environment, paid support is available from Toast Driven. Services offered include:

  • Advice/help with setup
  • Implementation in your project
  • Bugfixes in Tastypie itself
  • Features in Tastypie itself

If you're interested, please contact Daniel Lindsley (