There's so much potential with this module, yet it's so incredibly frustrating to dig through partial examples that do random stuff but leave out all the interesting parts.

Code examples are nice, but they're of very little use for people who are using languages other than the ones in the examples. I'd like to see the actual request that's being sent, so I can match up what my code is producing. Trial and error is no fun when hashes are involved.

Also, none of the examples use API keys. There are examples that use login, and the 6.x-3.x one that uses OAuth, but what about API keys? I don't need a login, but I want to use an API key. Can somebody who has successfully done this write up a brief example?

I'll be happy to contribute to that once I get stuff running. But until then, I need your help.

Comments

gdd’s picture

There is a very detailed example I wrote write here

http://drupal.org/node/394224

It is for Drupal -> Drupal communication, but it should be easily translated into your language of choice. All you really need is

1) A timestamp
2) A random string
3) The ability to make a sha256 hash

It should be pretty easy to put together.

bsenftner’s picture

I just added this documentation page:

Services 6.x-2.0 PHP xmlrpc example with api key
http://drupal.org/node/774298

yajnin’s picture

I've added info to the Services Version 6.2 area. It is written in JavaScript -- but the information contained will help anyone in any language.

At the least it is clear. And I've taken time to label fields descriptively.

General knowledge that will apply to any language:

- - Node Object structure
- - CCK Field Array/Object structure
- - Structure of the data call

//

I'll try and document my findings regarding content access control. And Drupal permissions. As I have time.

Perhaps by the end of my process (it'll be weeks to months) it'll all equate to a big top-down tutorial.

The work here is a start:

// See JavaScript entries

http://drupal.org/node/762088

gdd’s picture

Version: 6.x-2.0-beta1 » 6.x-3.x-dev
Status: Active » Fixed

I have also added reasonably complete examples for Services 3.x in the handbook. If anyone wants additional work done please create a new documentation issue with specific requests.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.