Ruby Library for interacting with PivotalTracker API

The Shopify API gem allows Ruby developers to programmatically access the admin section of Shopify stores. The API is implemented as JSON or XML over HTTP using all four verbs (GET/POST/PUT/DELETE). Each resource, like Order, Product, or Collection, has its own URL and is manipulated in isolation.

Library for the Ruckus Wireless SPoT API

A ruote participant implementation using ActiveResource to notify RESTful interfaces about workitems.

future OOOR port for Tryton

Ruby wrapper to access salesforce rest api

Ruby library for working with Samba Videos data API

Samenessed provides access to the sameness service using simple object methods.

* This gem provides two executable binaries to interact with Mingle (http://mingle.thoughtworks.com/mingle-agile-project-management) through its API. It also has sample interactive Rake task on how to facilitate easy card movements when a card enters/exits the development queue. * mtx is a binary that facilities transition changes for use on rake tasks * minglr is a more interactive tool that provides a quick interface for many common uses

Provides a simple wrapper for creating, listing and reviewing Scripted.com Jobs and Pitches.

Ruby object based Sendle API wrapper.

Abstracts out and port to ruby the functionality of the shopify textmate bundle for use in other editors. Provides a shopify console with the ability to switch between configured shops, using either custom app or oauth token style authentication. Provides caches of objects and convenience methods for fetching them.

allow use of limit: false in api requests

A fast, parallel shopify api client using typhoeus/hydra. Attempts to balance being a good citizen about api limits and fetching multiple apai records in parallel.

Simple content service

Interact with SalesKing

gem to consume the api of our invoicing tool https://skippr.com

tools utilizing the slicehost api

Ruby libraries for Socialmod moderation service

SoftAttributes provides a consistent way to define "soft" attributes on ActiveSupport. Typically calculated (non-persisted) attributes would be termed soft attributes. These will be included in the xml/json payload for serialization, but will need to be discarded if they appear in the incoming request.