Tech stuff, API and programming

Hi Magnatronus,

I'm using a dirty Python script to upload photos from my Linux desktop. It's not finished but "Works For Me"; here it is.

Actualy it gets authentication data from a file '$HOME/.upload23', wich contains:

# -----------------------------------
[auth]
api_key=DEMO
username=magnatronus
password=verysecret
# -----------------------------------

Take a look at the services_upload() function, who's really doing the job.

There's also a curl-upload explanation on the 23 Blog, a really nice starting point.

Not problems as such. But the examples use the username and password login. I am trying to do this by using the AuthCode( as per Flickr). so some examples of this would be great.

- thanks.

OK, this works for me:

a) Request a frob
Macintosh:~/ comp$ curl -F api_key=23demo -F method=auth.getFrob http://www.23hq.com/services/rest/


MYFROB


b) Validate frob by going to:
http://www.23hq.com/services/auth/?api_key=23demo&frob=MYFROB


c)
Macintosh:~/ comp$ curl -F api_key=23demo -F method=auth.getToken -F frob=MYFROB http://www.23hq.com/services/rest/



MYTOKEN
delete





d) Upload the photo
Macintosh:~/ comp$ curl -F api_key=23demo -F auth_token=MYTOKEN -F photo=@myphoto.jpg http://www.23hq.com/services/upload/


426294

well I am still getting the "Login failed / Invalid auth token" error when trying to upload an image. I an using java( btw the routines work fine with Flickr). I have redirected the post that is done to a local server so I can get a copy of the output which is included here:

POST /services/upload HTTP/1.1
Content-Type: multipart/form-data; boundary=---------------------------7d42082230740
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.4.2_05
Host: www.23hq.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 24530
-----------------------------7d42082230740
Content-Disposition: form-data; name="photo"; filename="grumpyas.jpg"
Content-Type: image/jpeg

[data here is the image data - removed for clarity]

-----------------------------7d42082230740
Content-Disposition: form-data; name="auth_token"
EB_MY_AUTH_TOKEN
-----------------------------7d42082230740
Content-Disposition: form-data; name="api_key"
MY_API_KEY
-----------------------------7d42082230740--


The auth key is not the problem as I also have an addtags function and if I manually upload an image then use the addtags method it works fine. So basically it is just the upload that gives me the error - any ideas???

First, try posting to "/services/upload/" rather than merely "/services/upload" -- it's unlikely that it changes anything, but it may...
Otherwise, please send me the full request including the "real" token to steffen@23hq.com (if you're unsure about that, remove the last five or six chars from the token, I'll look the full token it up in the db)

/Stc

The bug in setMeta has been resolved now. I'll be back to do the rss thingy after the weekend.

Hi Adam,

I'm on my way out for the weekend, but I wanted to give you an answer to some of your questions right away:

a) The parameter is "is_public" rather than "ispublic", and it works okay for me at the moment?

b) Yeah, you're right. I've allowed html for the moment, but I'll be back on Monday to do a cleanup, which will return errors in XML.

c) Basically, we're allowing everything apart from a "$" and {[]}. We have been looking at doing comparisons and other stuff by stripping some chars and making them "raw tags", but it's not implemented at the moment.

d) I'll look into this. For this purpose, we'll do it the way Flickr is doing it -- that should solve any unexpected behaviour, right?

e) This seems weird, and it certainly isn't by design. Once again, I'll be back to change this either tomorrow or on Monday.

With regard to tag searching and partial/mixed case matches, the discussion has been moved here:
http://www.23hq.com/forums/message-view?message_id=429648