the rendered output of the last IPageRequest
new for Chrome backend. if your IPageRequest had any content errors, they will be listed here.
data in either base64 or utf8 format, or JSON. see content.encoding
and content.name
for hints as to the type
new for Chrome backend. information on what finished the page execution.
If normal
then most likely everything was rendered properly. If another value, be advised your content may not have rendered properly.
Inspect the value of statusCode and Please see contentErrors and/or execErrors for details on what could have occured.
Additionaly, inspect other parameters for hints, such as resourceSummary and pageExecLastWaitedOn
utf8 or base64
new for Chrome backend. the rendered page's final eventPhase. see IPageResponse.eventPhase for further explanation
new for Chrome backend. if the rendering system experienced any errors when processing the page, they will be listed here.
extra response headers you want sent with your response. set by IRenderSettings.extraResponseHeaders
headers of the target url, only set if IRenderSettings.passThroughHeaders===true
filename you could use if saving the content to disk. this will be something like 'content.text', 'content.jpeg', 'content.pdf' thus this informs you of the content type
new for Chrome backend. for debugging your request, if our IPageRequest didn't succeed with statusCode 200, we'll output the last thing waited on.
set via IRenderSettings.passThroughStatusCode, if this is true, when returning the response to you, the content's status code will be sent, irrespective of your API statusCode.
new for Chrome backend. summary of all resources requested by the page. see IPageResponse.resources for detailed listings
the size of data, in bytes
status of the content.
200
: Everything good, no errors were encountered at all408
: The targetURL was unable to load.424
: Some errors were encountered during rendering the page. These may be harmless script errors in the page itself, but it also may be something that could impact your rendered output.
Please see contentErrors and/or execErrors for details.
Additionaly, inspect other parameters for hints, such as resourceSummary and pageExecLastWaitedOnthe final url of the IPageRequest after redirects
metadata about the transaction
information about the PhantomJsCloud.com system processing this transaction
identifier of the system, for troubleshooting purposes
Chrome or PhantomJs
(major/minor/point)
number of requests processed by this backend
how much this transaction costs.
NOTE: the creditCost, prepaidCreditsRemaining, and dailySubscriptionCreditsRemaining are also returning in the HTTP Response Headers via the keys
pjsc-credit-cost
, pjsc-daily-subscription-credits-remaining
, and pjsc-prepaid-credits-remaining
bytes egress
the total cost of this response
estimation of your remaining daily creditBalance. This is incrementally refilled hourly.
the end time of your IUserRequest.
bytes ingress when using a built-in proxy (including geolocation)
cost of geo or builtin proxy
the start time of your IUserRequest.
if true, informs our server to send back JSON, including the response plus metadata. if False, if should send back only the content.
debug trace information provided by the api.
the original request, without defaults applied. to see the request with defaults, see IPageResponse.pageRequest
a collection of load/processing information for each IPageRequest you requested.
output from IPageRequest.queryJson. used to reduce output verbosity.
the HTTP Status Code PhantomJsCloud returns to you
if an error was detected, we will try to supply a statusMessage to help debug. Additionally,this will be placed as the pjsc-status-message
response header.
This is returned to you when "outputAsJson=true".