API
  • API Index
  • Batch API
  • Content Negotiation
  • Dynamic Paths
  • Hierarchy API
  • List API
  • Quick Reference
  • Time Series API
  • Views
      • Configuration
  • Overview
  • Application Configuration
  • Documentation Configuration
  • Spec Configuration
      • Features
  • API Testing
  • Asynchronous Processing
  • Cassandra Time-Series Engine
  • Cassandra Integration
  • Default Controller Customisation
  • Documentation
  • Geospatial Filtering
  • Model Documentation
  • PostgreSQL Integration
  • Excel Spreadsheet Format
      • Tutorials
  • Step-by-Step Guide
  • Archetype Setup
  • Logging
  • Prometheus
  • Sentry Logging
      • UI Customisation
  • UI Customisation
  • SASS Build Chain
  • Shared Layout
  • API Documentation
  • Model Documentation
  • Results
    • sapi-nt v current

    Sapi-nt Configuration

    Your sapi-nt application can be set up and customised entirely using configuration files. These include Spring configuration files and sapi-nt specific files. Usually, these files should be written in YAML format.

    The various types of configuration are documented here:

    The sapi-nt archetype should provide an adequate minimal configuration for the app to run successfully, but you will need to include spec files for your data model, data source and endpoints in order to start building an API and emitting useful data.