I'm trying to create a simple application that reminds me of two weeks before I was supposed to get a delivery. My data is store in a Priority database and I'm looking for a way to read it using code (prefer in Python).
I read about Priority REST API and tested it with the examples that are in the site(https://prioritysoftware.github.io/restapi/request/). it seems like this is the way to do it but I see that it requires a URL to the Priority account and I don't know what is my URL because I use the desktop app.
So I have 2 questions:
Is using the API is the best way?
how do I find the URL to my account?
In addition I would be happy for further help regarding my idea for a program reminiscent of two weeks before receiving a delivery (examples, tips, ways to implement and so on).
Thank in advance
In order to use Priority API you need to install its application server.
More information can be found here.
If you are working locally you can access carefully directly to your SQL server and look for your data.
Priority has built-in functionality to send email reminders (BPM rules)
I'd like to be able to add a user as a guest to a project specific to that individual, but it looks like I cannot do this programmatically and must instead resort to manually adding them as a guest. Is there anything I'm missing in the API documentation? Is there an undocumented feature that would let me do so? Or am I just out of luck?
It is currently not possible to manage users of an organization via the API.
This is on our API roadmap, which I hope to publish a public version of soon.
You can subscribe to incremental changes of our API and it's documentation on API changelog https://www.apichangelog.com/api/asana
I need to implement direct call feature via vicidial in my web application.
Let me explain the flow to better understand what I need to do. user would be able to login in vicidial via a webpage of my app. then can call on any number by entering number.
Is there any doc or wiki available to implement this feature. Guidance in simple steps would also be appreciating.
Thanks in advance :)
We implemented something like that using a product called WombatDialer that offers good APIs and is quite easy to set up (well, easier than ViciDial).
See http://www.wombatdialer.com/manuals/WD_UserManual-chunked/ar01s08.html for an API reference.
I'm able to create an event via the Facebook Graph API but I have yet to see a way in which to invite users to that event.
My fallback is to simply use the old REST API but sooner or later that will be phased out so I wanted to see if anyone had any suggestions.
--
Additional side question:
While using the REST API (or possibly even the Graph API) I have not found a way to invite guests who are not on Facebook. Is there a way to do this?
--
Thanks in advance for your help.
The bad news is that I think you're stuck with the REST API, at least I couldn't find another way (see http://bugs.developers.facebook.net/show_bug.cgi?id=10070 if you haven't already). The good news is that there's still so much functionality missing from the graph API that I'm pretty sure Facebook isn't going to be phasing it out any time soon. Very frustrating though...
can I use the JavaScript SDK to call the old REST API method ?
JS SDK
I have a rails application running on a Linux server. I would like to interact with Outlook/Exchange 2003 appointments from the rails application. For example, certain actions should trigger sending an appointment, and then preferably accepting/canceling the appointment in Outlook should trigger events in the application.
Failing this, is it possible to publish calendars that Outlook 2003 can read without requiring Outlook plugins? I note that Outlook 2003 does not support ical without plugins for example. Similarly, if this is not easily doable in Ruby, but is in another language (such as Perl for example) running on Linux then those suggestions would be welcome.
Any advice on how to achieve this, or where to start looking for answers would be gratefully received.
Outlook appointments are just e-mails with special header information. There's some information in this tutorial on the required parts. I sent a few meeting invites from my Outlook to my Gmail account and took a look at the raw headers there - you can figure most of the protocol out from that.
The iCalendar specs may help you, as well.
Thanks for everyones help. I found something that showed me how to do this with Perl, and ported it over to ruby. I've blogged about it for those looking for a solution
If you can upgrade to Exchange 2007, you can use Exchange Web Services that is more powerful and convenient to use than WebDAV.
At work, I inherited a Rails app that allow users to create single appointments. I was asked to write code to link those appointments in the app to users' outlook calendars, so that they are always in sync. Sounds to me very similar to what you want to do.
I don't think I'm allowed to publish the exact code I wrote though. Anyway I'll give you a bit idea on how I addressed it.
Exchange Web Services only provide API in C# (no surprise, it's Microsoft. Technically, you can use other languages since it's actually SOAP.). I wrote a middleware in C# that does the sync between Exchange server and the Rails app. When users do scheduling in the app, changes are sent to the middleware so changes can be reflected to their outlook calendars. Meanwhile, the middleware registers Push Notification subscriptions for all users -- every time changes are made in Outlook, the middleware will be immediately notified, which in turn faithfully reflect those changes in the app as well. Of course, recurring appointments are also supported.
Hope that helps you.
Take a look at the project RExchange on github.
For accessing appointments, you can just access the Calendar folder on Exchange using WebDav. For creating appointments, please refer to RFC2445 for details.
Further to ceejayoz's comment, you can also use ActionMailer to catch the replies that are sent back, and act on them - you'll need some form of unique id in a place that will be included in the reply though.