<div dir="ltr">I just realized that the iOS Variant endpoint still expects an mutlipartform :/ that will make it a bit more difficult (mostly because of the certificate) <div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 3, 2015 at 12:02 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi peeps,<div><br></div><div>We recently added some documentation around integration : <a href="https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration" target="_blank">https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration</a> (still on the staging site but will be released soon) </div><div>and also some scripts that shows how this integration can work : <a href="https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js</a></div><div><br></div><div>And that made me think of the following use case : </div><div><br></div><div>A third party should be able to create in one call the Push App and its variants. That would not be too much work on the server side, so wdyt ? </div><div><br></div><div><br></div></div>
</blockquote></div><br></div>