WEBT Logs

JSON (JavaScript Object Notation) is a lightweight text format whose syntax mirrors JavaScript objects, so the browser can turn it into usable data almost for free. JSON encodes data as key–value pairs inside { }, looking just like a JavaScript object literal: { "name": "Anna M...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

JSON is compact and maps straight onto JavaScript data, while XML is more verbose but supports attributes, comments, and richer schema validation — and for web APIs, JSON usually wins. The same data shows the contrast. In XML a list of relatives needs a repeated tag for each item...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

Because fetch only rejects on network failure, not on HTTP error statuses — so you need both: try…catch for the network, and an explicit response.ok check for 4xx/5xx responses. * fetch's two failure classes: the network rejects into catch; HTTP errors resolve and need the respo...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

An element is the content from start-tag to end-tag (including everything nested inside); an attribute is a named key="value" pair written inside the start-tag that annotates the element. The two are XML's two places to put data, and they look different: <book isbn="1575213966">...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

You nest data in JSON by putting objects inside objects and using arrays of objects, to any depth — the same way you'd nest JavaScript objects and arrays. { "person": { "name": "Anna", "address": { "street": "Main St", "city": "Zurich" }, "phones": [...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

In frontend integration the user's browser calls the external API directly with JavaScript after the page has loaded — your own webserver is not involved in those calls. The flow has two distinct phases. First the page is delivered normally; then the JavaScript on it talks to the...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

In backend integration your webserver calls the external API itself and sends the finished result to the client — the browser never talks to the external service directly. The difference is who makes the external call. In the frontend model the browser fetches the API directly; i...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

Integrating an external webservice follows a predictable arc: understand the API, poke it by hand, then build search → display → error handling around it. A "webservice integration" means your app pulls live data from someone else's API instead of computing it itself. The trap be...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

An API key (sometimes called a token) is a unique string that identifies and authenticates your application to an external API — usually sent as a query parameter or an HTTP header. You typically get a key by registering with the provider; the key then ties every request back to...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026

Node.js has the same built-in fetch API as the browser (no import needed since Node v21), so the calling code looks almost identical — the difference is in the request headers that get sent. async function getStationData(station) { const url = 'https://transport.opendata.ch/v1/...

Quiz: WEBT / External Webservices | updated: Nov 01, 2026