⚠️ This project is deprecated. rest.li is no longer actively maintained and the repository will be archived (read-only) on July 22, 2026. LinkedIn has moved to gRPC internally; gRPC is not a drop-in replacement. Existingcom.linkedin.pegasus:*artifacts on Maven Central remain available. See #1178 for details.
At LinkedIn, we are focusing our efforts on advanced automation to enable a seamless, LinkedIn-wide migration from Rest.li to gRPC. gRPC will offer better performance, support for more programming languages, streaming, and a robust open source community. There is no active development at LinkedIn on new features for Rest.li. The repository will also be deprecated soon once we have migrated services to use gRPC. Refer to this blog for more details on why we are moving to gRPC.
Rest.li is an open source REST framework for building robust, scalable RESTful architectures using type-safe bindings and asynchronous, non-blocking IO. Rest.li fills a niche for applying RESTful principles at scale with an end-to-end developer workflow for building REST APIs, which promotes clean REST practices, uniform interface design and consistent data modeling.
Source | Documentation | Discussion Group
- End-to-end framework for building RESTful APIs
- Approachable APIs for writing non-blocking client and server code using ParSeq
- Type-safe development using generated data and client bindings
- JAX-RS inspired annotation driven server side resource development
- Engineered and battle tested for high scalability and high availability
- Optional Dynamic Discovery subsystem adds client side load balancing and fault tolerance
- Backward compatibility checking to ensure all API changes are safe
- Support for batch operations, partial updates and projections
- Web UI for browsing and searching a catalog of rest.li APIs.
See our website for full documentation and examples.
- Discussion Group: LinkedIn Rest.li Group
- Follow us on Twitter: @rest_li
- Issue Tracking: GitHub issue tracking