Alternatives to OkHttp logo

Alternatives to OkHttp

Retrofit, Netty, Postman, Amazon API Gateway, and Insomnia REST Client are the most popular alternatives and competitors to OkHttp.
64
77
+ 1
0

What is OkHttp and what are its top alternatives?

HTTP is the way modern applications network. It’s how we exchange data & media. Doing HTTP efficiently makes your stuff load faster and saves bandwidth.
OkHttp is a tool in the API Tools category of a tech stack.

Top Alternatives to OkHttp

  • Retrofit
    Retrofit

    Retrofit turns your HTTP API into a Java interface

  • Netty
    Netty

    Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Amazon API Gateway
    Amazon API Gateway

    Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. ...

  • Insomnia REST Client
    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

  • OpenAPI
    OpenAPI

    It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service. ...

  • OpenAPI Specification
    OpenAPI Specification

    It defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. ...

  • Paw
    Paw

    Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code. ...

OkHttp alternatives & related posts

Retrofit logo

Retrofit

218
167
0
A type-safe HTTP client for Android and Java
218
167
+ 1
0
PROS OF RETROFIT
    Be the first to leave a pro
    CONS OF RETROFIT
      Be the first to leave a con

      related Retrofit posts

      Netty logo

      Netty

      228
      323
      14
      Asynchronous event-driven network application framework
      228
      323
      + 1
      14
      PROS OF NETTY
      • 8
        High Performance
      • 3
        Easy to use
      • 3
        Just like it
      CONS OF NETTY
      • 1
        Limited resources to learn from

      related Netty posts

      Postman logo

      Postman

      72.1K
      59.8K
      1.8K
      Only complete API development environment
      72.1K
      59.8K
      + 1
      1.8K
      PROS OF POSTMAN
      • 486
        Easy to use
      • 369
        Great tool
      • 275
        Makes developing rest api's easy peasy
      • 156
        Easy setup, looks good
      • 143
        The best api workflow out there
      • 53
        History feature
      • 53
        It's the best
      • 44
        Adds real value to my workflow
      • 42
        Great interface that magically predicts your needs
      • 34
        The best in class app
      • 11
        Can save and share script
      • 9
        Fully featured without looking cluttered
      • 7
        Option to run scrips
      • 7
        Collections
      • 7
        Global/Environment Variables
      • 6
        Dark theme easy on the eyes
      • 6
        Shareable Collections
      • 6
        Dead simple and useful. Excellent
      • 5
        Great integration with newman
      • 5
        Awesome customer support
      • 4
        Documentation
      • 4
        The test script is useful
      • 4
        Simple
      • 3
        This has simplified my testing significantly
      • 3
        Easy as pie
      • 3
        Makes testing API's as easy as 1,2,3
      • 3
        Saves responses
      • 2
        API-network
      • 2
        Mocking API calls with predefined response
      • 2
        I'd recommend it to everyone who works with apis
      • 1
        Easy to setup, test and provides test storage
      • 1
        Graph
      • 1
        Postman Runner CI Integration
      • 1
        Now supports GraphQL
      • 1
        Continuous integration using newman
      • 1
        Pre-request Script and Test attributes are invaluable
      • 0
        Runner
      • 0
        <a href="http://fixbit.com/">useful tool</a>
      CONS OF POSTMAN
      • 9
        Stores credentials in HTTP
      • 7
        Poor GraphQL support
      • 7
        Bloated features and UI
      • 7
        Cumbersome to switch authentication tokens
      • 3
        Expensive
      • 2
        Not free after 5 users
      • 2
        Can't prompt for per-request variables
      • 1
        Support websocket
      • 1
        Import curl
      • 1
        Import swagger

      related Postman posts

      Noah Zoschke
      Engineering Manager at Segment · | 30 upvotes · 2.2M views

      We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

      Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

      Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

      This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

      Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

      Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

      Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      Amazon API Gateway logo

      Amazon API Gateway

      1.3K
      914
      42
      Create, publish, maintain, monitor, and secure APIs at any scale
      1.3K
      914
      + 1
      42
      PROS OF AMAZON API GATEWAY
      • 36
        AWS Integration
      • 5
        Websockets
      • 1
        Serverless
      CONS OF AMAZON API GATEWAY
      • 1
        Less expensive
      • 1
        No websocket broadcast

      related Amazon API Gateway posts

      A Luthra
      VP Software Engrg at Reliant · | 3 upvotes · 555.4K views
      Shared insights
      on
      ApigeeApigeeAmazon API GatewayAmazon API Gateway

      Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

      See more
      Insomnia REST Client logo

      Insomnia REST Client

      640
      527
      40
      The most intuitive cross-platform REST API Client 😴
      640
      527
      + 1
      40
      PROS OF INSOMNIA REST CLIENT
      • 16
        Easy to work with
      • 11
        Great user interface
      • 6
        Works with GraphQL
      • 3
        Cross platform, available for Mac, Windows, and Linux
      • 2
        Opensource
      • 2
        Preserves request templates
      • 0
        Does not have history feature
      • 0
        Vim and Emacs key map
      CONS OF INSOMNIA REST CLIENT
      • 4
        Do not have team sharing options
      • 2
        Do not store credentials in HTTP

      related Insomnia REST Client posts

      Jason Barry
      Cofounder at FeaturePeek · | 4 upvotes · 2M views

      We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

      • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
      • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
      • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

      Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

      See more
      OpenAPI logo

      OpenAPI

      379
      314
      0
      Allows the owner of a network-accessible service to give universal access
      379
      314
      + 1
      0
      PROS OF OPENAPI
        Be the first to leave a pro
        CONS OF OPENAPI
          Be the first to leave a con

          related OpenAPI posts

          Joshua Dean Küpper
          CEO at Scrayos UG (haftungsbeschränkt) · | 4 upvotes · 273.3K views

          We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

          We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

          See more
          OpenAPI Specification logo

          OpenAPI Specification

          229
          121
          9
          An API description format for REST APIs
          229
          121
          + 1
          9
          PROS OF OPENAPI SPECIFICATION
          • 5
            API Documentation
          • 4
            API Specification
          CONS OF OPENAPI SPECIFICATION
            Be the first to leave a con

            related OpenAPI Specification posts

            Paw logo

            Paw

            207
            261
            165
            The ultimate REST client for Mac
            207
            261
            + 1
            165
            PROS OF PAW
            • 46
              Great interface
            • 38
              Easy to use
            • 25
              More stable and performant than the others
            • 16
              Saves endpoints list for testing
            • 13
              Supports environment variables
            • 12
              Integrations
            • 9
              Multi-Dimension Environment Settings
            • 4
              Paste curl commands into Paw
            • 2
              Creates code for any language or framework
            CONS OF PAW
            • 3
              It's not free
            • 2
              MacOS Only

            related Paw posts

            Jason Barry
            Cofounder at FeaturePeek · | 4 upvotes · 2M views

            We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

            • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
            • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
            • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

            Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

            See more