Introduction

For a functional overview of how the integration works, see Functional Overview.

The Element451 integration with Anthology is designed to be simple from a user perspective, while handling complex data processing behind the scenes.

Element451 has built a baseline integration that interacts with standard endpoints and processes available through the Anthology API to sync basic student data, previous school history, applications, and documents to the SIS system, but there may be additional properties or fields your system is configured to use based upon your SOW.

Scope of This Guide

This section provides a high-level technical overview of what occurs after the integration process is triggered by the webhook (see Functional Overview).

• The process described here reflects the standard integration flow used for most partners
• Some implementations may include customizations or exceptions based on specific requirements

For detailed information on Anthology endpoints, payloads, and data structures, refer to Anthology’s API documentation: https://developer.anthology.com/portal/displayApi/Student

Primary Tool

Element451 uses Dagster to orchestrate all integration processes.

Dagster manages the following sync types:

• Element451 → Anthology
• Anthology → Element451

How It Works

• Dagster runs a series of jobs and sensors to monitor and execute integration activity.
• Within each sync process, multiple operations (ops) are performed to:
  • Extract data
  • Transform data
  • Send or receive data between systems