BIG changes! Here are the highlights:

- method names have dramatically changed. The old methods will still work, and probably will forever, but no promises. I strongly suggest you start using the new naming scheme. See the docs.

- new interface! REST! Some would argue it's even simpler than XML-RPC, and they might be right. See the docs.

- APIKeys! To curb abuse and increase our ability to track API usage, all uses of the API now require an API key. Easy to apply for, quick to obtain, you'll need it to use any of the new functions, new REST interface, etc. See the docs.

- New methods to let you manipulate Categories & SubCategories: rename, delete, etc.

- Stats methods to get hits and bytes sent per album and per photo.

- Bug fixes to quite a few methods to return the proper values (ints, bools, etc) and results.

I'm sure I've introduced bugs, so holler if you find some.

Don

Don,

smugmug.images.get & smugmug.albumtemplates.get are returning method not found


David

Originally Posted by onethumb BIG changes! Here are the highlights: - method names have dramatically changed. The old methods will still work, and probably will forever, but no promises. I strongly suggest you start using the new naming scheme. See the docs. - new interface! REST! Some would argue it's even simpler than XML-RPC, and they might be right. See the docs. - APIKeys! To curb abuse and increase our ability to track API usage, all uses of the API now require an API key. Easy to apply for, quick to obtain, you'll need it to use any of the new functions, new REST interface, etc. See the docs. - New methods to let you manipulate Categories & SubCategories: rename, delete, etc. - Stats methods to get hits and bytes sent per album and per photo. - Bug fixes to quite a few methods to return the proper values (ints, bools, etc) and results. I'm sure I've introduced bugs, so holler if you find some. Don

Are you planning on maintaining xml-rpc as well as rest? I hope so. Python support of xml-rpc is first class, but not so for rest.

Don, I think it would be really great when you have a change like this that is going to break everything, to publish the documentation, changes, etc, in advance and give us some time to get ready. Please?

Originally Posted by rutt Don, I think it would be really great when you have a change like this that is going to break everything, to publish the documentation, changes, etc, in advance and give us some time to get ready. Please?

I agree -- I first noticed my PHP script returning an error and dug through the code for a bit before I came here to read about the API changes. A simple "the API will be changing" heads-up would have been helpful, even without other details. Perhaps a 1 week "grace period" where API calls work without keys would have been helpful.

As long as the old functionality keeps working "as is", at least for the time being, I'm all up for the changes!

I agree, sort of advance notice would be nice, but hey, sometimes $%it just happens:-)

I'l looking forward to see the REST:-)

One question: is your intension to
1) support/uprdage *both* branches (rpx-aml & rest),
or
2) the rpc-xml gets to rest:-) and REST will be the "main" API?

Thanks again for keep an eye of this area!

Originally Posted by Nikolai As long as the old functionality keeps working "as is", at least for the time being, I'm all up for the changes!

I agree, but the old functionality isn't working "as is" -- I don't have an API Key yet and my scripts using the old API calls are failing due to 'invalid API key'.
Oh well - I'm sure once I get the API Key things will work very well. I think it's great that Don and the rest of the crew are so actively trying to make the API a useful and powerful tool.

Originally Posted by rutt Are you planning on maintaining xml-rpc as well as rest? I hope so. Python support of xml-rpc is first class, but not so for rest. Don, I think it would be really great when you have a change like this that is going to break everything, to publish the documentation, changes, etc, in advance and give us some time to get ready. Please?

I did rigorous backwards compatibility testing so I really shouldn't have "broken everything".

Note what's not working that used to work and I'll get it fixed.

Don

Originally Posted by CSwinton I agree -- I first noticed my PHP script returning an error and dug through the code for a bit before I came here to read about the API changes. A simple "the API will be changing" heads-up would have been helpful, even without other details. Perhaps a 1 week "grace period" where API calls work without keys would have been helpful.

All existing functionality continues to work, without Keys.

Come on guys, I'm not that stupid. There's a huge grace period where all the old calls work, there's no key required for anything that was old, etc etc.

If something's not working, it's an honest mistake and a bug, not intentional. Tell me which call isn't working, rather than complaining with zero details. :)

Don

Obviously, the docs aren't clear enough, though it seems like it to me. :)

For the record: Both REST and XML-RPC will be jointly updated in lockstep. XML-RPC isn't going anywhere.

Of course, also for the record, the APIs are currently sans official support or endorsement. Use at your own risk. ;)

Don

Originally Posted by onethumb All existing functionality continues to work, without Keys. Come on guys, I'm not that stupid. There's a huge grace period where all the old calls work, there's no key required for anything that was old, etc etc. If something's not working, it's an honest mistake and a bug, not intentional. Tell me which call isn't working, rather than complaining with zero details. :) Don

Sorry. Zero details is right. I didn't even test. I just read what you wrote and assumed that you were announcing that it wasn't going to work. Sorry if I read it wrong, but it wasn't 100% clear and I didn't sleep so great last night anyway.

I'll test and let you know.

Originally Posted by devbobo Don, smugmug.images.get & smugmug.albumtemplates.get are returning method not found David

Silly typos. I assume you were talking about the XML-RPC interface?

Try now. :)

Don

Originally Posted by onethumb BIG changes! Here are the highlights:

Oh, yeah, and the API endpoints changed again. Just to be clear, the old endpoints still work and should continue to work for a long long time, but I'd shift to using the new ones (which are permanent, now, I promise!) for all future work.

Don

Smugmug.py does seem to work. Next time I'll try to be more empirical. Sorry.

Thanks, Don, for all the work on this. It really is a pleasure to have this interface.

Originally Posted by onethumb All existing functionality continues to work, without Keys. Come on guys, I'm not that stupid. There's a huge grace period where all the old calls work, there's no key required for anything that was old, etc etc. If something's not working, it's an honest mistake and a bug, not intentional. Tell me which call isn't working, rather than complaining with zero details. :) Don

If I thought you were stupid would I be paying you money? Sorry for the lack of details. I have a PHP script and am using XMP_RPC (with old API for the moment). "loginWithPassword" fails due to 'invalid API key'. Using the API key I just received, it works perfectly. Any idea why the old call with the API key would fail? I'm not sure (being new to this) which other details would be helpful - please let me know what else you need.

Originally Posted by CSwinton If I thought you were stupid would I be paying you money? Sorry for the lack of details. I have a PHP script and am using XMP_RPC (with old API for the moment). "loginWithPassword" fails due to 'invalid API key'. Using the API key I just received, it works perfectly. Any idea why the old call with the API key would fail? I'm not sure (being new to this) which other details would be helpful - please let me know what else you need.

The API key for XML-RPC should only kick in if you're sending a Version that's equal to or greater than "1.1.0".

What Version are you sending?

Don

Originally Posted by onethumb The API key for XML-RPC should only kick in if you're sending a Version that's equal to or greater than "1.1.0". What Version are you sending? Don

That was it - I was sending "1.1". Thanks for the quick replies and sorry for any confusion. I didn't think about version control in the API. That's what I get for posting messages on little sleep. Now I know.

Would there be any advantage, in PHP, to use the REST interface? The XML-RPC classes available for PHP seem to work well. Thanks.

Originally Posted by CSwinton I agree, but the old functionality isn't working "as is"

Works like a charm. no api key, no rest.
Prolly something on your side, my man!

Cheers!

Originally Posted by CSwinton That was it - I was sending "1.1". Thanks for the quick replies and sorry for any confusion. I didn't think about version control in the API. That's what I get for posting messages on little sleep. Now I know. Would there be any advantage, in PHP, to use the REST interface? The XML-RPC classes available for PHP seem to work well. Thanks.

Whew. Glad to hear. :)

The interfaces are essentially identical, so which one to use is left up to the author. Both interfaces are easy to use and lightweight (as opposed to SOAP), so you can't really go wrong with either one.

Don

Hi, I just got my API key and I'm trying to give the REST API a shot but so far I've had no luck, just a lot of invalid API key errors

As a quick check that it should be working, in my browser I've been trying to hit this URL:
https://api.smugmug.com/hack/rest/?m...RealAPIKeyHere
with or without SSL, the response is invalid API key. AFACT this should be just like the sample request in the docs. Does it work for anyone else? If so, what browser/OS are you using?

Originally Posted by dds Hi, I just got my API key and I'm trying to give the REST API a shot but so far I've had no luck, just a lot of invalid API key errors As a quick check that it should be working, in my browser I've been trying to hit this URL: https://api.smugmug.com/hack/rest/?m...RealAPIKeyHere with or without SSL, the response is invalid API key. AFACT this should be just like the sample request in the docs. Does it work for anyone else? If so, what browser/OS are you using?

Give it a shot now.

Don