Skip to end of metadata
Go to start of metadata

API Builder 3.x is deprecated


Support for API Builder 3.x ceased on 30 April 2020. Use the v3 to v4 upgrade guide to migrate all your applications to API Builder 4.x.

Contact if you require migration assistance.


Composite models require the appc.composite connector to be installed. This comes by default with all API Builder Projects. If you are missing this connector you can learn how to install it here.

Create a composite model

Composite models allow you to create a single model that is composed of two or more models based on the same or different connectors. Composite models can be joined together via a common set of properties, such as primary keys or foreign keys, or they can have no properties in common at all. The power of composite models is that you can represent multiple data sources and entities as a single API endpoint, which is ideal for many mobile use cases.

To create a composite model, follow the same procedure when creating a regular model except the connector property must be set to appc.composite, each field in the definition object must specify the model property to indicate which model the field originates from, and the metadata property must define the join operation to combine the models or leave it undefined to perform no join operations.

The composite connector can either perform a left join or inner join:

  • left join: all records from the main model are returned regardless if it found a match in the secondary models
  • inner join: only records that match both models are returned

The composite connector can also perform either a one-to-one join or one-to-many join:

  • one-to-one: only one record from the secondary model matches a record in the main model
  • one-to-many: multiple records from the secondary model can match a record in the main model

To define the join operation, set the metadata property to either the left_join key or inner_join key, either of which takes an array of objects defining the join. Each object in the left_join or inner_join property defines the model to join (model property), a key to join (join_properties property), and optionally if the join is one-to-one or one-to-many (multiple property).

Join object definition

modelStringName of the model. For left joins, this is the secondary model you want to join with the main model.
join_propertiesObjectCollection of key-value pairs that determine the keys in each model to perform the join operation. The key is the property of the model defined in this object and the value is the property to join in another model (or the main model for left joins).
multipleBooleanDetermines if the match is one-to-one (false) or one-to-many (true). The default value is false.

Left join example

The example below combines the employee and managers models to create the employee_manager model. The models are joined based on a match between the managers model's employee_id and the employee model's auto-generated id.


Inner join example

The example below performs an inner join on the employeeemployee_manager, and employee_habit models. Both the employee_manager and employee_habit properties will try to match the employee_id property.

 Expand source