Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

History

18 Commits

Repository files navigation

FlashForge API Documentation

Unofficial, community-driven documentation for FlashForge 3D printer networking protocols and APIs. Covers the Adventurer 3, Adventurer 4, Adventurer 5M, and AD5X printer families.

All documentation lives in the Wiki.


Supported Printer Families

FamilyPrimary APIAuthWiki Page
Adventurer 5M / 5M ProHTTP REST (8898) + TCP (8899)CheckCodeAdventurer 5M Series
AD5XHTTP REST (8898) + TCP (8899) + IFSCheckCodeAD5X
Creator 5 / 5 ProHTTP REST (8898) only — no TCPCheckCodeCreator 5 Series
Adventurer 4 Pro / LiteTCP (8899)NoneAdventurer 4 Series
Adventurer 3 SeriesTCP (8899)NoneAdventurer 3 Series

Documentation

Core Protocols

  • HTTP REST API — JSON-based control interface on port 8898 (5M / AD5X)
  • TCP Protocol — Text-based G/M-code interface on port 8899 (all models)
  • Discovery Protocol — UDP auto-discovery for finding printers on the network
  • Authentication — CheckCode auth for HTTP API, open access for TCP

References

Printer-Specific

Advanced

Endpoint YAML Files

Machine-readable endpoint specifications are available in the endpoints/ directory:

FileDescription
endpoints_5m_3.2.7.yamlAdventurer 5M / 5M Pro HTTP endpoints (firmware 3.2.7)
endpoints_ad5x_1.1.7.yamlAD5X HTTP endpoints (firmware 1.1.7)
endpoints_ad5x_1.2.1.yamlAD5X HTTP endpoints (firmware 1.2.1)
endpoints_creator5_1.9.2.yamlCreator 5 / 5 Pro HTTP endpoints (HTTP-only, firmware 1.7.8 / 1.9.2)
networkserver_commands_adventurer3.yamlAdventurer 3 TCP commands
networkserver_commands_adventurer4.yamlAdventurer 4 TCP commands

Methodology

This documentation is compiled from:

  • Firmware analysis and filesystem inspection
  • Network traffic capture and protocol analysis
  • Community testing across multiple printer models and firmware versions

Contributing

Contributions are welcome via pull requests. When submitting:

  • Specify the printer model and firmware version tested
  • Include methodology (traffic capture, binary analysis, live testing)
  • Reference specific protocol details or packet captures where possible

This is an unofficial community project and is not affiliated with FlashForge.

About

Unofficial FlashForge API Documentation

Topics

Resources

Stars

6 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages