Why REST?

Why REST?

Representational State Transfer (REST) is a distinct way of architecting software for communication and data transfer between distributed systems.

REST-style communication typically includes a client-to-server relationship where the client initiates a request to the server, which processes that request and returns a response. Requests and responses are built around the transfer of representations of resources—for example, an SMS message or a menu item selected by a caller. That representation is typically a document that captures the current or intended state of the resource. Clients can build and modify resources, while servers store, manage and distribute them.


Diagram showing client request to the Phon.com API server

Phone.com chose REST because it offers you a familiar and secure method of communicating with our API. The REST protocol fits naturally on top of HTTP, allowing developers to choose from a wide variety of HTTP communication libraries (like cURL), programming languages, and virtually any modern operating system or platform.

Also, REST allows us to represent non-standard resources (like a phone call or an SMS message) in the same way we represent more typical resources (like call logs, menus and audio files), providing a predictable pattern for usage and management.

Learn More:

Phone.com API Topics:

Tutorials on External Sites:

Introductory:

More Advanced: