Skip to main content

Confirm

Are you sure?

Console

Capture the JavaScript console output a page produces as it loads — errors, warnings and uncaught exceptions. Useful for monitoring third-party scripts, catching regressions and health-checking your own pages.

This is a web operation — no AI, metered against your web allowance.

POST/console

Capture console messages

Body parameters

  • Name
    url
    Type
    string
    Required
    Required
    Description
    The absolute URL of the page to process. Rendered with headless Chrome, so JavaScript runs and redirects are followed. It must not include a username or password (https://user:pass@example.com).
  • Name
    report_to
    Type
    string
    Description
    Webhook URL — an http or https address URLpipe POSTs the result to when it's ready. Optional: without it we deliver to your project's default endpoint if it has one, and otherwise send no webhook at all — the result still waits for you at GET /result/:token. A value we cannot deliver to returns 422. Ignored on a sync=true request. Deliveries can be signed so your endpoint can verify they came from us.
  • Name
    sync
    Type
    boolean
    Description
    Process the request synchronously, returning the result inline in the response. Defaults to false (async: return a token now, and either receive the result at a webhook or fetch it with GET /result/:token). See Async & sync modes for the full contract.
  • Name
    max_age
    Type
    string | integer
    Description
    How fresh a cached result must be to be accepted. Either an integer number of seconds (3600) or a duration string of the form "<number> <unit>" — units s/min/h/d/w (e.g. "2 hours", "3 days", "30m"). Defaults to 7 days, clamped to a max of 30 days; 0 always bypasses the cache. See Caching for all accepted units.

Response

Content type application/json — an array of message objects. An empty array [] means the page produced no errors or warnings.

Message fields

  • Name
    type
    Type
    string
    Description
    One of error, warning or exception.
  • Name
    text
    Type
    string
    Description
    The message text.
POST/console
curl -X POST https://urlpipe.dev/console \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'
Response
[
  {
    "type": "error",
    "text": "Failed to load resource: the server responded with a status of 404 ()"
  },
  {
    "type": "warning",
    "text": "A cookie was set with `SameSite=None` but without `Secure`"
  },
  {
    "type": "exception",
    "text": "ReferenceError: bar is not defined"
  }
]

Message types

  • Name
    error
    Description
    From console.error() calls and failed resource loads.
  • Name
    warning
    Description
    From console.warn() calls and browser deprecation warnings.
  • Name
    exception
    Description
    Uncaught JavaScript exceptions caught via window.onerror.

How it works

URLpipe loads the page in a headless browser, listens for console errors, warnings and uncaught exceptions, then waits briefly after the page's network activity settles so asynchronous scripts have time to run and report. All captured messages are returned together.

Responses

Whatever the status, the response carries metadata headers: the result token, whether it was served from cache and how old that result is, how long we took, and the quota you have left.

Status
When
Body
200 OK
The request succeeded.
Sync: the result, in this endpoint's format (see Response above). Async: a job token — { "token": "…", "status": "accepted" }.
422 Unprocessable Entity
The analysis failed, or a parameter was invalid (a bad max_age, or a report_to we will not deliver to).
{ "error": "<message>" }
429 Too Many Requests
You've hit your monthly quota for this operation's category (checked only on a cache miss).
{ "error": "quota_exceeded", "category", "limit", "used", "resets_at" }
504 Gateway Timeout
Sync only: the analysis didn't finish within 60s. It keeps running — fetch it via GET /result/:token.
{ "error": "processing_timeout", "token": "…" }
401 Unauthorized
Missing or invalid API key.

Try it live — no API key needed

Run this endpoint against any URL right in your browser.

Open tool