No ReST-ing for the Esendex Development Team ...or is there?

The Esendex Development team waits for no-one. Having released two new services (BlogIt and Voice SMS) very recently we are also working hard on a completely new API for the Esendex developer community.

We have made the decision to create the new API as a ReST (Representational State Transfer) web service. With ReST, the idea is that the services are comprised of resources (an item of interest). Calls to ReST services return a representation of a resource placing the client application in a state. Typically a resource provides access to other resources via links. The client uses these links when working with resources, placing the client application in another state, hence the name Representational State Transfer.

ReST is an architectural style, rather than a standard (although it works with recognised standards such as HTTP). This means we not only needs to make key decisions on entities to expose but other key decisions for providing a great, new and exciting API for our customers. Keep posted to find out about our new API work in the coming weeks.