iPrice RESTful API Generator for October CMS

Generate secure RESTful APIs for your models.

---

Features

JWT-Based Authentication

• Choose to secure your resource endpoints with JWT-based authentication or not.

Resource Relationship Eager-loading

• Set which relationships should always be eager-loaded on GET requests. Visit the October CMS Database Relationships on how to set-up relationships.

GET

• Get a collection of resources.
• Get a single resource.
• Filter by column using query parameters or route parameters.
• Paginate using the page query parameter with configurable limit query parameter.

POST

• Create a resource.

PUT

• Update a resource.

DELETE

• Delete a resource.

---

Usage

Creating/editing a resource endpoint

The resource form has the following fields:

• Base Endpoint (required): the base url of the endpoint you want to create. Examples are api/v1/blogs, api/v1/{category}/blogs. You can have a route parameter as in the example ({category}) but make sure the parameter name is an actual field in your resource table and resource name (blogs) is placed at the end.
• Model Class (required): the Eloquent model class you want to expose in the API as a resource.
• Eager Load Relationships: the relationships specified in your Eloquent model class you want to eager-load on every GET request.
• Require Authentication: check this if you want to protect your resource API with JWT-based authentication.

Using your resource API

GET requests

To request a collection, do something like the following:

# Basic collection
GET example.com/api/v1/blogs

# Filtered collection.
# note: you can use any fields from the resource as filter
# and you can use as many filters as you want.
GET example.com/api/v1/blogs/?category=tech

# Filtering with operator
# You can use operator in filtering requests
# by indicating the field that you want to filter,
# the operator and the value

# Get collection where views > 10
GET example.com/api/v1/blogs/?views[gt]=10

# Get collection where id not equal to 2
GET example.com/api/v1/blogs/?id[neq]=2

# Get collection where id is between 2 and 200
GET example.com/api/v1/blogs/?id[gte]=2&id[lte]=200

# Supporting operators:
## 'gte': greater than and equal (>=)
## 'gt': greater than (>)
## 'lte': less than and equal (<=)
## 'lt': less than (<)
## 'eq': equal to (=) - used as default if not specified
## 'neq': not equal to (<>)
## 'contains': contains sub-string (like)

By default, the API will return the first 10 results. If you want to get the next batch or return more than the default limit, you can use the page and/or limit query parameters like the following:

# Get the first 20 results.
GET example.com/api/v1/blogs/?limit=20

# Get the next 20 results.
GET example.com/api/v1/blogs/?page=2&limit=20

# You can use the `page` and `limit` query parameters
# along with any filters you need.
# Filter by category and get the results from page 2.
GET example.com/api/v1/blogs/?category=tech&page=2

If you specified a route parameter in your endpoint, eg: api/v1/{category}/blogs, you need to specify a value in place of the route parameter:

GET example.com/api/v1/tech/blogs

You can still use pagination and filters along with route parameters.

To get a single resource, specify the resource ID after the base endpoint:

GET example.com/api/v1/blogs/1
GET example.com/api/v1/tech/blogs/1

To sort your results, use sort as a query parameter. The values of sort parameter is an array with sort_field as a key and sort_order as value. If sort_order is not specified, the default sort order asc will be used

# Sort results by position - from the first to the last (ascending)
GET example.com/api/v1/blogs/?sort[position]=asc

# Sort results by created_at - from the newest to the oldest (descending)
GET example.com/api/v1/blogs/?sort[created_at]=desc

# Sort results by position - from the first to the last. If there are records with the same position, sort by created_at - from the newest to the oldest
GET example.com/api/v1/blogs/?sort[position]=asc&sort[created_at]=desc

The order of sort criteria in the query string will be preserved.

PUT requests

You can update a resource by doing a PUT request to a specific resource with a payload:

PUT example.com/api/v1/blogs/1 -H 'content-type:appilcation/json' -d '{"title":"Updated blog title"}'

DELETE requests

You can delete a resource by doing a DELETE request to a specific resource:

DELETE example.com/api/v1/blogs/1

Authentication

If you chose to protect your API endpoints with authentication, you need to acquire a token by logging in and use that token on every API request you make.

To manage API users, please refer to RainLab User plugin.

To log in, make a POST request to the api/auth/login endpoint with a login and password payload:

# Acquire a token (login)
POST example.com/api/auth/login -H 'content-type:application/json' -d '{"login":"[email protected]","password":"password123"}'

If successful, it will return something like the following:

{
    "token": "some.jw.token",
    ...
}

Use the value of the token field as a bearer token in the header or as a token query parameter:

# As a header
GET example.com/api/v1/blogs -H 'authorization: bearer some.jw.token'

# As a query parameter
GET example.com/api/v1/blogs/?token=some.jw.token