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

    Default Controller Customisation

    A good starting point in creating a custom default controller is the DefaultController which is an entry point for all the requests that come into your api. The table below contains the name of the methods and the corresponding media types served by them:

    Name Media type served
    respondWithHtml text/html
    respondWithGeoJson appilcation/geo+json
    respondWithOther application/json, text/turtle, application/rdf+xml and text/csv
    respondWithCsvm application/csvm+json

    If you want to remove the support for any media type you can simply remove it from the produces value or remove the entire request mapping.