Options

API Update - Printmarks (27th August 2010)

devbobodevbobo Registered Users, Retired Mod Posts: 4,339 SmugMug Employee
edited August 29, 2010 in SmugMug API Support & Integrations
G'day Guys,

Tonight we shipped a new pro feature Printmarks.

API 1.2.2 has been updated to support this new feature, new methods...

- smugmug.printmarks.create
- smugmug.printmarks.delete
- smugmug.printmarks.get
- smugmug.printmarks.getInfo
- smugmug.printmarks.modify

The following methods have also been updated to accept a PrintmarkID parameter..
- smugmug.albums.create
- smugmug.albums.changeSettings

For more info, check out the API documentation.

Cheers,

David
David Parry
SmugMug API Developer
My Photos

Comments

  • Options
    test.iwavetest.iwave Registered Users Posts: 3 Beginner grinner
    edited August 27, 2010
    How do i get "sessionid" in smugmug
    How do i get "sessionid" in smugmug
  • Options
    jfriendjfriend Registered Users Posts: 8,097 Major grins
    edited August 28, 2010
    test.iwave wrote: »
    How do i get "sessionid" in smugmug
    See the loginWithPassword command or any of the other ways to login that return a session.
    --John
    Homepage • Popular
    JFriend's javascript customizations • Secrets for getting fast answers on Dgrin
     Always include a link to your site when posting a question
  • Options
    lildudelildude Registered Users Posts: 70 Big grins
    edited August 29, 2010
    Ermmm, I think I've noticed an undocumented change to the API with this update, or more specifically the method the API uses to generate the HMAC-SHA1 OAuth signature.

    It seems as of this update, the signature calculation performed by the API expects FALSE values to be a numerical 0 when calculating the signature when previously a blank was acceptable.

    Is this correct and expected?
    Colin Seymour
    Personal Blog | Tech Blog | phpSmug
  • Options
    devbobodevbobo Registered Users, Retired Mod Posts: 4,339 SmugMug Employee
    edited August 29, 2010
    lildude wrote: »
    Ermmm, I think I've noticed an undocumented change to the API with this update, or more specifically the method the API uses to generate the HMAC-SHA1 OAuth signature.

    It seems as of this update, the signature calculation performed by the API expects FALSE values to be a numerical 0 when calculating the signature when previously a blank was acceptable.

    Is this correct and expected?

    Hey Colin,

    Nothing in that area has changed recently, can you please email me some more detailed info.

    Thanks,

    David
    David Parry
    SmugMug API Developer
    My Photos
Sign In or Register to comment.