I don't think there is. The sole purpose of a resource is to represent a single Model and provide CRUD operations for it. If this is a must have in your case, first thing that comes to mind would be to have a view in your database that combines the two tables. This way you can have a model that represents the view and a resource for said model. You can always customize the create/update action of the form so you can split the form data into two separate models.