Documentation
  • Welcome
  • 🚀Getting Started
    • Introduction to AstroPlant
  • 🌱AstroPlant Kit Setup
    • Welcome to the setup guide
    • Designing your project
    • Operation & safety
    • Building the Maker Kit
      • Electronics assembly [Maker Edition]
      • Electronics assembly from scratch
      • Casing assembly v5.2
      • Extension shield connection mapping
    • AstroPlant software
      • Kit software setup
      • Building your kit software from scratch
      • Updating your kit software
      • Changelog
    • Registering and configuring a kit
    • AstroPlant Growth Protocol
    • Resources
    • Setup FAQ
  • ⌨️ Developers
    • Become a space dev!
      • AstroPlant Ecosystem
      • Data Concepts and Terminology
      • Software Architecture
      • GitHub Repositories
    • Core API
      • Getting Started
      • API Models
      • Live Feeds (WebSockets)
    • Community Platform
      • Architectural Decisions
      • Documentation
        • Project Structure
        • Front-End
        • Back-End
      • Development Setup
      • Roadmap
    • Software Customization
      • Use cases
    • Developers FAQ
  • 📚Resources
    • Contributing
Powered by GitBook
On this page
  • Purpose
  • Technical architecture and implementation

Was this helpful?

  1. ⌨️ Developers

Core API

PreviousGitHub RepositoriesNextGetting Started

Last updated 4 years ago

Was this helpful?

Purpose

The purpose of the core API is to provide access to data produced by AstroPlant kits and to control those kits. The API provides raw data, so that it's completely up for analysis after it's been served.

If you are looking for a way to gather raw data from your kit into an application or analysis directly from the API, or to programmatically control your kit—or even to create your own control interface—you are in the right place.

This documentation will go over the concepts used in the API. The exact endpoints and data models are prescribed by an OpenAPI specification. A Swagger UI to explore the specification can be found .

Technical architecture and implementation

If you are not interested in how the API is made, but want to know what you can do with it, you can skip this part and directly go to .

The API implementation source code is available . This program provides controlled access to the back-end, performing authentication and authorization, and enforces constraints on data state. This allows the API to be exposed publicly on the internet, to en enable users to securely and safely control the back-end and the kits connected to it. It also implements a controlled gateway of directly communicating with kits through the Kit Remote Procedure Call protocol.

here
the Getting Started section
here