GET /api/v2/video/1049
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, PUT, PATCH, HEAD, OPTIONS
{ "category": "EuroPython 2011", "language": "English", "slug": "good-api-design", "speakers": [ "Alex Martelli" ], "tags": [ "api", "design", "interfaces" ], "id": 1049, "state": 1, "title": "Good API design", "summary": "[EuroPython 2011] Alex Martelli - 20 June 2011 in \"Track Spaghetti\"\n\n", "description": "Designing interfaces so that other code can interact with ours (whether our\ncode is a library, framework, application, website\u2026) is a very common and\nclearly crucial activity, but it's fraught with dangers - there's a lot stuff\nwe all keep doing wrong time after time. This talk shows some common\ncategories of API design errors encountered in the wild, with tips on how to\navoid them when you design your next API.\n\nGoals: to show you how to focus resources and attention to help avoid mistakes\nin API design. Prereqs: experience designing and developing software, esp.\nsoftware which needs to interact w/other existing software.\n\n", "quality_notes": "", "copyright_text": "Standard YouTube License", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\";hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\";hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "", "duration": null, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "", "whiteboard": "", "recorded": "2011-07-21", "added": "2012-08-30T21:02:17", "updated": "2014-04-08T20:28:27.734" }