⚡ Neuro-surgery in progress. We ship live.
Live Case Study
M
MealShift

Building MealShift's API Developer Portal

Turning a 10-page PDF into a professional developer experience for mealshift.co.uk - the UK's flexible, fair food delivery platform

Client: Said Ziane, Founder | Started: 25 Mar 2026, 14:56 UTC | Phase 1 Complete - Active Project
0h 0m 0s
Builder: Yossra Benzad | Engine: ElektraOS
Overview

Project scope

What

Turn a 10-page PDF into a professional developer portal

Who

MealShift - UK-based food delivery platform

Deliverables

Developer docs portal, OpenAPI 3.x spec, end-to-end examples

Scope

11 endpoints (9 REST + 2 webhooks)

Progress

Phase dashboard

✓
Research
Analyzed PDF, studied Flipdish portal
✓
Design
Architecture decisions, page structure
✓
Build
Docs portal, OpenAPI spec
✓
Encrypt
AES-256 encryption, password protection
✓
Deploy
GitHub Pages, handoff to client
⚙
Integration
API integration planning, system mapping
Build Log

Live timeline - every step, every decision

Your clock = Yossra's instruction time  |  Build clock = ElektraOS processing time

14:56 UTC Client Brief your clock: 16 min
Said Ziane shared the project scope via WhatsApp: MealShift API PDF (10 pages), requirement spec (AI-generated from Perplexity), and Flipdish developer portal as reference.
WhatsApp PDF
15:12 UTC Research build: 3 min
3 parallel research tasks: (1) Audit elektraos.dev site structure and case study patterns, (2) Review ElektraOS backend for project tracking infrastructure, (3) Analyze Flipdish developer portal + attempt MealShift PDF download (S3 link expired).
ElektraOS 3x Explore Agents WebFetch
15:15 UTC Research build: 1 min
Parsed MealShift API PDF locally via pypdf (ElektraOS venv). Extracted 12,123 characters across 10 pages. Confirmed 11 endpoints: 9 REST + 2 webhooks. Stored in ElektraOS vault as structured brief.
pypdf ElektraOS Vault WSL/Python
15:18 UTC Design your clock: 2 min
Security architecture decision. 3 options evaluated: (1) Private GitHub repo, (2) Local build + encrypt before push, (3) ElektraOS vault + encrypted output. Chose Option 3 - source files never leave local machine. Only AES-256 encrypted HTML deployed.
ElektraOS Architecture Decision
15:20 UTC Design build: 4 min
Designed full implementation plan: 4 phases, file structure, encryption workflow, ElektraOS integration, deployment pipeline.
Plan Agent ElektraOS
15:25 UTC Research build: 1 min
Fetched MealShift branding from mealshift.co.uk. Extracted: primary green #FF5362, logo PNG URL, tagline "Flexible, fair, food delivery!", company info (est. 2020, Hertfordshire).
WebFetch WebSearch
15:27 UTC Build build: 8 min
Phase 1 foundation: Created directory structure, set up mealshift-docs-builder module in ElektraOS, created project directory, parsed PDF into vault/projects/mealshift/brief.md.
ElektraOS SQLite Vault
15:30 UTC Build build: 4 min
Built this live workplan page. MealShift branding integrated (coral #FF5362, logo). Dual clock system (your time vs build time). Real-time elapsed timer. Phase dashboard. Architecture diagram.
ElektraOS HTML/CSS/JS
15:35 UTC Design your clock: 1 min
Brand color correction. WebFetch returned green (#18a300) from a button class - wrong. Visual inspection of mealshift.co.uk confirmed actual brand is coral red (#FF5362). Fixed across all files.
Chrome Visual Audit
15:40 UTC Security build: 5 min
Full security audit across ElektraOS. Fixed 4 HIGH severity issues: disabled /docs /redoc /openapi.json exposure (was leaking 387KB API blueprint), tightened CORS to localhost+elektraos.dev only, minimized health endpoint, disabled telemetry content capture.
Security Agent ElektraOS cURL
15:50 UTC Security build: 3 min
Sandboxed Elektra chat for this page. Removed external JS dependencies (chat.js, sigil3d.js) that connected to ElektraOS backend. Replaced with inline FAQ-only chat. Zero external API connections. Said cannot access any system outside this page.
ElektraOS PageCrypt
16:00 UTC Build build: 10 min
Generated complete OpenAPI 3.0.3 specification from parsed PDF. All 11 endpoints documented with full request/response schemas, 8 reusable component schemas, realistic UK example data (London addresses, GBP currency). Stored in ElektraOS vault.
OpenAPI 3.0.3 YAML Vault
16:10 UTC Build build: 4 min
Built developer portal using Redoc with custom dark theme. MealShift coral (#FF5362) as primary, ElektraOS dark backgrounds. Stripe-style two-panel layout: explanations left, code samples right. Spec embedded inline - fully self-contained.
Redoc HTML/CSS OpenAPI
16:15 UTC Encrypt build: 1 min
AES-256 encrypted the docs portal via PageCrypt. Source HTML (57KB) never touches GitHub. Only encrypted output deployed. Verified: zero secrets in public repo, _src/ gitignored, robots.txt blocks crawlers.
PageCrypt AES-256 Git
16:20 UTC Deploy build: 2 min
Pushed encrypted HTML to GitHub Pages. Verified AES-256 access works. Passkey shared with client via WhatsApp. Case study card added to /cases/ portfolio with metrics, tags, and encrypted access badge.
GitHub Pages PageCrypt Git
Session 2 - March 26, 2026
10:00 UTC Integration build: 12 min
Audited MealShift's existing tech stack. No public repo - private codebase built by CookieDev. Stack: WordPress (marketing), Fuse React dashboard, native iOS/Android apps, Stripe Connect, Google Maps. 7 integration partners confirmed: Deliverect, Otter, Foodhub, Nash, GloriaFood, Flipdish. UrbanPiper coming soon.
WebSearch GitHub Chrome
10:15 UTC Integration build: 8 min
Designed API integration strategy for MealShift's existing systems. 4 integration paths mapped: (1) POS middleware - single endpoint for Lightspeed/Square/Epos Now, (2) Partner onboarding automation - self-serve API key generation + sandbox, (3) Webhook relay layer - centralized status tracking across all 7 partners, (4) White-label SDK - embeddable JS client for restaurant chains. Pending Said's review.
ElektraOS Architecture Planning
10:30 UTC Build build: 5 min
Upgraded sandboxed FAQ chat to live ElektraOS-connected assistant. Said can now submit real feedback that reaches Yossra. Groq LLM + vault RAG responses replace static keyword matching. Email fallback button added. Client-side FAQ retained as offline fallback.
ElektraOS API Groq JavaScript
Session 3 - March 26, 2026 (afternoon)
14:00 UTC Integration 3 parallel research tracks: 15 min
Deep research into MealShift's full ecosystem. 3 parallel tracks: (1) Platform research - found zero-commission model, 20+ UK cities, CookieDev build, Stripe Connect payments, (2) API audit - mapped all 11 endpoints, auth flow, webhook system, (3) Partner analysis - confirmed 7 live integrations with Deliverect, Flipdish, GloriaFood, Otter, Nash, Foodhub, UrbanPiper. No public API docs exist anywhere - all integrations manual via email.
Web Research Chrome Bitbucket Trustpilot
14:20 UTC Integration build: 20 min
Designed 6-phase API integration roadmap. Phase 1: Developer onboarding portal (self-serve keys). Phase 2: Webhook relay with normalized events across 7 partners. Phase 3: POS middleware for Lightspeed/Square/Epos Now. Phase 4: White-label delivery SDK (npm + PyPI). Phase 5: Real-time tracking + analytics API. Phase 6: API gateway + multi-region scaling. Each phase scoped with ElektraOS vs CookieDev responsibility split.
ElektraOS Architecture
14:45 UTC Build build: 10 min
Built interactive approval pipeline on case study page. Said can expand phase details, select priorities via checkboxes, and submit selections to Yossra for scoping. Client interactions (chat, approvals, page views) are logged to the timeline in real time via localStorage. Nothing gets built until Yossra approves.
JavaScript localStorage PageCrypt
Architecture

Build pipeline

Source
PDF (10 pages)
→
Parser
pypdf
→
Structure
JSON Schema
→
Output
HTML Portal + OpenAPI 3.x
↓
Secure
AES-256 Encrypt
↓
Deploy
GitHub Pages
Decisions

Why we chose what we chose

Why single-page docs?

Simpler encryption, instant navigation, better search. No page-to-page transitions. The entire portal lives in one encrypted file.

Why AES-256?

PageCrypt encrypts entire HTML. Content invisible in source, network tab, and GitHub repo. Zero server-side requirements.

Why ElektraOS vault?

Source files never leave the local machine. Only encrypted output is deployed. Maximum security for client data.

Why dark theme?

Developers prefer dark. Matches ElektraOS design system. Reduces eye strain during long reading sessions.

Integration Roadmap

6-phase plan to scale MealShift's API ecosystem

Based on deep research of MealShift's stack (CookieDev backend, 7 integration partners, native apps, Stripe, WordPress). Click any phase to expand details. Said - select the phases you want built and send for approval below.

✓
API Foundation
Developer Portal
2
Webhook Relay
3
POS Middleware
4
SDK & Widget
5
Tracking & Analytics
6
Gateway & Scale

Phase 0: API Foundation

Complete

OpenAPI 3.0.3 specification with 11 endpoints documented. Redoc developer portal with MealShift branding. AES-256 encrypted deployment. Pushed to Bitbucket for merge into mealshift.co.uk/docs/.

11 endpoints 8 schemas Delivered Mar 25-26
OpenAPI 3.0.3RedocPageCryptGitHub Pages

Phase 1: Developer Onboarding Portal

Recommended Next

Self-service API key generation at developers.mealshift.co.uk. Replaces the current email-based onboarding (partnerships@mealshift.co.uk) with automated credential provisioning. Partner dashboard showing usage, webhook health, and active restaurant clients.

ElektraOS builds Portal frontend, partner dashboard UI, sandbox environment, interactive documentation
CookieDev handles Key generation backend endpoint, integration with MealShift's core auth system, database migrations
Timeline: 4-6 weeks Revenue: onboarding drops from days to 10 min
Next.jsPostgreSQLOAuth 2.0Cloudflare

Phase 2: Webhook Relay and Monitoring

Planned

Centralized webhook ingestion from all 7 partners (Deliverect, Flipdish, GloriaFood, Otter, Nash, Foodhub, UrbanPiper). Normalized event schema with one adapter per partner. Retry logic with exponential backoff, dead letter queue for failed deliveries, and event replay for debugging.

ElektraOS builds Adapter layer, normalization schemas, monitoring dashboard, DLQ logic, replay API
CookieDev handles Integration with existing webhook processing, Redis/SQS infrastructure provisioning
Timeline: 3-4 weeks Revenue: prevents lost orders, cuts support load
Redis StreamsAdapter PatternGrafanaHMAC-SHA256

Phase 3: POS Middleware Layer

Planned

Single integration point for UK POS systems: Lightspeed, Square, Epos Now, TouchBistro. Order flow: POS fires order webhook, middleware translates to MealShift schema, requests quote, publishes order. Opens MealShift to 50,000+ UK restaurants that have POS but no aggregator.

ElektraOS builds Middleware service, POS connector adapters, JSON translation layer, configuration UI
CookieDev handles Core order API modifications for POS-originated orders, driver assignment logic
Timeline: 6-8 weeks (2 wks per connector) Revenue: 50K+ new restaurant connections
Node.js FastifyLightspeed APISquare APIEpos Now API

Phase 4: White-Label Delivery SDK

Planned

JavaScript SDK (@mealshift/delivery-sdk on npm) and Python SDK (mealshift on PyPI). Embeddable delivery widget for restaurant websites - single script tag, configurable colors and logo. Branded tracking page with real-time driver location. Auto-generated from the OpenAPI spec we already built.

ElektraOS builds Both SDKs, embeddable widget, tracking page, npm/PyPI publishing pipeline, documentation
CookieDev handles WebSocket endpoint for real-time tracking, CORS configuration, CDN hosting for widget
Timeline: 4-6 weeks Revenue: SaaS per restaurant or per-order fee
TypeScriptnpmPyPIPydanticWebSocket

Phase 5: Real-Time Tracking and Analytics API

Planned

WebSocket-based live driver tracking with 5-second GPS updates. Analytics API endpoints for delivery volume, partner performance, cost optimization, and geographic demand heatmap. Internal dashboard for MealShift ops team.

ElektraOS builds Analytics API design + docs, dashboard UI, tracking page frontend, OpenAPI spec extension
CookieDev handles WebSocket server, driver app GPS streaming, TimescaleDB schema, GPS data pipeline
Timeline: 6-8 weeks Revenue: premium tier analytics for enterprise partners
Socket.ioRedis Pub/SubTimescaleDBHeatmap.js

Phase 6: API Gateway and Multi-Region

Planned

Production-grade API gateway with rate limiting per partner and configurable tiers. API versioning strategy with 12-month deprecation lifecycle. Multi-region architecture: UK first, then EU (Ireland), then global. API marketplace listings on RapidAPI and Postman for partner discovery.

ElektraOS builds Gateway config, rate limiting policies, versioning strategy, marketplace listings, docs
CookieDev handles Backend deployment in new regions, database replication, driver app region support
Timeline: 8-12 weeks Revenue: EU market access, usage-based billing
Kong / AWS API GWCloudflareRapidAPIMulti-region

Said, which phases should we build?

Select the phases you want to prioritize. We will scope and timeline them based on your selection. Nothing gets built until you approve.

Your selection will be emailed to Yossra for scoping. You can also use the chat below.
Metrics

By the numbers

11/11
Endpoints Documented
3
Build Sessions
0h 0m
Total Build Time
6
Files Created
6
Integration Phases
7
Partner Adapters
Deliverable

API Developer Portal

11 endpoints documented with Redoc, interactive examples, and a downloadable OpenAPI 3.0.3 spec. Same passkey as this page.

OPEN API DOCS
Download OpenAPI Spec (YAML)
Stack

Tools used

ElektraOS ElektraOS pypdf Prism.js PageCrypt OpenAPI 3.x GitHub Pages
This workplan updates live during build sessions. Powered by ElektraOS.
Elektra
AI Assistant - MealShift Project
✉ Email
Hey Said! Big update: we designed a 6-phase integration roadmap for MealShift's API - developer portal, webhook relay, POS middleware, white-label SDK, real-time tracking, and API gateway. Scroll to the Integration Roadmap section, review each phase, and select the ones you want built. Nothing starts until you approve. Use the checkboxes + Send button, or chat with me here.
Elektra AI Assistant

Hey Said! 6-phase integration roadmap is ready. Scroll to Integration Roadmap, review each phase, select your priorities, and send for approval. Nothing gets built until you approve.