Comments on: Snipplr API

By: Ian Lewis

Ian Lewis — Sat, 09 Aug 2008 03:55:25 +0000

snippet.list started returning multiple results for a single snippet.

For instance I searched my own snippets for one matching “mail” and got 7 results for only 2 matched snippets. 3 are for one snippet and 4 for another.

check_email_address() email validator
check_email_address() email validator
check_email_address() email validator
Send multi-part encoded mail with attachments
Send multi-part encoded mail with attachments
Send multi-part encoded mail with attachments
Send multi-part encoded mail with attachments

By: Matt Hobbs (1man)

Matt Hobbs (1man) — Mon, 19 May 2008 20:12:38 +0000

Hi Tyler,
Is the server capable of outputting in JSON? Or would it be able to add the function?

By: Jason Tan

Jason Tan — Thu, 01 May 2008 21:57:30 +0000

@bela - I just fixed the snippet.delete method to return the correct code (1 on successful deletion, 0 otherwise)

By: Tenzer

Tenzer — Mon, 10 Mar 2008 23:01:25 +0000

A little more testing shows that if you just use the HTTP 1.1 standard instead of HTTP 1.0, there is no problems with the 301 error.

By: Tenzer

Tenzer — Mon, 10 Mar 2008 22:46:42 +0000

I think I found the cause of the issue Avinash described almost a year ago, since I also have experienced the same issue.

The error message comes when the URL for the server is sent as “http://snipplr.com:80/xml-rpc.php”, which includes the port number. Then a 301 HTTP error message is sent back redirecting to “http://snipplr.com/xml-rpc.php”.

Unfortunately it seems that some XML-RPC libraries always includes the port number in the URL, which makes them unusable together with your API.

Could the redirect system maybe be blacklisted from the xml-rpc.php file?

By: bela

bela — Tue, 23 Oct 2007 17:18:01 +0000

snippet.delete appears to return 0 whether or not the snippet was actually deleted.

That is, when a snippet is successfully deleted (no longer appears with snippet.list) the response is 0.
If snippet.delete is then called on the same snippet_id, the response is the same.

By: maid450

maid450 — Mon, 10 Sep 2007 14:45:09 +0000

something I think would be great is a “tags.list” or something method that returns a list of all different tags of your snippets

By: Ian Lewis

Ian Lewis — Sun, 15 Jul 2007 14:19:39 +0000

@ Tyler

Perfect. That’s exactly the info I was looking for. Thanks.

By: Tyler

Tyler — Mon, 02 Jul 2007 15:04:59 +0000

@ Ian Lews - It shouldn’t be too hard to detect the error. The API returns a faultCode of “1″ and a faultString that says ” No snippets found with tags = ””. Other error codes are:

1 - No snippets found
2 - No snippet found (when search for snippet by ID)
3 - Incorrect API key
4 - Requested method name not found

By: Ian Lewis

Ian Lewis — Mon, 02 Jul 2007 14:16:30 +0000

I’m making a Snipplr plugin for the jEdit text editor. Is there a reason why the snippet.list sends an error response when there are no snippets returned by the query? It’s hard to tell on the client side the difference between a real XML-RPC error and an error resulting from a query that has no results.