> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enterspeed.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schemas

The schemas define the API endpoint and data structure for your data. This is where decoupling is happening since you are specifying the new structure of your [source entities](/enterspeed/key-concepts/source-entities) through schema mappings, and generating [views](/enterspeed/key-concepts/views) based on these mappings.

### How?

A schema acts as a middleman, grabbing the data from the source entities and generating the view with a data structure that is based on the schema definitions.

[Views](/enterspeed/key-concepts/views) are the result of the above, and what we receive as a response when calling the Enterspeed API.

Schema is key in setting up and defining API's, property mapping, [routes](/enterspeed/key-concepts/routing), [actions](/enterspeed/reference/js/full-schema/actions) and more.

## Important topics

[Schema docs](/enterspeed/reference/js/full-schema/intro)

[Referencing schemas](/enterspeed/key-concepts/referencing-schemas)

[Actions](/enterspeed/reference/js/full-schema/actions)

[Routing](/enterspeed/key-concepts/routing)

[Partial schemas](/enterspeed/key-concepts/partial-schemas)

[Reprocessing](/enterspeed/key-concepts/reprocessing)

## Tutorials

[Schema snippets](/enterspeed/reference/snippets)

[Designing a schema](/enterspeed/transform/designing-a-schema)

[Multilevel navigation example](/enterspeed/tutorials/multilevel-navigation/1-getting-started)

[Umbraco & Next.js example](/enterspeed/tutorials/umbraco-nextjs/3-designing-your-apis)