Skip to main content

aiosatisfactory

This is an async Python library for Satisfactory dedicated server's APIs.

This work is based off the official documentation that is provided with the game files or is also available on the official wiki

Lightweight API (docs)

This API should be used to poll the server state before making most of the https requests
No errors are raised but you must check if the query was succesful

Usage:

from aiosatisfactory import SatisfactoryServer
import asyncio, time

async def main():
    server = SatisfactoryServer("server.ip")
    query = await server.lightweight.query(time.time_ns())
    print(query.response.SubStates)

asyncio.run(main())

Https API (docs)

This API requires the session parameter to be set in the SatisfactoryServer constructor
It does raise an ErrorResponse exeption if the function you try to execute fails

Usage:

import asyncio, aiohttp
from aiosatisfactory import SatisfactoryServer
from aiosatisfactory.https.models import ErrorResponse

async def main():
    async with aiohttp.ClientSession() as session:
        client = SatisfactoryServer("server.ip", session=session)
        try:
            response = await client.https.api.health_check()
            print(response.health)
        except ErrorResponse as e:
            print(f"Error: {e.error_code, e.error_message, e.error_details}")

asyncio.run(main())

Mappings

The Https API provides the value of active_schematic and game_phase as some internal strings, this class provides translations to the proper display names

Usage:

import asyncio, aiohttp
from aiosatisfactory import SatisfactoryServer
from aiosatisfactory.https.models import ErrorResponse

async def main():
    async with aiohttp.ClientSession() as session:
        client = SatisfactoryServer("server.ip", session=session, api_token="your_api_token")
        try:
            response = await client.https.api.query_server_state()
            print(client.mappings.game_phase(response.game_phase))
            print(client.mappings.schematic(response.active_schematic))
        except ErrorResponse as e:
            print(f"Error: {e.error_code, e.error_message, e.error_details}")

asyncio.run(main())

Metadata

Release files for aiosatisfactory 0.1.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aiosatisfactory 0.1.7
File Size Uploaded
aiosatisfactory-0.1.7.tar.gz 9.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aiosatisfactory 0.1.7
File Interpreter ABI Platform
aiosatisfactory-0.1.7-py3-none-any.whl Python 3 none any Details

Total release size: 21.2 kB

Release files / aiosatisfactory-0.1.7.tar.gz

Download URL aiosatisfactory-0.1.7.tar.gz
Size 9.6 kB
Tags Source
SHA-256 checksum
How to use checksums
11d9119449a910b051f1e473714831080a1304259b641815a80fdf70c17535b3
BLAKE2b-256 checksum
How to use checksums
5c820a97eb67cabec9b19094647169f92286e710134cb947d1657f828e349a6a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.

Transparency log

Release files / aiosatisfactory-0.1.7-py3-none-any.whl

Download URL aiosatisfactory-0.1.7-py3-none-any.whl
Size 11.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7526c7efe8a09019ffd2e1c39da3f0289572da49b0c52bf39ba3b377d760f978
BLAKE2b-256 checksum
How to use checksums
550eea1a5e9d3ad4bae4e255b8df26f5cad735517c72d6501e39ea8fbde0f293
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.7 This release

2 release files

0.1.6

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page