API Changes

An iPhone client for Growl available on the App Store.
User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Tue Jul 20, 2010 4:05 am

Fixed content-type from text/html to text/xml in API responses.

Two new API fields to be added soon with new Prowl version, stay tuned.

User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Sat Jan 22, 2011 4:55 pm

Removed SSL requirement on the API. It's still strongly recommended, but not required. Please use SSL unless you absolutely cannot.

User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Mon Jan 24, 2011 5:08 am

Users are now able to generate multiple API keys, lessening the burden. Still thinking about OAuth or a fetch-an-API-key solution for third-party providers.

User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Fri Jan 28, 2011 6:42 pm

Added 'url' parameter a few days ago with the 1.2.1 release. The parameter has a maximum length of 512, and will be offered to the user as a redirect option when the notification is opened, as well as provide the redirect disclosure button (>) in the notification list.

User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Sun Jan 30, 2011 5:40 am

New API methods: retrieve/token and retrieve/apikey. Added changes to the main API page, and added ability to manage providerkeys through your account, including making them on the fly.

slashk
Harmless
Posts: 3
Joined: Fri Sep 03, 2010 6:48 pm

Wrong Return Codes for retrieve/token

Postby slashk » Sun Mar 20, 2011 9:36 pm

In version 1.2 of the API, you say that "A success will return the following format, as well as the HTTP status code 200", but when I do this for retrieve/token I get a zero status code with success. here is the results:

Code: Select all

<prowl>
   <success code='0' remaining='999' resetdate='1300659778'/>
   <retrieve token='b7b1e4fbcee10334058d94a3162b04e5f56f074b' url='https://www.prowlapp.com/retrieve.php?token=b7b1e4fbcee10334058d94a3162b04e5f56f074b'/>
</prowl>


It appears to be a correct call, but it returns a zero success code. is this an error ?

User avatar
zac
Cocoaforge Admin
Posts: 1518
Joined: Sun Mar 27, 2005 3:19 pm
Contact:

Re: API Changes

Postby zac » Sun Mar 20, 2011 10:07 pm

Good catch, fixed. retrieve/token now returns 200 instead of the incorrect 0.

slashk
Harmless
Posts: 3
Joined: Fri Sep 03, 2010 6:48 pm

Re: API Changes

Postby slashk » Sun Mar 20, 2011 10:45 pm

zac wrote:Good catch, fixed. retrieve/token now returns 200 instead of the incorrect 0.


Thanks for the quick correction !
Just finishing my updates to prowly (ruby gem) to support API version 1.2
cheers
/k

User avatar
xenji
Harmless
Posts: 1
Joined: Mon May 09, 2011 9:12 am
Location: Duesseldorf, Germany
Contact:

Re: API Changes

Postby xenji » Mon May 09, 2011 9:19 am

I've updated the PHP library to match the API v1.2 requirements. Please notice that from version 1.0.0 on only PHP 5.3 will be supported.

Get the library at https://github.com/xenji/ProwlPHP
Get the API docs at http://xenji.github.com/ProwlPHP/
Maintainer of ProwlPHP https://github.com/xenji/ProwlPHP


Return to “Prowl”

Who is online

Users browsing this forum: No registered users