{"id":3720,"date":"2026-11-02T09:03:53","date_gmt":"2026-11-02T06:03:53","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3720"},"modified":"2026-11-02T09:03:57","modified_gmt":"2026-11-02T06:03:57","slug":"what-is-an-api-in-web-development","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/what-is-an-api-in-web-development\/","title":{"rendered":"What Is an API in Web Development? Frontend &amp; Backend"},"content":{"rendered":"\n<!--\nNewton Institute of Technology \u2014 Article 214\nMaster Stylesheet v6 Premium production body \u2014 31 October 2026\nWordPress supplies the page's only semantic H1. This fragment uses .nit-hero__title instead.\nLoad the locked NIT-Articles-Master-v6.0.css once at site level.\nNo article-specific CSS, inline styles, scripts, new component classes or article images are used.\nCanonical: https:\/\/niteducation.com\/resources\/what-is-an-api-web-development\/\nPrimary intent: what is an API in web development; how frontend and backend communicate.\n-->\n<article class=\"nit-article nit-article--pathway-guide nit-article--software\" itemscope itemtype=\"https:\/\/schema.org\/Article\" aria-labelledby=\"nit-article-title\">\n  <meta itemprop=\"datePublished\" content=\"2026-10-31\">\n  <meta itemprop=\"dateModified\" content=\"2026-10-31\">\n  <meta itemprop=\"inLanguage\" content=\"en-KE\">\n  <meta itemprop=\"author\" content=\"Newton Institute of Technology Editorial Team\">\n\n  <div class=\"nit-pg-hero\" aria-labelledby=\"nit-article-title\">\n    <div>\n      <p class=\"nit-pg-kicker\">Web Development Guide <span>Basics<\/span><\/p>\n      <p class=\"nit-hero__title\" id=\"nit-article-title\" itemprop=\"headline\">What Is an API?<br>How Frontend and Backend Communicate<\/p>\n      <p class=\"nit-pg-hero__line\">Frontend <i>\u00b7<\/i> API <i>\u00b7<\/i> Backend<\/p>\n      <p class=\"nit-pg-hero__summary\" itemprop=\"description\">Follow one web request from the screen to the server and back, then inspect the same request yourself in the browser.<\/p>\n      <div class=\"nit-pg-hero__actions\">\n        <a class=\"nit-pg-button nit-pg-button--gold\" href=\"#how-api-works\">Follow one request<\/a>\n        <a class=\"nit-pg-button nit-pg-button--outline\" href=\"#devtools\">Inspect it in DevTools<\/a>\n      <\/div>\n    <\/div>\n\n    <div class=\"nit-pg-hero__art\" aria-label=\"Frontend to backend API communication route\">\n      <p>The communication route<\/p>\n      <div class=\"nit-pg-signpost\" aria-hidden=\"true\">\n        <span class=\"nit-pg-signpost__top\">Frontend<\/span>\n        <span class=\"nit-pg-signpost__centre\">API<\/span>\n        <span class=\"nit-pg-signpost__bottom\">Backend<\/span>\n      <\/div>\n      <strong>Request goes in. Response comes back.<\/strong>\n    <\/div>\n\n    <div class=\"nit-pg-hero__meta\" aria-label=\"Article summary\">\n      <p><span>Focus<\/span>Web APIs<\/p>\n      <p><span>Flow<\/span>Request \u2192 response<\/p>\n      <p><span>Core tools<\/span>HTTP \u00b7 JSON \u00b7 Fetch<\/p>\n      <p><span>Updated<\/span>31 October 2026<\/p>\n    <\/div>\n  <\/div>\n\n  <div class=\"nit-article__body\">\n    <section class=\"nit-quick-answer\" aria-labelledby=\"quick-answer-title\">\n      <div class=\"nit-quick-answer__head\">\n        <span class=\"nit-quick-answer__mark\" aria-hidden=\"true\">\u2713<\/span>\n        <div>\n          <p class=\"nit-quick-answer__label\">Quick answer<\/p>\n          <p class=\"nit-quick-answer__kicker\" id=\"quick-answer-title\">What is an API in web development?<\/p>\n        <\/div>\n      <\/div>\n      <div class=\"nit-quick-answer__body\">\n        <p class=\"nit-quick-answer__text\"><strong>API stands for Application Programming Interface.<\/strong> It is a defined interface that lets software request data or functionality from other software. In a web application, an API often lets the frontend ask the backend for data or an action. The backend validates the request, performs the required work and sends a response back. APIs are broader than web APIs, so this guide focuses specifically on the web-development use case. <sup><a href=\"#ref-1\">[1]<\/a><\/sup><\/p>\n        <ul class=\"nit-quick-answer__signals\">\n          <li>Frontend sends<\/li>\n          <li>API defines<\/li>\n          <li>Backend processes<\/li>\n          <li>Database stores<\/li>\n          <li>Response returns<\/li>\n        <\/ul>\n      <\/div>\n    <\/section>\n\n    <div class=\"nit-facts-grid nit-software-facts\" aria-label=\"API fundamentals at a glance\">\n      <div class=\"nit-fact-card\"><span>Frontend<\/span><strong>User interface<\/strong><\/div>\n      <div class=\"nit-fact-card\"><span>API<\/span><strong>Communication interface<\/strong><\/div>\n      <div class=\"nit-fact-card\"><span>Backend<\/span><strong>Logic and rules<\/strong><\/div>\n      <div class=\"nit-fact-card\"><span>Database<\/span><strong>Persistent data<\/strong><\/div>\n      <div class=\"nit-fact-card\"><span>Request<\/span><strong>What client asks<\/strong><\/div>\n      <div class=\"nit-fact-card\"><span>Response<\/span><strong>What server returns<\/strong><\/div>\n    <\/div>\n\n    <nav class=\"nit-toc\" aria-labelledby=\"toc-title\">\n      <h2 id=\"toc-title\">On this page<\/h2>\n      <ol>\n        <li><a href=\"#how-api-works\">How an API works step by step<\/a><\/li>\n        <li><a href=\"#request-anatomy\">What is inside a request?<\/a><\/li>\n        <li><a href=\"#methods-status\">Methods and status codes<\/a><\/li>\n        <li><a href=\"#practical-examples\">Four practical examples<\/a><\/li>\n        <li><a href=\"#rest\">API, REST, backend and database<\/a><\/li>\n        <li><a href=\"#fetch\">Call an API with JavaScript<\/a><\/li>\n        <li><a href=\"#devtools\">Inspect a request in DevTools<\/a><\/li>\n        <li><a href=\"#security\">CORS, authentication and security<\/a><\/li>\n        <li><a href=\"#practice\">Beginner practice exercise<\/a><\/li>\n        <li><a href=\"#faq\">Frequently asked questions<\/a><\/li>\n      <\/ol>\n    <\/nav>\n\n    <section class=\"nit-section-panel\" id=\"how-api-works\">\n      <h2>How an API works: follow one student-results request<\/h2>\n      <p>The easiest way to understand a web API is to stop thinking about the term for a moment and follow one feature from the screen to the server and back.<\/p>\n\n      <div class=\"nit-concept-grid\">\n        <article class=\"nit-concept-card\">\n          <h3>1. User action<\/h3>\n          <p>A student who is already signed in presses <strong>View My Results<\/strong>. The frontend detects the click and knows that it needs examination data.<\/p>\n        <\/article>\n        <article class=\"nit-concept-card\">\n          <h3>2. Request<\/h3>\n          <p>The frontend sends a request such as <code>GET \/api\/me\/results<\/code>. The method says what kind of operation is intended; the target identifies what is being requested.<\/p>\n        <\/article>\n        <article class=\"nit-concept-card\">\n          <h3>3. Server work<\/h3>\n          <p>The backend checks the request, identifies the signed-in user, verifies permission, applies business rules and retrieves the permitted records.<\/p>\n        <\/article>\n        <article class=\"nit-concept-card\">\n          <h3>4. Response<\/h3>\n          <p>The server returns a status, headers and\u2014when appropriate\u2014data. The frontend reads the response and turns it into a results table the student can understand.<\/p>\n        <\/article>\n      <\/div>\n\n      <h3>The complete chain<\/h3>\n      <ol class=\"nit-checklist\">\n        <li><strong>The student clicks the button:<\/strong> the browser detects the action.<\/li>\n        <li><strong>The frontend prepares a request:<\/strong> for example <code>GET \/api\/me\/results<\/code>.<\/li>\n        <li><strong>The request reaches the server:<\/strong> HTTP carries the request to the target service.<\/li>\n        <li><strong>The backend validates it:<\/strong> the server checks the request structure and required information.<\/li>\n        <li><strong>Authentication is considered:<\/strong> the system determines who is making the request.<\/li>\n        <li><strong>Authorisation is checked:<\/strong> the system decides what that user is allowed to access.<\/li>\n        <li><strong>Application rules run:<\/strong> for example, whether results have been released.<\/li>\n        <li><strong>Data is retrieved:<\/strong> the backend may query a database or another service.<\/li>\n        <li><strong>The server returns a response:<\/strong> HTTP status, headers and possibly a response body come back.<\/li>\n        <li><strong>The frontend updates the screen:<\/strong> raw data becomes a useful interface.<\/li>\n      <\/ol>\n\n      <div class=\"nit-callout nit-callout--info\">\n        <p class=\"nit-callout__title\">The mental model to keep<\/p>\n        <p><strong>User \u2192 Frontend \u2192 Request \u2192 API\/Backend \u2192 Database or service \u2192 Response \u2192 Frontend.<\/strong> HTTP is built around client requests and server responses; the request method communicates the client&#8217;s intent and the response status communicates the result. <sup><a href=\"#ref-2\">[2]<\/a><\/sup><\/p>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"request-anatomy\">\n      <h2>What is actually inside an API request?<\/h2>\n      <p>\u201cSend a request\u201d sounds abstract until you can read one. A simplified request might look like this:<\/p>\n\n      <div class=\"nit-code-window\" aria-label=\"Example HTTP request\">\n        <div class=\"nit-code-window__bar\">\n          <span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span>\n          <span class=\"nit-code-window__file\">HTTP request<\/span>\n        <\/div>\n        <div class=\"nit-code-window__body\">\n          <span class=\"nit-code-line\"><span class=\"nit-code-keyword\">GET<\/span> <span class=\"nit-code-string\">\/api\/me\/results?term=2<\/span> HTTP\/1.1<\/span>\n          <span class=\"nit-code-line\"><span class=\"nit-code-name\">Accept<\/span>: <span class=\"nit-code-string\">application\/json<\/span><\/span>\n          <span class=\"nit-code-line\"><span class=\"nit-code-name\">Authorization<\/span>: Bearer &lt;token&gt;<\/span>\n        <\/div>\n      <\/div>\n\n      <div class=\"nit-tech-board\">\n        <article class=\"nit-tech-card\"><h3>Method<\/h3><p><code>GET<\/code> expresses the request&#8217;s intended operation. HTTP defines standard method semantics. <sup><a href=\"#ref-2\">[2]<\/a><\/sup><\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Target \/ endpoint<\/h3><p><code>\/api\/me\/results?term=2<\/code> identifies where the request is directed and includes a query string.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Headers<\/h3><p>Headers carry request metadata, such as accepted response formats or credentials used by the application&#8217;s authentication design.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Body<\/h3><p>Some requests also carry content\u2014for example JSON submitted to register a user or create an order.<\/p><\/article>\n      <\/div>\n\n      <h3>Endpoint, path value and query parameter<\/h3>\n      <p>Consider <code>GET \/api\/students\/104\/results?term=2<\/code>.<\/p>\n      <ul class=\"nit-list\">\n        <li><code>\/api\/students\/104\/results<\/code> is the request path.<\/li>\n        <li><code>104<\/code> can be used by an API design as a path value identifying a particular student.<\/li>\n        <li><code>?term=2<\/code> is a query string. Query parameters are often used for filtering, searching, sorting or modifying a request.<\/li>\n      <\/ul>\n      <p>Browser APIs such as <code>URLSearchParams<\/code> provide a standard way to work with URL query strings. <sup><a href=\"#ref-12\">[12]<\/a><\/sup><\/p>\n\n      <h3>What is inside a response?<\/h3>\n      <p>A simplified successful response might contain <code>200 OK<\/code>, a <code>Content-Type: application\/json<\/code> header and a JSON body such as <code>{\"student\":\"Amina\",\"mathematics\":78}<\/code>. JSON is a lightweight, text-based, language-independent data-interchange format. <sup><a href=\"#ref-3\">[3]<\/a><\/sup><\/p>\n    <\/section>\n    <section class=\"nit-section-panel\" id=\"methods-status\">\n      <h2>HTTP methods and status codes beginners should know<\/h2>\n      <p>Do not memorise a huge protocol reference at the start. Learn the methods and response codes you will meet repeatedly, then deepen your knowledge as your applications become more complex.<\/p>\n\n      <h3>Five HTTP methods you will meet often<\/h3>\n      <div class=\"nit-tech-board\">\n        <article class=\"nit-tech-card\">\n          <h3>GET<\/h3>\n          <p><strong>Beginner meaning:<\/strong> Retrieve a resource.<\/p>\n          <p><strong>Example:<\/strong> Read examination results.<\/p>\n          <p><strong>Important nuance:<\/strong> HTTP defines GET as a safe retrieval method, so it should not be used to request state-changing behaviour. <sup><a href=\"#ref-2\">[2]<\/a><\/sup><\/p>\n        <\/article>\n        <article class=\"nit-tech-card\">\n          <h3>POST<\/h3>\n          <p><strong>Beginner meaning:<\/strong> Submit content for processing.<\/p>\n          <p><strong>Example:<\/strong> Submit a registration.<\/p>\n          <p><strong>Important nuance:<\/strong> POST is often used to create resources, but its standard meaning is broader than simply \u201ccreate\u201d.<\/p>\n        <\/article>\n        <article class=\"nit-tech-card\">\n          <h3>PUT<\/h3>\n          <p><strong>Beginner meaning:<\/strong> Create or replace target state.<\/p>\n          <p><strong>Example:<\/strong> Replace stored profile details.<\/p>\n          <p><strong>Important nuance:<\/strong> PUT uses replacement semantics for the target resource.<\/p>\n        <\/article>\n        <article class=\"nit-tech-card\">\n          <h3>PATCH<\/h3>\n          <p><strong>Beginner meaning:<\/strong> Apply a partial modification.<\/p>\n          <p><strong>Example:<\/strong> Change only a phone number.<\/p>\n          <p><strong>Important nuance:<\/strong> PATCH is defined separately from the core RFC 9110 method set.<\/p>\n        <\/article>\n        <article class=\"nit-tech-card\">\n          <h3>DELETE<\/h3>\n          <p><strong>Beginner meaning:<\/strong> Request removal.<\/p>\n          <p><strong>Example:<\/strong> Delete an allowed record.<\/p>\n          <p><strong>Important nuance:<\/strong> The server still has to authenticate, authorise and validate the action.<\/p>\n        <\/article>\n      <\/div>\n      <p>HTTP method semantics are defined by standards rather than by framework conventions alone. <sup><a href=\"#ref-2\">[2]<\/a><\/sup><\/p>\n\n      <h3>Status codes you will meet repeatedly<\/h3>\n      <div class=\"nit-tech-board\">\n        <article class=\"nit-tech-card\"><h3>200 OK<\/h3><p><strong>Meaning:<\/strong> The request succeeded.<\/p><p><strong>Check next:<\/strong> Read and use the returned content.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>201 Created<\/h3><p><strong>Meaning:<\/strong> A new resource was created.<\/p><p><strong>Check next:<\/strong> Review the returned representation or location information.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>400 Bad Request<\/h3><p><strong>Meaning:<\/strong> The request has a client-side problem.<\/p><p><strong>Check next:<\/strong> Inspect input, syntax and required fields.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>401 Unauthorized<\/h3><p><strong>Meaning:<\/strong> Valid authentication credentials are missing.<\/p><p><strong>Check next:<\/strong> Inspect login state, token\/session and authentication flow.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>403 Forbidden<\/h3><p><strong>Meaning:<\/strong> The server refuses the action.<\/p><p><strong>Check next:<\/strong> Inspect the user&#8217;s role and permission.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>404 Not Found<\/h3><p><strong>Meaning:<\/strong> The target resource was not found.<\/p><p><strong>Check next:<\/strong> Inspect the route, identifier and whether the resource exists.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>405 Method Not Allowed<\/h3><p><strong>Meaning:<\/strong> That method is not allowed for the target.<\/p><p><strong>Check next:<\/strong> Confirm whether the endpoint expects GET, POST, PATCH or another method.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>429 Too Many Requests<\/h3><p><strong>Meaning:<\/strong> Requests are arriving too frequently.<\/p><p><strong>Check next:<\/strong> Respect the API&#8217;s rate limits and retry guidance.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>500 Internal Server Error<\/h3><p><strong>Meaning:<\/strong> The server encountered an unexpected failure.<\/p><p><strong>Check next:<\/strong> Inspect server-side logs and processing if you control the backend.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>503 Service Unavailable<\/h3><p><strong>Meaning:<\/strong> The service is temporarily unable to handle the request.<\/p><p><strong>Check next:<\/strong> Check availability and retry policy rather than assuming user input is wrong.<\/p><\/article>\n      <\/div>\n      <p>RFC 9110 defines HTTP response status classes and codes, including the distinction between authentication-related 401 responses and access-refusal 403 responses. <sup><a href=\"#ref-2\">[2]<\/a><\/sup><\/p>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"practical-examples\">\n      <h2>Four practical examples of APIs in real applications<\/h2>\n      <p>The definition becomes easier when you can recognise the same request-response pattern in different systems.<\/p>\n\n      <div class=\"nit-project-grid\">\n        <article class=\"nit-project-card\" data-project=\"01\">\n          <h3>Student results portal<\/h3>\n          <p>A student clicks <strong>View Results<\/strong>. The frontend requests the signed-in student&#8217;s records; the backend checks identity and permission, obtains the records and returns them.<\/p>\n          <span class=\"nit-project-status\">Internal web API<\/span>\n        <\/article>\n        <article class=\"nit-project-card\" data-project=\"02\">\n          <h3>Online shop order<\/h3>\n          <p>The frontend submits product and quantity information. The backend validates the request, checks stock and pricing, applies rules, creates the order and sends the outcome back.<\/p>\n          <span class=\"nit-project-status\">Business workflow<\/span>\n        <\/article>\n        <article class=\"nit-project-card\" data-project=\"03\">\n          <h3>Application login<\/h3>\n          <p>The browser submits credentials to a login endpoint. The backend verifies the account and returns success or failure. The visible form is only one part of authentication.<\/p>\n          <span class=\"nit-project-status\">Authentication flow<\/span>\n        <\/article>\n        <article class=\"nit-project-card\" data-project=\"04\">\n          <h3>M-PESA integration<\/h3>\n          <p>A Kenyan application&#8217;s backend can communicate with Safaricom&#8217;s Daraja platform to integrate M-PESA payment functionality into web or mobile applications. <sup><a href=\"#ref-9\">[9]<\/a><\/sup><\/p>\n          <span class=\"nit-project-status\">External API<\/span>\n        <\/article>\n      <\/div>\n\n      <div class=\"nit-callout nit-callout--success\">\n        <p class=\"nit-callout__title\">Internal API vs external API<\/p>\n        <p>An internal API can connect components controlled by the same organisation. An external API lets your application communicate with another organisation&#8217;s service. In both cases, software interacts through a defined interface.<\/p>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"rest\">\n      <h2>API vs backend vs database\u2014and where REST fits<\/h2>\n      <div class=\"nit-tech-board\">\n        <article class=\"nit-tech-card\"><h3>Frontend<\/h3><p>Presents information, collects user interaction and decides when it needs to request or submit data.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>API<\/h3><p>Defines how another software component can request permitted data or functionality.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Backend<\/h3><p>Runs server-side logic, validation, permissions, integrations, background work and database operations.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Database<\/h3><p>Stores and retrieves persistent information such as users, results, products, payments or orders.<\/p><\/article>\n      <\/div>\n\n      <div class=\"nit-callout nit-callout--warning\">\n        <p class=\"nit-callout__title\">Three misconceptions to remove early<\/p>\n        <p><strong>API \u2260 database.<\/strong> A database stores data. <strong>API \u2260 backend.<\/strong> The API can be one interface to a larger backend. <strong>API \u2260 REST.<\/strong> REST is one architectural style used for networked systems.<\/p>\n      <\/div>\n\n      <h3>What is REST?<\/h3>\n      <p><strong>REST<\/strong> stands for Representational State Transfer. Roy Fielding introduced REST as an architectural style defined by constraints for distributed hypermedia systems, not merely as \u201can API that uses GET and POST\u201d. <sup><a href=\"#ref-6\">[6]<\/a><\/sup><\/p>\n      <p>Many APIs described as RESTful organise their interface around resources and use HTTP methods to interact with those resources. For example, <code>GET \/api\/students\/104<\/code> can retrieve one student while <code>PATCH \/api\/students\/104<\/code> can request a partial change.<\/p>\n      <p>Also remember: <strong>REST does not mean JSON.<\/strong> JSON is a data format; REST is an architectural style.<\/p>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"fetch\">\n      <h2>How frontend JavaScript calls an API<\/h2>\n      <p>Seeing a real call makes the architecture less abstract. Modern browsers provide the Fetch API for making network requests.<\/p>\n\n      <div class=\"nit-code-window\" aria-label=\"JavaScript fetch API example\">\n        <div class=\"nit-code-window__bar\">\n          <span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span>\n          <span class=\"nit-code-window__file\">load-results.js<\/span>\n        <\/div>\n        <div class=\"nit-code-window__body\">\n          <span class=\"nit-code-line\"><span class=\"nit-code-keyword\">async function<\/span> <span class=\"nit-code-name\">loadResults<\/span>() {<\/span>\n          <span class=\"nit-code-line nit-code-line--indent\"><span class=\"nit-code-keyword\">try<\/span> {<\/span>\n          <span class=\"nit-code-line nit-code-line--indent2\"><span class=\"nit-code-keyword\">const<\/span> response = <span class=\"nit-code-keyword\">await<\/span> fetch(<span class=\"nit-code-string\">&quot;\/api\/results&quot;<\/span>);<\/span>\n          <span class=\"nit-code-line nit-code-line--indent2\"><span class=\"nit-code-keyword\">if<\/span> (!response.ok) <span class=\"nit-code-keyword\">throw new<\/span> Error(response.status);<\/span>\n          <span class=\"nit-code-line nit-code-line--indent2\"><span class=\"nit-code-keyword\">const<\/span> data = <span class=\"nit-code-keyword\">await<\/span> response.json();<\/span>\n          <span class=\"nit-code-line nit-code-line--indent2\">console.log(data);<\/span>\n          <span class=\"nit-code-line nit-code-line--indent\">} <span class=\"nit-code-keyword\">catch<\/span> (error) {<\/span>\n          <span class=\"nit-code-line nit-code-line--indent2\">console.error(<span class=\"nit-code-string\">&quot;Could not load results&quot;<\/span>, error);<\/span>\n          <span class=\"nit-code-line nit-code-line--indent\">}<\/span>\n          <span class=\"nit-code-line\">}<\/span>\n        <\/div>\n      <\/div>\n\n      <div class=\"nit-concept-grid\">\n        <article class=\"nit-concept-card\"><h3><code>fetch()<\/code><\/h3><p>Starts a network request to the supplied resource.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3><code>await<\/code><\/h3><p>Lets the async function wait for the promise to settle before using the result.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3><code>response.ok<\/code><\/h3><p>Provides a convenient check for HTTP success status in the 200\u2013299 range.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3><code>response.json()<\/code><\/h3><p>Reads the response body and parses it as JSON.<\/p><\/article>\n      <\/div>\n\n      <div class=\"nit-callout nit-callout--success\">\n        <p class=\"nit-callout__title\">A beginner trap worth remembering<\/p>\n        <p><code>fetch()<\/code> does not automatically reject its promise just because the server returned an HTTP error such as 404 or 500. Your code should inspect the response status or <code>response.ok<\/code>. <sup><a href=\"#ref-4\">[4]<\/a><\/sup><\/p>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"devtools\">\n      <h2>See an API request yourself with Browser DevTools<\/h2>\n      <p>This is the practical exercise that turns an API from an idea into something you can observe. Use a site or application you are authorised to inspect.<\/p>\n      <ol class=\"nit-checklist\">\n        <li><strong>Open Chrome DevTools:<\/strong> use the browser menu or the platform keyboard shortcut.<\/li>\n        <li><strong>Open the Network panel:<\/strong> network requests are recorded while DevTools is open.<\/li>\n        <li><strong>Reload the page:<\/strong> watch the request list populate.<\/li>\n        <li><strong>Perform an action:<\/strong> open a dashboard, search or use a non-sensitive feature in your own practice application.<\/li>\n        <li><strong>Filter for Fetch\/XHR where useful:<\/strong> many API calls from frontend JavaScript appear there.<\/li>\n        <li><strong>Select one request:<\/strong> inspect its URL, method, status and initiator.<\/li>\n        <li><strong>Inspect Headers:<\/strong> see request and response metadata.<\/li>\n        <li><strong>Inspect Payload:<\/strong> see submitted data where the request carries it.<\/li>\n        <li><strong>Inspect Response:<\/strong> see what the server returned.<\/li>\n        <li><strong>Inspect Timing:<\/strong> see how long different parts of the request took.<\/li>\n      <\/ol>\n      <p>Chrome&#8217;s official documentation describes the Network panel as a tool for recording and inspecting network activity, including request headers, responses and timing. <sup><a href=\"#ref-8\">[8]<\/a><\/sup><\/p>\n\n      <h3>A simple API debugging sequence<\/h3>\n      <div class=\"nit-career-grid\">\n        <article class=\"nit-career-card\"><h3>1. Was a request sent?<\/h3><p>If nothing appears in Network, investigate the frontend event or code path first.<\/p><\/article>\n        <article class=\"nit-career-card\"><h3>2. Was the target correct?<\/h3><p>Check the URL and HTTP method before assuming the server or database is broken.<\/p><\/article>\n        <article class=\"nit-career-card\"><h3>3. What came back?<\/h3><p>Use the status code, response body and headers as evidence instead of guessing.<\/p><\/article>\n        <article class=\"nit-career-card\"><h3>4. What failed behind it?<\/h3><p>If you control the backend, continue into server logs, application logic, database queries and external-service calls.<\/p><\/article>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"security\">\n      <h2>CORS, authentication, authorisation and API secrets<\/h2>\n      <p>Security terms often arrive all at once when a beginner starts connecting a frontend to a backend. Keep each concept separate.<\/p>\n\n      <h3>What is CORS?<\/h3>\n      <p>If frontend JavaScript at one origin requests an API at another origin, browser same-origin rules can apply. <strong>CORS<\/strong>\u2014Cross-Origin Resource Sharing\u2014is an HTTP-header-based mechanism through which a server indicates which other origins a browser may allow to access its resources. <sup><a href=\"#ref-5\">[5]<\/a><\/sup><\/p>\n      <div class=\"nit-callout nit-callout--info\">\n        <p class=\"nit-callout__title\">CORS is enforced by browsers<\/p>\n        <p>A CORS error does not automatically mean the API server is offline. A browser may be refusing scripted cross-origin access because the response lacks the required CORS permission. Server-to-server calls are not subject to browser CORS enforcement in the same way. Do not \u201cfix\u201d CORS by blindly allowing every origin; permit only what the application requires. <sup><a href=\"#ref-5\">[5]<\/a><\/sup><\/p>\n      <\/div>\n\n      <h3>Authentication vs authorisation<\/h3>\n      <div class=\"nit-concept-grid\">\n        <article class=\"nit-concept-card\"><h3>Authentication<\/h3><p><strong>Who are you?<\/strong> The system establishes the identity associated with the request.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3>Authorisation<\/h3><p><strong>What may you do?<\/strong> The system checks whether that identity is allowed to perform this action on this resource.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3>HTTPS<\/h3><p><strong>Protect the connection.<\/strong> HTTPS helps protect data in transit, but it does not replace application permission checks.<\/p><\/article>\n        <article class=\"nit-concept-card\"><h3>API credentials<\/h3><p><strong>Protect secrets deliberately.<\/strong> A private key, consumer secret or server-side credential should not be shipped inside public browser code.<\/p><\/article>\n      <\/div>\n      <p>OWASP&#8217;s REST security guidance recommends HTTPS for secure REST services, access-control checks at protected endpoints, restricting allowed methods and careful API-key handling. <sup><a href=\"#ref-7\">[7]<\/a><\/sup><\/p>\n\n      <div class=\"nit-callout nit-callout--warning\">\n        <p class=\"nit-callout__title\">Knowing a record ID is not permission<\/p>\n        <p>If someone requests <code>\/api\/students\/104\/results<\/code>, the backend must not return the record merely because Student 104 exists. It must verify that the requester is authorised to receive it.<\/p>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"failure-docs\">\n      <h2>What good frontend code does when an API is slow or fails<\/h2>\n      <p>Network operations are not guaranteed to succeed immediately. A request can fail because connectivity is lost, the server is unavailable, the request is invalid, authentication expired, permission is missing or another dependency failed.<\/p>\n      <div class=\"nit-tech-board\">\n        <article class=\"nit-tech-card\"><h3>Loading<\/h3><p>Tell the user that work is happening. Avoid leaving the interface looking frozen.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Success<\/h3><p>Show the returned information or confirm that the requested operation completed.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Error<\/h3><p>Give a useful message and preserve enough evidence for the developer to trace the failure.<\/p><\/article>\n        <article class=\"nit-tech-card\"><h3>Retry<\/h3><p>Where appropriate, let the user retry without accidentally duplicating state-changing operations.<\/p><\/article>\n      <\/div>\n\n      <h3>How to read API documentation without getting lost<\/h3>\n      <ol class=\"nit-checklist\">\n        <li><strong>Start with one task:<\/strong> for example \u201cretrieve one student&#8217;s details\u201d.<\/li>\n        <li><strong>Find the base address and endpoint:<\/strong> where should the request go?<\/li>\n        <li><strong>Check the method:<\/strong> GET, POST, PATCH, DELETE or something else?<\/li>\n        <li><strong>Check authentication:<\/strong> session, token, key or another credential?<\/li>\n        <li><strong>Check path and query parameters:<\/strong> which IDs or filters are required?<\/li>\n        <li><strong>Check headers and request body:<\/strong> what must the client send?<\/li>\n        <li><strong>Read the successful response example:<\/strong> what structure should come back?<\/li>\n        <li><strong>Read the error responses:<\/strong> what do common failure codes mean for this API?<\/li>\n        <li><strong>Check limits and rules:<\/strong> rate limits, allowed methods and provider-specific requirements.<\/li>\n      <\/ol>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"practice\">\n      <h2>Beginner practice: design a small API on paper<\/h2>\n      <p>You do not need to build a huge application to practise API thinking. Imagine a small school system with students, courses, enrolments and results.<\/p>\n\n      <div class=\"nit-table-wrap\">\n        <table class=\"nit-table\">\n          <thead><tr><th scope=\"col\">Request<\/th><th scope=\"col\">What it should mean<\/th><th scope=\"col\">Question you must answer<\/th><\/tr><\/thead>\n          <tbody>\n            <tr><th scope=\"row\"><code>GET \/api\/students<\/code><\/th><td>Retrieve the student collection<\/td><td>Who is allowed to list students?<\/td><\/tr>\n            <tr><th scope=\"row\"><code>GET \/api\/students\/104<\/code><\/th><td>Retrieve Student 104<\/td><td>What happens if the record does not exist?<\/td><\/tr>\n            <tr><th scope=\"row\"><code>POST \/api\/students<\/code><\/th><td>Submit data for a new student<\/td><td>Which fields are required and validated?<\/td><\/tr>\n            <tr><th scope=\"row\"><code>PATCH \/api\/students\/104<\/code><\/th><td>Change part of Student 104<\/td><td>Which roles may edit this record?<\/td><\/tr>\n            <tr><th scope=\"row\"><code>GET \/api\/students\/104\/results<\/code><\/th><td>Retrieve this student&#8217;s results<\/td><td>How will the server prevent another student from reading them?<\/td><\/tr>\n          <\/tbody>\n        <\/table>\n      <\/div>\n      <p class=\"nit-table-note\">On a phone, swipe the table sideways to view every column.<\/p>\n\n      <div class=\"nit-callout nit-callout--success\">\n        <p class=\"nit-callout__title\">The exercise is not about memorising URLs<\/p>\n        <p>For each operation, decide who may call it, what must be sent, what can come back, what should happen when something is wrong and which evidence would help you debug it. That is the beginning of application architecture.<\/p>\n      <\/div>\n\n      <h3>A short learning order<\/h3>\n      <p>Learn HTML and CSS first, then JavaScript fundamentals, JSON and asynchronous JavaScript. Use <code>fetch()<\/code>, understand HTTP requests and responses, then build your own backend endpoints, connect a database and add authentication, authorisation and testing. For the broader journey, see NIT&#8217;s <a href=\"https:\/\/niteducation.com\/resources\/how-to-become-a-web-developer-in-kenya\/\">Web Developer Roadmap<\/a>.<\/p>\n    <\/section>\n\n    <section class=\"nit-section-panel\" id=\"nit-context\">\n      <h2>Where APIs fit in full-stack development<\/h2>\n      <p>A full-stack developer needs to understand how the layers connect. A student-registration feature can move through an interface, API route, validation, business logic, database write, response and final screen update.<\/p>\n      <p>NIT&#8217;s current Full-Stack Software Development programme connects frontend work with server-side development, databases, APIs, authentication, testing and deployment. The current programme has <strong>8 months of institutional training<\/strong>, followed by a <strong>compulsory industrial attachment of at least 3 months<\/strong>, with current published tuition of <strong>KSh 90,000<\/strong>. No previous programming experience is required. <sup><a href=\"#ref-10\">[10]<\/a><\/sup><\/p>\n      <p>NIT&#8217;s institutional website also documents student capstone work involving a React frontend, Node.js\/Express backend API, database integration and API integration\u2014practical examples of the same frontend-to-backend concepts described in this guide. <sup><a href=\"#ref-11\">[11]<\/a><\/sup><\/p>\n\n      <div class=\"nit-action-strip\">\n        <p>Want the career-path comparison rather than the communication mechanism?<\/p>\n        <div class=\"nit-action-strip__buttons\">\n          <a class=\"nit-button nit-button--secondary\" href=\"https:\/\/niteducation.com\/resources\/front-end-vs-back-end-vs-full-stack-in-kenya\/\">Front-End vs Back-End vs Full-Stack<\/a>\n          <a class=\"nit-button nit-button--secondary\" href=\"https:\/\/niteducation.com\/resources\/how-to-become-a-web-developer-in-kenya\/\">Web Developer Roadmap<\/a>\n        <\/div>\n      <\/div>\n    <\/section>\n\n    <section id=\"faq\" aria-labelledby=\"faq-title\">\n      <h2 id=\"faq-title\">API FAQs for beginners<\/h2>\n      <div class=\"nit-faq\">\n        <details class=\"nit-faq__item\"><summary>What does API stand for?<\/summary><div class=\"nit-faq__answer\"><p>API stands for <strong>Application Programming Interface<\/strong>.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>What is an API in simple terms?<\/summary><div class=\"nit-faq__answer\"><p>An API is a defined interface that lets one piece of software request data or functionality from another.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>What is an API in web development?<\/summary><div class=\"nit-faq__answer\"><p>In web development, an API commonly gives a frontend, backend or external service a structured way to exchange data or request actions over a network.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Is an API a programming language?<\/summary><div class=\"nit-faq__answer\"><p>No. An API is an interface. APIs can be created and used from many programming languages.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Is an API the same as a backend?<\/summary><div class=\"nit-faq__answer\"><p>No. An API can be part of a backend, while the backend may also contain business logic, background jobs, database access, file processing and other services.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Is an API a database?<\/summary><div class=\"nit-faq__answer\"><p>No. A database stores data. An API defines how software may request data or actions.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Does every website need an API?<\/summary><div class=\"nit-faq__answer\"><p>No. Static sites may not need one, and traditional server-rendered applications can work without a separate JSON API for the browser. APIs become especially useful when different clients or software systems need structured communication.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Does every API use HTTP or JSON?<\/summary><div class=\"nit-faq__answer\"><p>No. This guide focuses on web APIs, where HTTP and JSON are common. The broader API concept is not restricted to HTTP, and JSON is not the only possible data format.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Is every web API REST?<\/summary><div class=\"nit-faq__answer\"><p>No. REST is one architectural style. Other approaches exist.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Can HTML send data without JavaScript?<\/summary><div class=\"nit-faq__answer\"><p>Yes. An HTML form can submit data directly to a server. JavaScript is especially useful when an application needs programmatic network requests and partial interface updates.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Can a backend call another API?<\/summary><div class=\"nit-faq__answer\"><p>Yes. The API client does not have to be a browser. One backend can call payment, mapping, messaging, weather or other internal and external services.<\/p><\/div><\/details>\n        <details class=\"nit-faq__item\"><summary>Can I see API requests in my browser?<\/summary><div class=\"nit-faq__answer\"><p>Yes. Chrome DevTools includes a Network panel that records requests and lets you inspect properties such as status, headers, response content and timing. <sup><a href=\"#ref-8\">[8]<\/a><\/sup><\/p><\/div><\/details>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-pg-enrol\" aria-labelledby=\"enrol-title\">\n      <div class=\"nit-pg-enrol__copy\">\n        <p class=\"nit-pg-eyebrow\">Learn the complete workflow<\/p>\n        <h2 id=\"enrol-title\">Register for Full-Stack Software Development at NIT<\/h2>\n        <p>Learn how to build the interface, create the backend, design and use APIs, connect databases, control access, test complete workflows and deploy working applications.<\/p>\n      <\/div>\n      <div class=\"nit-pg-enrol__details\" aria-label=\"Full-Stack Software Development course details\">\n        <p><span>Institutional training<\/span><strong>8 months<\/strong><\/p>\n        <p><span>Industrial attachment<\/span><strong>At least 3 months<\/strong><\/p>\n        <p><span>Current published tuition<\/span><strong>KSh 90,000<\/strong><\/p>\n      <\/div>\n      <div class=\"nit-pg-enrol__actions\">\n        <a class=\"nit-pg-button nit-pg-button--gold\" href=\"https:\/\/niteducation.com\/admissions\/\">Register \/ Apply<\/a>\n        <a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/wa.me\/254713584858?text=Hello%20Newton%20Institute%20of%20Technology.%20I%20would%20like%20information%20about%20the%20Full-Stack%20Software%20Development%20Course.\" target=\"_blank\" rel=\"noopener\">Ask on WhatsApp<\/a>\n        <a class=\"nit-pg-button nit-pg-button--outline\" href=\"mailto:info@niteducation.com?subject=Full-Stack%20Software%20Development%20Enquiry\">Email Admissions<\/a>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-sources\" aria-labelledby=\"references-title\">\n      <h2 id=\"references-title\">References and further reading<\/h2>\n      <ul>\n        <li id=\"ref-1\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Glossary\/API\" rel=\"noopener\" target=\"_blank\">[1] MDN Web Docs \u2014 API glossary<\/a>. Definition and broader scope of APIs.<\/li>\n        <li id=\"ref-2\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9110.html\" rel=\"noopener\" target=\"_blank\">[2] RFC 9110 \u2014 HTTP Semantics<\/a>. Primary standards source for HTTP request methods, response status codes and core request-response semantics.<\/li>\n        <li id=\"ref-3\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8259.html\" rel=\"noopener\" target=\"_blank\">[3] RFC 8259 \u2014 The JSON Data Interchange Format<\/a>. Primary standards source for JSON.<\/li>\n        <li id=\"ref-4\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/Window\/fetch\" rel=\"noopener\" target=\"_blank\">[4] MDN Web Docs \u2014 Window: fetch()<\/a>. Browser Fetch API and HTTP-error handling behaviour.<\/li>\n        <li id=\"ref-5\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Guides\/CORS\" rel=\"noopener\" target=\"_blank\">[5] MDN Web Docs \u2014 Cross-Origin Resource Sharing (CORS)<\/a>. Browser cross-origin request behaviour and CORS headers.<\/li>\n        <li id=\"ref-6\"><a href=\"https:\/\/ics.uci.edu\/~fielding\/pubs\/dissertation\/abstract.htm\" rel=\"noopener\" target=\"_blank\">[6] Roy T. Fielding \u2014 Architectural Styles and the Design of Network-based Software Architectures<\/a>. Primary academic source for REST.<\/li>\n        <li id=\"ref-7\"><a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/REST_Security_Cheat_Sheet.html\" rel=\"noopener\" target=\"_blank\">[7] OWASP Cheat Sheet Series \u2014 REST Security<\/a>. HTTPS, access control, method restriction and API-key guidance.<\/li>\n        <li id=\"ref-8\"><a href=\"https:\/\/developer.chrome.com\/docs\/devtools\/network\/overview\" rel=\"noopener\" target=\"_blank\">[8] Chrome for Developers \u2014 Network panel<\/a>. Inspecting browser network requests, responses, headers and timing.<\/li>\n        <li id=\"ref-9\"><a href=\"https:\/\/developer.safaricom.co.ke\/\" rel=\"noopener\" target=\"_blank\">[9] Safaricom Developers \u2014 Daraja 3.0<\/a>. Official M-PESA API integration platform.<\/li>\n        <li id=\"ref-10\"><a href=\"https:\/\/niteducation.com\/resources\/full-stack-software-development-course\/\">[10] Newton Institute of Technology \u2014 Full-Stack Software Development Course<\/a>. Current programme structure, tuition and beginner-entry information.<\/li>\n        <li id=\"ref-11\"><a href=\"https:\/\/niteducation.com\/about\">[11] Newton Institute of Technology \u2014 About \/ Built By Our Students<\/a>. Institutional examples of student frontend, backend API and database work.<\/li>\n        <li id=\"ref-12\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/URLSearchParams\" rel=\"noopener\" target=\"_blank\">[12] MDN Web Docs \u2014 URLSearchParams<\/a>. Browser interface for working with URL query strings.<\/li>\n      <\/ul>\n      <p><strong>Information checked:<\/strong> 31 October 2026.<\/p>\n      <p><strong>Editorial responsibility:<\/strong> Newton Institute of Technology Editorial Team.<\/p>\n    <\/section>\n  <\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>Web Development Guide Basics What Is an API?How Frontend and Backend Communicate Frontend \u00b7 API \u00b7 Backend Follow one web request from the screen to the server and back, then inspect the same request yourself in the browser. Follow one request Inspect it in DevTools The communication route Frontend API Backend Request goes in. Response [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[30],"tags":[771,770],"class_list":["post-3720","post","type-post","status-publish","format-standard","hentry","category-ict","tag-how-does-frontend-connect-to-backend","tag-what-is-an-api-in-web-development"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3720","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/comments?post=3720"}],"version-history":[{"count":1,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3720\/revisions"}],"predecessor-version":[{"id":3721,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3720\/revisions\/3721"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3720"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3720"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3720"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}