/-/headless/Headless: available in Headless and Hybrid WebEngine Modes
/-/headless/routing.jsonRouting: available in Headless and Hybrid WebEngine Modes
/?toJSONtoJSON: available in Headless and Hybrid WebEngine Modes
/-/gql/GraphQL: available in Headless and Hybrid WebEngine Modes
/-/instant/Instant API: available in Developer Settings
/-/headless/endpoint in the browser. In each content item there is a Headless section. When selected it will provide formatted links to the following:
/?toJSONendpoint to output the item in JSON
/-/instant/endpoint provides the same read only Instant API JSON the Manager provides in models and items
/-/gql/formatted URLs output flat objects ideal for feeding to GraphQL servers
/-/headless/endpoint. This can be achieved by adding the endpoint to your Instances live domain. For example:
/?toJSONendpoint can be added to the end of any view route established in the users' Instance. Once applied the route will automatically render a JSON output of that view. Additional parameters can be applied to remove the meta data from the output. For example:
/-/gql/is slightly different from other JSON options. The addition to the URL is attached to the end of the Instance's domain, followed by the model's name. For example:
toJSON()there are some limitations to incorporating multiple content items in one object. However, it is ideal for creating a fully hydrated JSON object of any content item. This method is covered in depth here.
toJSON()method, users can loop through multiple content items to produce a JSON that has the desired content. As well as filter out the fields that are not necessary for the rendered output. Creating a custom endpoint guide can be found here.