Skip to main content

/pressure API

The /pressure API returns real-time system load information for your Browserless instance, and is available for both self-hosted and dedicated accounts.

Querying system pressure

Issue a GET request to /pressure to check current load:

curl -X GET \
https://production-sfo.browserless.io/pressure?token=YOUR_API_TOKEN_HERE

Running this request will result in a JSON output like:

{
"pressure": {
"cpu": 45,
"memory": 62,
"isAvailable": true,
"maxConcurrent": 10,
"maxQueued": 10,
"running": 3,
"queued": 0,
"reason": "",
"recentlyRejected": 0,
"date": 1711468800000,
"message": ""
}
}

Response fields

FieldTypeDescription
cpunumber or nullCPU usage percentage
memorynumber or nullMemory usage percentage
isAvailablebooleanWhether the instance accepts new sessions
maxConcurrentnumberMaximum concurrent browser sessions
maxQueuednumberMaximum queued requests
runningnumberCurrently running sessions
queuednumberCurrently queued requests
reasonstringWhy the instance is unavailable: full, cpu, memory, or empty
recentlyRejectednumberRecent rejected connection count
datenumberTimestamp of the response in milliseconds
messagestringAdditional status message

Common use cases

Use /pressure to check whether your instance can handle another connection before starting a new session. This is especially useful for:

  • Load balancing: Route traffic to instances with available capacity (see NGINX Load Balancing)
  • Auto-scaling: Trigger scale-up when isAvailable is false or running approaches maxConcurrent
  • Health monitoring: Integrate with external monitoring systems to track resource usage over time
  • Queue management: Check queued count to detect when requests are backing up