Implementing Browser Extension Integration with Server REST API

Integrating a browser extension with a REST API is a routine but treacherous task. Common issues include CORS errors, authentication problems, and data loss in offline mode. We specialize in such integrations: over the years, we have completed more than 40 projects with extensions for Chrome, Firefox, and Edge. We've built CRM extensions, data collection tools, and web assistants. We offer a turnkey solution in 4–6 business days.

Key Problems Solved

• CORS and CSP: Without proper server configuration, extensions cannot make any requests. The server must whitelist the extension's origin.
• Authentication and token refresh: Tokens expire quickly; without automatic refresh, the extension stops working.
• Offline mode and synchronization: Users may lose connection while filling data; without an offline queue, data is lost.
• Manifest V3 limitations: Service workers have a short lifespan and no DOM access.

Case Study

We once worked on a CRM extension that synchronized contacts. The original implementation did not handle 401 errors — after token expiration, the extension stopped working until reinstallation. We implemented a refresh token, added an offline queue, and properly configured CORS on the server (Laravel 11). The result: synchronization speed increased 2x, and failures dropped to zero.

Why Proper CORS and Offline Handling Matter

The server must allow origins like chrome-extension:// and moz-extension://. Without it, no request succeeds. Offline mode is critical: a user may fill in data and lose connection. Without an offline queue, data disappears. We use the executeOrQueue pattern: on fetch failure, the request is saved to chrome.storage.local; on startup or reconnection, the queue is flushed.

const PENDING_ACTIONS_KEY = 'pending_actions';

async function executeOrQueue(action) {
  try {
    await fetch(action.url, action.options);
  } catch (error) {
    const pending = (await chrome.storage.local.get(PENDING_ACTIONS_KEY))[PENDING_ACTIONS_KEY] || [];
    pending.push({ ...action, queued_at: Date.now() });
    await chrome.storage.local.set({ [PENDING_ACTIONS_KEY]: pending });
  }
}

chrome.runtime.onStartup.addListener(flushPendingActions);

Secure Authentication

The access token is stored in chrome.storage.local (not localStorage, which is inaccessible to Service Worker). On each fetch, we add headers Authorization: Bearer <token> and X-Extension-Version. In the Service Worker, we must return true for async responses.

chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
  if (message.action === 'save_item') {
    saveItemToServer(message.data)
      .then(result => sendResponse({ success: true, data: result }))
      .catch(err => sendResponse({ success: false, error: err.message }));
    return true;
  }
});

async function saveItemToServer(itemData) {
  const token = await getStoredToken();
  const resp = await fetch('https://api.example.com/v1/items', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': 'Bearer ' + token,
      'X-Extension-Version': chrome.runtime.getManifest().version,
    },
    body: JSON.stringify(itemData),
  });
  if (!resp.ok) {
    if (resp.status === 401) await refreshToken();
    throw new Error(`API error: ${resp.status}`);
  }
  return resp.json();
}

Synchronization Approaches Comparison

The choice depends on requirements. Chrome Storage Sync is suitable for basic settings but does not guarantee server delivery. Server sync gives full control but requires a constant connection. The hybrid approach combines local storage speed with background sync reliability. We recommend it for most projects.

Typical Mistakes and Solutions

Our Work Process

1. Analysis: Study server API, extension specifics, synchronization requirements.
2. Design: Choose architecture (Repository, BFF), request schemas, token storage.
3. Implementation: Write Service Worker, content script, configure CORS, add offline queue.
4. Testing: Emulate offline, token changes, load testing.
5. Deployment: Publish to Chrome Web Store / Firefox Add-ons, monitor errors.

What's Included

• Integration architecture design accounting for extension constraints.
• Implementation of Service Worker, content script, and server side (CORS middleware, auth endpoints).
• Setup of offline queue and automatic synchronization.
• Integration documentation (request schemas, endpoint descriptions).
• Assistance with publishing to extension stores.
• 30-day integration warranty — free bug fixes.

Timeline and CTA

Turnkey integration takes 4–6 business days. Pricing is custom after analysis. Get a consultation — we'll assess your task within one business day. Order integration today and eliminate sync issues. Contact us — we'll explain how to cut development time and reduce maintenance costs.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.