The Anon API lets you easily access extracted and processed data from migrations. This guide introduces the core concepts and API features you need to understand to effectively integrate with Anon.
This guide covers the fundamental concepts of the Anon API. For step-by-step implementation instructions, see the Quickstart guide.
Anon offers a REST API that follows resource-based principles. Each entity in the system (users, migrations, files) is a resource with a unique identifier that can be created, retrieved, and managed through standard HTTP methods.
Your organization can only access data that originates from migrations initiated through your embedded modal interface.
When integrating Anon, you’ll be working with end users (your customers) who initiate migrations. Anon’s API allows you to:
Generate a link for an embeddable iframe of the migration modal tailored to a specific end user
Retrieve migrations and extracted data for specific end users
End users initiate migrations via the embedded modal, and your system can subsequently retrieve these migrations through the API endpoints for additional processing and integration.
Anon organizes data into a medallion architecture, which separates data into three distinct layers that progressively improve data quality and structure:
Bronze Artifacts / Files: Raw, unprocessed data exports from the source system. These files maintain the original format and structure from the source platform.
Silver Artifacts / Files: Cleaned and standardized data files that have been transformed into a consistent, machine-readable format (typically JSON). This layer may include data validation and quality checks.
Gold Artifacts / Files: Business-ready, aggregated data that combines and enriches information from multiple silver files. These files are optimized for analytics and reporting.