-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
embedly requires API key #25
Comments
Hmm...yeah, this definitely needs to be addressed. Looking into the best way to implement this. I'm somewhat kicking myself for writing the providers as database objects, would be nicer to have more programmatic control of them. |
This commit 813a34e makes it easier to include the key in the (activated) embedly providers. I've been able to work around the issue in my case by passing a |
Yeah, totally -- it's not a problem if you're doing by hand, but if you want it to "just work" with the tags it gets a little tricky -- the internal API of the app probably needs to be refactored. One option is to add arbitrary url parameters to a stored provider and just use those on every request, but it seems kinda gross. |
Why not look for a embed.ly key in the settings.py file? |
yeah but you don't want to send your api key to youtube -- need to be able to specify "these" credentials -> "these" oembed providers |
You may want to check out my new project: http://micawber.readthedocs.org/ it should be able to better handle embed.ly |
OK, so how do I provide my embed.ly key when using djangoembed? I don't see this documented anywhere. |
@coleifer: |
Using embed.ly as an endpoint is really cool, but requires an api key. It will work, but after a while the response will be a 403:
However, I don't see a way to supply an API key using djangoembed
The text was updated successfully, but these errors were encountered: