I'd recommend reading about REST, it's pretty much the de-facto standard for web API implementations these days. Using this scheme, anyone implementing a client for your API will already know where they are at.
The HTTP verbs / URLs would look something like: # Returns a list of all prints (may not be applicable for you) GET /prints # Return a single print, where 123 is your unique ID GET /prints/123 # Create a new print POST /prints # Update an existing print PUT /prints/123 # Delete a print DELETE /prints/123 This leverages HTTP in the way it was designed to be used. Malc On Feb 7, 1:38 pm, Jmumby <[email protected]> wrote: > Hi, Just starting out on a API for a remote printing system. It can be > found herehttp://smartorder.co.nz/apidocs.phplooking for suggestions > or feedback on what I have done so far. > > Cheers. -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
