{"__v":18,"_id":"54349c225b10711400c6c539","category":{"__v":8,"_id":"54343531bfaa3d0800c4d4b0","pages":["54349c225b10711400c6c539","54349c905b10711400c6c53b","54370bea4e799808006da391","54370fa726469424002a6e19","5480aad4e952bb1a006b320c","5638d6c12fc5520d001a4cc9","568fe01b21fcf0190071d8fb"],"project":"54343170fa5527080064f449","version":"54343531bfaa3d0800c4d4af","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-10-07T18:31:12.137Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"is_link":false,"parentDoc":null,"project":"54343170fa5527080064f449","user":"54343147fa5527080064f43f","version":{"__v":27,"_id":"54343531bfaa3d0800c4d4af","forked_from":"54343170fa5527080064f44c","project":"54343170fa5527080064f449","createdAt":"2014-10-07T18:47:13.086Z","releaseDate":"2014-10-07T18:47:13.086Z","categories":["54343531bfaa3d0800c4d4b0","543435b1edce040800409240","543435b9edce040800409241","543435bcedce040800409243","543435bfedce040800409244","543435c2edce040800409245","54370cc426469424002a6dfa","54370cf026469424002a6dfd","5437129d26469424002a6e2f","543712d226469424002a6e30","5480c8fd74904f1a00053c86","54aafc6eefb39016009e4d71","54ac1d36de18cc1400226e01","54ad59369219922100751732","54b41bcf4f25cb1600518d2c","54b533a3a806f40c0050d53c","54b54bbf96fe3c0b00d38d2a","54b688a27379a90c00f53a8a","54b699efbc1a46160005edfa","54b8191691011f0b00068804","54bfb002d03bfc0d0000e814","54bfb33ed03bfc0d0000e816","55a3e94e912a6e2300882cdb","55a56c370f354f0d00fd02a8","55e85ad034516037002e9325","5638ecb62fc5520d001a4cf9","572cba2fc310640e008f63d5"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3.0"},"updates":["54b5803f2562600c00e05f06"],"next":{"pages":[],"description":""},"createdAt":"2014-10-08T02:06:26.963Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"basic_auth":false,"results":{"codes":[]},"settings":"","try":true,"auth":"never","params":[],"url":""},"isReference":false,"order":0,"body":"[block:html]\n{\n  \"html\": \"<iframe src='https://s3.amazonaws.com/static.mediasilo.com/embed/index.html?mrss=https://feeds.mediasilo.com/FF71B713-3900-4439-86E9-56B88F6083B9/mrss/' width='720' height='405' frameBorder='0' />\"\n}\n[/block]\nThe MediaSilo API version 3.0 is a stateless RESTful service that allows you to interact programmatically with MediaSilo. It's an easy and convenient way to build applications that integrate seamlessly with our platform. The MediaSilo API can be used for to develop custom client applications, extensive system level integrations, workflow automations, and more.  It can support just about any application that needs access to content or information on the MediaSilo platform.\n\nWe chose REST because it is simple to use and there is a wealth of quality development resources available online. Many projects already have native support for dealing with REST, which makes getting started easy for developers. If you are not familiar with REST or how it works, check out [A Beginners Guide to HTTP and REST](http://code.tutsplus.com/tutorials/a-beginners-guide-to-http-and-rest--net-16340). \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"What you can do\"\n}\n[/block]\nAll of MediaSilo's products and applications are built on top of this same API--which means you can build anything from a small app to a fully-fledged media management system. Examples of what customers have built:\n\n- Online stock footage portal with store\n- Mobile casting apps\n- Media portals\n- Screening rooms\n- Custom uploaders\n- Adobe Panels\n- Presentation apps\n- Dailies apps\n- Custom integrations between multiple systems\n- Automations that trigger workflows in other systems when media is changed in MediaSilo\n\nMediaSilo's API is getting more powerful every day, with new API endpoints for video encoding, watermarking, and media distribution in the works. \n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Rate Limits\",\n  \"body\": \"API requests are rate limited by account. A standard account has a limit of 10,000 requests per hour and developer accounts are limited to 500 per hour. Each response includes the remaining number of calls in the header file.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"REST\"\n}\n[/block]\nWhile REST is a fluid standard that leaves specifics of the implementation up to the developer, MediaSilo's REST API uses best practices and a standards-based approach wherever possible. If you feel like we missed the mark on something or would like to see support for new functionality, we welcome your feedback.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Sample Applications\"\n}\n[/block]\nMany applications have been built on the MediaSilo platform. Common applications have been made available as working code samples on the \"Code Samples\" section. Feel free to download and experiment!","excerpt":"[![Slack Status](http://slack.mediasilo.com:8080/badge.svg)](http://slack.mediasilo.com:8080)","slug":"overview","type":"basic","title":"Overview"}

Overview

[![Slack Status](http://slack.mediasilo.com:8080/badge.svg)](http://slack.mediasilo.com:8080)

[block:html] { "html": "<iframe src='https://s3.amazonaws.com/static.mediasilo.com/embed/index.html?mrss=https://feeds.mediasilo.com/FF71B713-3900-4439-86E9-56B88F6083B9/mrss/' width='720' height='405' frameBorder='0' />" } [/block] The MediaSilo API version 3.0 is a stateless RESTful service that allows you to interact programmatically with MediaSilo. It's an easy and convenient way to build applications that integrate seamlessly with our platform. The MediaSilo API can be used for to develop custom client applications, extensive system level integrations, workflow automations, and more. It can support just about any application that needs access to content or information on the MediaSilo platform. We chose REST because it is simple to use and there is a wealth of quality development resources available online. Many projects already have native support for dealing with REST, which makes getting started easy for developers. If you are not familiar with REST or how it works, check out [A Beginners Guide to HTTP and REST](http://code.tutsplus.com/tutorials/a-beginners-guide-to-http-and-rest--net-16340). [block:api-header] { "type": "basic", "title": "What you can do" } [/block] All of MediaSilo's products and applications are built on top of this same API--which means you can build anything from a small app to a fully-fledged media management system. Examples of what customers have built: - Online stock footage portal with store - Mobile casting apps - Media portals - Screening rooms - Custom uploaders - Adobe Panels - Presentation apps - Dailies apps - Custom integrations between multiple systems - Automations that trigger workflows in other systems when media is changed in MediaSilo MediaSilo's API is getting more powerful every day, with new API endpoints for video encoding, watermarking, and media distribution in the works. [block:callout] { "type": "info", "title": "Rate Limits", "body": "API requests are rate limited by account. A standard account has a limit of 10,000 requests per hour and developer accounts are limited to 500 per hour. Each response includes the remaining number of calls in the header file." } [/block] [block:api-header] { "type": "basic", "title": "REST" } [/block] While REST is a fluid standard that leaves specifics of the implementation up to the developer, MediaSilo's REST API uses best practices and a standards-based approach wherever possible. If you feel like we missed the mark on something or would like to see support for new functionality, we welcome your feedback. [block:api-header] { "type": "basic", "title": "Sample Applications" } [/block] Many applications have been built on the MediaSilo platform. Common applications have been made available as working code samples on the "Code Samples" section. Feel free to download and experiment!