POSIX

POSIX, the Portable Operating System Interface standardized as IEEE 1003 (and jointly published by The Open Group), defines a common contract for how software talks to a Unix-like operating system. It specifies the system-call API, the shell and command-line utilities, and the environment behavior that programs can rely on, so that source code written to the standard can compile and run across compliant systems. It is one of the foundational portability standards underneath the software most APIs run on.

• A portable system API - Standardized calls for files, processes, threads, signals, and I/O let software move between Unix-like platforms.
• Shell and utilities - Defines the behavior of the shell and core command-line tools, which is why scripts behave consistently across systems.
• Multiple profiles - Real-time, threads, and other option groups let constrained and specialized systems claim partial conformance.
• A stable, versioned contract - Maintained across decades through IEEE and The Open Group revisions, giving vendors a durable target.

POSIX rarely appears in an API spec directly, but it is the substrate almost every API service is deployed on — Linux, macOS, and the containers running in the cloud all trace their portability guarantees back to it. Understanding it matters for the operational side of API delivery: build tooling, CI pipelines, shell-based automation, and the runtime environments where servers execute all lean on POSIX behavior. It is a good reminder that the API economy sits on top of long-lived interface standards that make portability possible in the first place.