Connect Lovable or Base44 to Web2Application Push (API Guide)

Who this is for: builders on Lovable or Base44 who already have (or will create) a Web2Application mobile app and want to send push notifications from their AI-built web app.

This page documents a limited connector surface only — enough for Lovable/Base44 to integrate, without publishing internal APIs, Firebase keys, or server details.

Security rules (read first)

• Use only a connector API key from your Web2Application dashboard (starts with w2a_live_).
• Never put the key in frontend code, Git, or VITE_ variables. In Lovable: store it under Cloud → Secrets.
• Never paste Firebase keys, WordPress Application Passwords, or database credentials into Lovable/Base44.
• The key is bound to one app you own. It cannot control other customers’ apps.
• Only the endpoints listed below are supported for this integration.

Before you start

1. Create your mobile app in Web2Application from your Lovable/Base44 website URL (free APK test available).
2. Confirm a test push works from the Web2Application dashboard.
3. Create a connector key: open your app → Integration / API keys (integration-keys) → create key → copy it once.
4. For personal push: capture the user email inside the app (Listeners) so the email is linked to a device.

Limited API surface

Base URL: https://web2application.com/w2a/integrations/v1

Auth header: X-Api-Key: w2a_live_…

OpenAPI (for Base44 import): https://web2application.com/w2a/integrations/openapi/push-v1.json

Lovable — copy this prompt

1. Enable Cloud in your Lovable project.
2. Cloud → Secrets → add WEB2APP_API_KEY = your connector key.
3. Paste the prompt below into Lovable chat.

Integrate Web2Application push securely via Cloud Edge Function (never expose the API key to the browser).

OpenAPI (limited public surface): https://web2application.com/w2a/integrations/openapi/push-v1.json
Base URL: https://web2application.com/w2a/integrations/v1
Auth: HTTP header X-Api-Key from Cloud secret WEB2APP_API_KEY.

Allowed endpoints only:
1) GET /me.php — verify connected app
2) POST /push/user.php — JSON { email, title, body, link?, image_url? }
3) POST /push/broadcast.php — JSON { title, body, link?, image_url? }
4) POST /push/emails.php — JSON { emails: string[], title, body, link?, image_url? } (max 50)

Create an Edge Function proxy that reads WEB2APP_API_KEY server-side and a simple UI to:
- Test connection (me.php)
- Send personal push
- Send broadcast push

Do not request Firebase keys, WordPress keys, or any other endpoints. Do not log or display the API key.

Base44 — Custom Integration (OpenAPI)

1. Workspace admin → Settings → Integrations → New Integration.
2. Import OpenAPI from URL: https://web2application.com/w2a/integrations/openapi/push-v1.json
3. Select the four operations (me + three push endpoints).
4. Add header X-Api-Key with your connector key (stored as a workspace secret).
5. In your app, call via base44.integrations.custom.call(...) as documented by Base44.

Example request bodies

Personal push

{{
  "email": "[email protected]",
  "title": "Hello",
  "body": "Your order is ready"
}

Broadcast

{{
  "title": "Update",
  "body": "New content is available"
}

FAQ

Will Lovable/Base44 users find us automatically?

Not until an official catalog connector exists. Share this guide / prompt. Official marketplace listings (Make, Zapier, and partner programs) increase discovery.

Why is the API documentation limited?

On purpose. Builders only need push + connection check. Broader internal APIs are not published here.

Personal push returned success but no phone alert

The email must be linked to a device in the app. Re-open the app, capture the email again, then retry.

Lovable / Base44 → native app overview · Make.com push guide · Free course