tastypie

I keep getting a 401 response when I try to use authentication = ApiKeyAuthentication() in my ModelResource. I looked at Django Tastypie: How to Authenticate with API Key and he uses the get parameters to solve his issue. If I try use get parameters it picks up username but not api_key! This works in browser http://127.0.0.1:8000/api/v1/spot/8/?username=darren&api_key=9999d318e43b8055ae32d011be5b045ad61dad50 Sending via curl in terminal doesn't pickup api_key parameter curl --dump-header - http://127.0.0.1:8000/api/v1/spot/8/?username=darren&api_key=9999d318e43b8055ae32d011be5b045ad61dad50 Why

We're building a web application using Django/TastyPie as the back-end REST service provider, and building an AngularJS based front end, using lots of $resource based services to CRUD objects on the server. Everything is working great so far! But, we would like to reduce the amount of data that we're shipping around when we want to update only one or two changed fields on an object. TastyPie supports this using the HTTP PATCH method. We have defined a .diff() method on our objects, so we can determine which fields we want to send when we do an update. I just can't find any documentation on how

I consider it a standard that an object-creating function returns the newly created object. So, any idea how do you do that in tastypie? When I send the POST request, the object is created, I get nothing in response, though. What I would like is to receive the JSON form of the newly created object (or at least the PK). I tried overriding the dehydrate method, but it seems that it's not even called when it comes to POST. Any ideas? Can't believe the answer was so easy. http://django-tastypie.readthedocs.org/en/latest/resources.html#always-return-data Just add always_return_data = True to your

I had a simple question on filtering in tastypie. I want to filter with multiple values. For example: /api/v1/message/?accountId=1,5,12 This doesnt work. Any idea how i can do this? Do i need to use advanced filtering? If yes, how do I go about creating such a filter? A simple effortless example of puesdo-code would be great! Thanks! Hmm, You can do this: /api/v1/message/?accountId__in=1&accountId__in=5&accountId__in=12 PS: in filtering meta attribute, add {'accountId': ALL} The most recent version seems to work pretty easily - just use an "__in": /api/v1/message/?accountId__in=1,5,12 (I

I'm using require.js to help organize my Backbone.js based application. I'm trying to figure out the right way to use a 3rd party javascript library that is not AMD compatible with require.js The library in questions is backbone-tastypie.js . Basically what the library does is monkeypatch some of the prototype methods of Backbone to provide simpler support for the TastyPie Django REST framework. It does this by directly manipulating the Backbone object in the global namespace. However, since I'm using Backbone.js as a require.js module, it isn't available when this library tries to access it.

How does the Tastypie APIKey authentication work? I know there is a signal as mentioned in the documentation: from django.contrib.auth.models import User from django.db import models from tastypie.models import create_api_key models.signals.post_save.connect(create_api_key, sender=User) However, when is this called? If I want to give a user their APIkey I know I can find it in the APIKey db that this create_api_key function adds the key into, but where and when do I call this models.signals.post_save function? Is this just another django model? I think it is? Is this called everytime a user