Location and time

Tell the page where and when it is being viewed

A page can ask the browser for coordinates and a clock. Those two answers are yours to set — the third one, the exit IP, is a different product.

geolocation_latitudegeolocation_longitudegeolocation_accuracytime_zoneip_country_code
curl --fail-with-body "https://api.pagecapture.dev/v1/take" \
  -H "X-Access-Key: $PAGECAPTURE_KEY" \
  -H "Content-Type: application/json" \
  --data '{"url":"https://example.com","format":"jpg","geolocation_latitude":41.3874,"geolocation_longitude":2.1686,"geolocation_accuracy":50,"time_zone":"Europe/Madrid"}' \
  -o capture.jpg

Verified 2026-08-13 by running the published code against a fixture.

Configure it in the playground
What you are seeing

A store locator shows the wrong city, or timestamps in the capture are hours off from the audience the screenshot is for.

Why the page does that

The capture pool has one physical location and, by default, one clock. A page that personalises on either gets the pool's answer, not your customer's.

What it does

  • Answers the browser Geolocation API with the coordinates and accuracy you set, so a page that asks for permission receives a definite reply.
  • Sets the browser context's IANA time zone, defaulting to UTC, which is what every rendered date and time follows.
  • Keeps all three in the cache key, so a capture localised for one city is never served for another.

What it does not do

  • Does not change the IP the request exits from. Geolocation is what the page asks the browser; the exit address is what the page observes on its own.
  • Does not grant location permission on a site that never asks for it. Nothing here forces the prompt.
  • Does not currently offer a country-level proxy exit. `ip_country_code` is validated and entitled, and its infrastructure is not serving traffic yet — see below.
The contract

Every limit on this page is the one the API enforces

These rows are read from the same parameter table that validates your request. Nothing here is transcribed, so a number cannot drift from the behaviour it describes.

ParameterTypeDefaultRangeEndpointsCache key
geolocation_latitude

Latitude reported to the Geolocation API.

number-90 – 90/v1/take, /v1/animateIn
geolocation_longitude

Longitude reported to the Geolocation API.

number-180 – 180/v1/take, /v1/animateIn
geolocation_accuracy

Accuracy in metres.

number0 – 100,000/v1/take, /v1/animateIn
time_zone

IANA time zone for the browser context.

stringUTC/v1/take, /v1/animateIn
ip_country_code

Country the managed proxy pool exits from. The catalog is served at /v1/regions.

enum/v1/take, /v1/animateIn
Group: GeolocationValues outside a documented range are rejected before a browser opens.
ip_country_codeNot available yet

Included on Free, Growth, Scale, Enterprise. The entitlement exists and the infrastructure does not: Pending a contracted proxy provider. The parameter validates, and until this pill changes there is nothing behind it — do not build on it.

How it behaves next to the rest of the request

ip_country_code

Country the managed proxy pool exits from. The catalog is served at /v1/regions.

Exists in the contract, takes a code from the published region catalog and requires the ip_location entitlement. Availability is tracked separately from entitlement precisely so a plan cannot sell a capability that has no infrastructure behind it — and today this one does not.

time_zone

IANA time zone for the browser context.

An IANA name, defaulting to UTC. Set it whenever the capture contains a timestamp somebody will read as their own local time.

proxy

Your own proxy, as `http://user:pass@host:port`.

Your own proxy, if you have one, is the way to control the exit address today. It is write-only, encrypted, and destroyed with the job.

Errors this option can produce

None of them is billable. No error code in the catalog is.

Questions this raises

Can I capture a page as if I were in another country?

Partly. Coordinates and clock are set here; the exit IP is not. A site that geolocates by IP will still see the capture pool's address unless you supply your own proxy.

Is ip_country_code usable today?

No. It is a documented parameter with a plan entitlement and a published region catalog, and no proxy provider is contracted yet. The page says so rather than letting the pricing table imply otherwise.

What time zone applies if I set nothing?

UTC. It is a default rather than the machine's zone, so two captures of the same page are comparable regardless of which worker ran them.