[10:46:12 CDT(-0500)] <TonyUnicon> hmm bridge isnt working for me
[10:46:13 CDT(-0500)] <TonyUnicon> redialing
[11:04:03 CDT(-0500)] <JasonElwood> Is there an API for templates?
[11:23:50 CDT(-0500)] <dmccallum54> yes
[11:23:53 CDT(-0500)] <dmccallum54> root is /1/reference/map/template
[11:24:09 CDT(-0500)] <dmccallum54> a GET on that supports the following query params
[11:24:28 CDT(-0500)] <dmccallum54> isPrivate, objectStatus, divisionCode, programCode, departmentCode
[11:24:41 CDT(-0500)] <dmccallum54> then there is / which supports GET
[11:25:07 CDT(-0500)] <JasonElwood> thanks
[11:25:24 CDT(-0500)] <dmccallum54> and /summary which supports GET and the same query params as /
[11:25:37 CDT(-0500)] <dmccallum54> a POST to / is a create
[11:25:58 CDT(-0500)] <dmccallum54> a POST to /print is a printable payload
[11:26:43 CDT(-0500)] <dmccallum54> (/print takes a complete template JSON object and prints it - we do this b/c you have to be able to print an unsaved template)
[11:27:32 CDT(-0500)] <dmccallum54> a POST to /email generates an email. it also takes a complete template JSON object. the response is just a dummy confirmation string
[11:28:43 CDT(-0500)] <dmccallum54> the / resource also accepts a PUT, which is an update. the request payload is the proposed new state of the template
[11:28:57 CDT(-0500)] <dmccallum54> and / also accepts a DELETE
[11:29:35 CDT(-0500)] <dmccallum54> and there's /validate, which accepts a POST of an arbitrary template JSON object to be validated and returns a marked up template JSON object
[11:29:39 CDT(-0500)] <dmccallum54> that's it