System fields

All default, and custom content types come with some managed system fields. These fields reflect certain states of your content, such as when it was last updated, or published at.

Default model fieldsAnchor

These fields are included with all content models you create within Hygraph.

User fieldsAnchor

Since the User model is included with every project, it also comes with some predefined fields, as well as all of the system fields above (but not createdBy, updatedBy, and publishedBy).

The User model is part of "user attribution", and is connected with content entries. This connection allows you to see who created, updated, and published content entries.

• If content is mutated with a Permanent Auth Token then kind will return PAT.
• If Public API Permissions are enabled, and content is mutated, kind will return PUBLIC.

{
  posts {
    createdBy {
      id
      name
      picture
      kind
    }
  }
}

{
  posts {
    updatedBy {
      id
      name
      picture
      kind
    }
  }
}

{
  posts {
    publishedBy {
      id
      name
      picture
      kind
    }
  }
}

Asset fieldsAnchor

Since the Asset model is included with every project, it also comes with some predefined fields, as well as all of the system fields above.

The Asset field type has all of the default model fields, as well as:

Asset fields are localized by default, and always include the localization fields described below.

Localization fieldsAnchor

When you localize fields within Hygraph, the model will be updated to contain the following fields:

Learn more about working with Localization.

Version history fieldsAnchor

One of the auto-generated queries Hygraph will create is around versioning. Each time you publish content to a stage, a version is saved.

You can fetch the version history of a content entry by using the history field on a model. This field is managed automatically by Hygraph.

{
  posts {
    id
    title
    history {
      id
      stage
      revision
      createdAt
    }
  }
}

Connection type fieldsAnchor

Since Hygraph implements the Relay specification, when fetching with Relay you will have some fields made available to you automatically.

For example, let's imagine we have the model Post. The postsConnection would look a little something like:

[PostEdge!]!Anchor

{
  postsConnection {
    edges {
      cursor
      node {
        id
        title
      }
    }
  }
}

PageInfo!Anchor

Hygraph exposes the PageInfo type on the field pageInfo for connection queries. This is useful with cursor based pagination.

{
  postsConnection {
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
      endCursor
      pageSize
    }
  }
}

Learn more about Relay cursor pagination.

Aggregate!Anchor

It is possible using the connection type query to perform an aggregate count.

{
  postsConnection {
    aggregate {
      count
    }
  }
}