const sharp = require('sharp');

sharp('input.jpg')
  .resize(200)
  .toFile('output.jpg', (err, info) => {
    if (err) throw err;
    console.log(info);
  });

Blog

Support

Documentation

Dashboard

You can target different device types to execute the request on.

Device-type targeting

The Massive Network is a global edge network that’s used by partners to monitor internet performance, gather business intelligence, and detect fraud and malware.

Introduction

Start crawling the web in under 5 minutes.

Quickstart

Authentication

Our robust proxy services allows for geotargeting, sticky sessions, device type targeting, and advanced accounting and reporting.

Request routing

You can tune the request by providing geo parameters like an [ISO ZIP code, subdivision, and country code](https://www.iso.org/obp/ui/#search), and by [city](https://www.geonames.org/).

Geotargeting

We support session persistence (AKA sticky sessions) with a TTL of 15 minutes.

Sticky sessions

If you prefer to segregate requests for your customer invoicing or internal accounting, subaccounts can be provided.

Accounting

Some restrictions apply to the use of both the HTTP(S) and SOCKS5 endpoints.

Usage restrictions

Massive may respond with one of several common or custom error messages:

Error Types

Integrate the Massive Network into your Puppeteer workflows by setting the `--proxy-server` launch flag then calling a page object’s `authenticate` method:

Puppeteer

To connect to the Massive Network from Python, include your encoded credentials in the proxy address (this usage doesn’t risk leaking your API token to a shared history file per the caveat for Curl):

(Vanilla) Python

After installing Scrapy (`pip install scrapy`) and creating a project (`scrapy startproject [project name]`), you can connect to the Massive Network by saving code like that below to a file in the new `[project name]/[project name]/spiders` subdirectory then running `scrapy crawl demo` from the top-level `[project name]` directory (Scrapy doesn’t seem to support HTTPS proxy connections, but you can use the [network’s HTTP port](/authentication#http)):

Scrapy (for Python)

Ruby’s standard HTTP library doesn’t seem to support HTTPS proxy connections, so connect to the [Massive Network’s HTTP port](/authentication#http) with Ruby:

Ruby

.NET integrations should connect to the [Massive Network’s HTTP port](/authentication#HTTP) `65534` because [.NET doesn’t broadly support HTTPS proxies yet](https://github.com/dotnet/runtime/pull/87638):

.NET (in C#)

Extract live results from popular search engines

Search service

This guide will help you get started with the Reporting API in just a few minutes.

Reporting API

The Proxy Resellers API allows you to manage proxy reseller accounts. With this API, you can create, update, and manage accounts that are used to authenticate with the Massive Network API.

The Proxy Resellers API uses API key authentication. You must include your API key in the header of every request to authenticate.

This guide will help you get started with the Proxy Resellers API in just a few minutes.

Create new account

Get account

Get list of existing accounts

Update account

Disable account

Enable account

Allocate traffic for an account

Get account usage

Get the list of allocations made via the put endpoint for the account.

Get the allocation list

The Massive SDK provides a new way to monetize app features and content without annoying ads or low-converting paywalls.

The Massive SDK is available on Windows, Android, FireOS, iOS, and Linux.

The Massive SDK is available on Windows, macOS and Linux.

Select Your Platform

Integrate Massive SDK into your Windows application with this guide.

Windows (C/C++)

Integrate Massive SDK into your Mac application with this guide.

Mac (Objective-C)

Mac (Swift)

The Massive SDK is available on Android, FireOS, and iOS.

Android

Integrate Massive SDK into your Fire OS application with this guide.

Get Started

Proxy Configuration

Sample Integrations

Advanced Features

Reseller API

Monetization SDK

Device-type targeting