[Cmacc] CommonAccord API

[Christopher Clark]

I'd like to start a conversation about what the CommonAccord API should
look like.

Reason

APIs are super important. Twitter, for example, doesn't really do much, but
it was designed from the ground up with a good API. Then other people
started using the Twitter API to do awesome stuff. Now, Twitter has huge
momentum partly because of all the tools that have been developed for
Twitter.

How

Maybe we should just start a Google Doc where we write down what the API
should look like?

There is a tool called RAML <http://raml.org/> which seems like a very
popular way to define an API. Maybe as we start to finalize what the API
should look like, we can write it up there?

Some Possible Functions

   - GET a list of all legal document templates and total count of templates
   - GET a list of templates for a particular type of document, like NDAs
   - GET a particular template
   - POST private data to a particular template, which will return a
   document rendered with the private data
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.commonaccord.org/archive/cmacc/attachments/20141228/ee37ec01/attachment.html>