G'day All,

I am in the processing of implementing OAuth for the API. The first stage of the process was to refactor the API to make it possible to implement OAuth, as part of these changes I have done a lot of optimisation and implemented a few features that people having been asking for. So I am rolling this version out as a soft release, the released and beta api versions aren't going to change at this point as there is still quite a bit of work to complete the OAuth implementation.

Here's a list of changes in no particular order...

• Pretty mode: Adding &Pretty=1 to the request returns readable json responses.

• Boolean parameters: Boolean parameters can now be sent as either 0|1 or true|false.

• Strict mode: A number of people complained about calls like smugmug.albums.get returning an error response when there are no albums. By default now, empty elements (albums, images, subcats, watermarks, etc) are returned. To invoke an error like previously, add &Strict=1 to the request. This feature also works for methods like smugmug.albums.changeSettings where saving the same parameters resulted in an error.

• ThemeID: ThemeID can now be set for smugmug.albums.create and smugmug.albums.changeSettings, and is returned by smugmug.albums.getInfo and smugmug.albums.get with Heavy=1.

• Build your own heavy response: I have had a ton of requests by different people to add different bits and pieces to the standard non-heavy response for methods like smugmug.albums.get, smugmug.users.getTree or smugmug.images.get. I have added a new feature that lets you build your own heavy response and only return the info you want. To do this add &Extras to your requests and then comma-seperate the additional parameters you want returned.

eg. ....method=smugmug.albums.get&Extras=LastUpdated,G eography

• Previously, a number of parameters returned by smugmug.images.getInfo or smugmug.albums.getInfo were returned only for the owner scope. However, a number of these parameters were able to be determined by a logged out user of the site. As a result, what is returned now by those methods is more in line with what is available on the site.

Caveats:

• XML-RPC requests: All XML-RPC requests need to be sent as structs for api version 1.2.2 onwards. Altenatively, I have implemented it so that XML-RPC works with a standard GET request like the other API types. eg. http://api.smugmug.com/services/api/...SessionID=xxxx

• Stats methods: I haven't had a chance to rewrite the Stats methods yet, so they currenly return "System Error (Not Implemented yet)".

• Image/Album Key: This version of the API has the stage 3 security features implemented.

I imagine there are going to be some bugs, just let me know.

Cheers,

David

Wow, this is a real improvment! I can't wait (and won't) to start testing this!

Originally Posted by devbobo G'day All, <snip> Build your own heavy response: I have had a ton of requests by different people to add different bits and pieces to the standard non-heavy response for methods like smugmug.albums.get, smugmug.users.getTree or smugmug.images.get. I have added a new feature that lets you build your own heavy response and only return the info you want. To do this add &Extras to your requests and then comma-seperate the additional parameters you want returned. Previously, a number of parameters returned by smugmug.images.getInfo or smugmug.albums.getInfo were returned only for the owner scope. However, a number of these parameters were able to be determined by a logged out user of the site. As a result, what is returned now by those methods is more in line with what is available on the site. <snip>

This sounds great. Thanks for implementing our requests.

Does version 1.2.2 also have all of the methods listed in the 1.2.1 wiki implemented?: http://wiki.smugmug.com/display/SmugMug/1.2.1

Thanks for all your work on this

Originally Posted by David PL This sounds great. Thanks for implementing our requests. Does version 1.2.2 also have all of the methods listed in the 1.2.1 wiki implemented?: http://wiki.smugmug.com/display/SmugMug/1.2.1 Thanks for all your work on this

David,

yes, except for all the communitiy methods (i believe)

Originally Posted by devbobo G'day All, Boolean parameters Strict mode Build your own heavy response

Great! These new features and flexibility are a nice improvement. Thanks!

Dumb question... pretty and strict... do they accept true/false and 1/0 ?

Shan

Hi!
The smugmug.friend.get method returns this:
{"stat":"fail","code":3,"message":"invalid session"}

after this request (JSON):
method=smugmug.friends.get&SessionID=<sessionId>

The sessionID is just fine as I can add a friend w/o a hitch.
(using the 1.2.2 endpoint)

&&

In the watermark struct returned by watermarks.get the variable dissolve is returned as a string, maybe it should be returned as an int?
(JSON 1.2.2)

&&

The dgrinn documentation for watermak.create is wrong. int Dissolved should be int Dissolve

/Adam

Originally Posted by iotashan Dumb question... pretty and strict... do they accept true/false and 1/0 ? Shan

yes

Originally Posted by AdamN The smugmug.friend.get method returns this: {"stat":"fail","code":3,"message":"invalid session"}

fix internally

Originally Posted by AdamN In the watermark struct returned by watermarks.get the variable dissolve is returned as a string, maybe it should be returned as an int? (JSON 1.2.2)

yes, fixed internally

Originally Posted by AdamN The dgrinn documentation for watermak.create is wrong. int Dissolved should be int Dissolve

changed

Thanks

Ok, here goes:

Sharegroups.getInfo, create, results in "The remote server returned an error: (500) Internal Server Error"

Alsos theres a "waterwark" typo in smugmug.images.removeWaterwark
/Adam

Originally Posted by AdamN Ok, here goes: Sharegroups.getInfo, create, results in "The remote server returned an error: (500) Internal Server Error" Alsos theres a "waterwark" typo in smugmug.images.removeWaterwark /Adam

fixed (internally) and fixed

the above bug fixes should be live now

Originally Posted by devbobo ThemeID: ThemeID can now be set for smugmug.albums.create and smugmug.albums.changeSettings, and is returned by smugmug.albums.getInfo and smugmug.albums.get with Heavy=1.

How do you determine what the themeID is for a particular theme?

David

Originally Posted by DrDavid How do you determine what the themeID is for a particular theme? David

call smugmug.themes.get

Originally Posted by devbobo the above bug fixes should be live now

Sweet!

Ok...
Here goes!
smugmug.propricing.getPortfolio getAlbum, getImage w/o any optionals works just fine, but with a call like this:
"method=smugmug.propricing.getPortfolio&SessionID= e0d0da5a0bf9808fcc2ffb995392030a&ProductType=[\"CommonPrint\",\"Merchandise\",\"Download\"]"
you get an answer like this:
"{\"stat\":\"ok\",\"method\":\"smugmug.propricing. getPortfolio\"}" which is not as bad as an internal 500 but not quite as good as an array of products...
If you call it like this:
"method=smugmug.propricing.getPortfolio&SessionID= e0d0da5a0bf9808fcc2ffb995392030a&ProductID=[10040,10043,10048]"
or like this:
method=smugmug.propricing.getPortfolio&SessionID=e 0d0da5a0bf9808fcc2ffb995392030a&ProductType=[\"CommonPrint\",\"Merchandise\",\"Download\"]&ProductID=[10040,10043,10048]""
you get this:
{\"stat\":\"fail\",\"code\":16,\"message\":\"inval id data (no custom portfolio pricing set)\"}"
Which is not true...

Also a question.
The logout method returns an error when trying to logout a anonymous session. I understand the logic behind that but isn't actually good manners to tell the server that a session is to be considred expired instead of waiting for the session to timeout and die?

Originally Posted by AdamN Ok... Here goes! smugmug.propricing.getPortfolio getAlbum, getImage w/o any optionals works just fine, but with a call like this: "method=smugmug.propricing.getPortfolio&SessionID= e0d0da5a0bf9808fcc2ffb995392030a&ProductType=[\"CommonPrint\",\"Merchandise\",\"Download\"]" you get an answer like this: "{\"stat\":\"ok\",\"method\":\"smugmug.propricing. getPortfolio\"}" which is not as bad as an internal 500 but not quite as good as an array of products... If you call it like this: "method=smugmug.propricing.getPortfolio&SessionID= e0d0da5a0bf9808fcc2ffb995392030a&ProductID=[10040,10043,10048]" or like this: method=smugmug.propricing.getPortfolio&SessionID=e 0d0da5a0bf9808fcc2ffb995392030a&ProductType=[\"CommonPrint\",\"Merchandise\",\"Download\"]&ProductID=[10040,10043,10048]"" you get this: {\"stat\":\"fail\",\"code\":16,\"message\":\"inval id data (no custom portfolio pricing set)\"}" Which is not true... Also a question. The logout method returns an error when trying to logout a anonymous session. I understand the logic behind that but isn't actually good manners to tell the server that a session is to be considred expired instead of waiting for the session to timeout and die?

it does actually work, but you need to call it like this....

method=smugmug.propricing.getPortfolio&SessionID=e 0d0da5a0bf9808fcc2ffb995392030a&ProductType[]=CommonPrint&ProductType[]=Merchandise&ProductType[]=Downloads&ProductID[]=10040&ProductID[]=10043&ProductID[]=10048

Originally Posted by devbobo it does actually work, but you need to call it like this.... method=smugmug.propricing.getPortfolio&SessionID=e 0d0da5a0bf9808fcc2ffb995392030a&ProductType[]=CommonPrint&ProductType[]=Merchandise&ProductType[]=Downloads&ProductID[]=10040&ProductID[]=10043&ProductID[]=10048

Ok! Are you going to fix it to be more JSON-like, or is this how it should look?

/Adam

I've just noticed that the 1.2.2 albums.get() for anonymous calls don't return the same information as say earlier revs, eg 1.2.1.

I'm using the PHP endpoint.

eg. 1.2.1 anonymous albums.get(Heavy=FALSE):

Array
(
    [0] => Array
        (
            [id] => 4644971
            [Key] => vwxmf
            [Title] => Photo of the Week
            [Category] => Array
                (
                    [id] => 0
                    [Name] => Other
                )

            [ImageCount] => 5
            [Public] => 1
            [Passworded] => 
        )

    [1] => Array
[...]

eg. 1.2.2 anonymous albums.get(Heavy=FALSE):

Array
(
    [0] => Array
        (
            [id] => 4644971
            [Key] => vwxmf
            [Category] => Array
                (
                    [id] => 0
                    [Name] => Other
                )

        )

    [1] => Array
[...]

In fact, even using Heavy=TRUE doesn't return the album Title when logged in anonymously.

I've not tested any other methods yet, but as soon as I notice more diffs, I'll let you know.

something odd there...i'll check it out.

Originally Posted by lildude I've just noticed that the 1.2.2 albums.get() for anonymous calls don't return the same information as say earlier revs, eg 1.2.1. I'm using the PHP endpoint. eg. 1.2.1 anonymous albums.get(Heavy=FALSE): Array ( [0] => Array ( [id] => 4644971 [Key] => vwxmf [Title] => Photo of the Week [Category] => Array ( [id] => 0 [Name] => Other ) [ImageCount] => 5 [Public] => 1 [Passworded] => ) [1] => Array [...] eg. 1.2.2 anonymous albums.get(Heavy=FALSE): Array ( [0] => Array ( [id] => 4644971 [Key] => vwxmf [Category] => Array ( [id] => 0 [Name] => Other ) ) [1] => Array [...] In fact, even using Heavy=TRUE doesn't return the album Title when logged in anonymously. I've not tested any other methods yet, but as soon as I notice more diffs, I'll let you know.