# Introduction

The Onehub API enables developers to access data from the Onehub Service on behalf of a client. The API is organized around [REST](http://en.wikipedia.org/wiki/Representational_state_transfer). Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. Where appropriate, the API provides the four basic functions of persistent storage — **create**, **read**, **update**, and **delete**. In general, most API resources will accept an `index` request and return a [paginated](https://developer.onehub.com/api/pagination) set of all available items.