Platform Architecture & API Reference
Learn how LifeWithAMission works, how to submit URLs, and how to use our free REST API.
1. Platform Overview
LifeWithAMission is a completely free, open-source alternative to commercial backlink indexers. It runs natively on WordPress and is engineered to operate within the limits of Hostinger Shared Hosting (PHP 8.2+, MySQL 8.0+).
2. Legitimate URL Discovery
Unlike legacy tools that abuse the Google Indexing API (restricted by Google to JobPosting and BroadcastEvent metadata), LifeWithAMission submits to legitimate discovery channels: XML Sitemaps, RSS 2.0/Atom feeds, internal link traversal, and IndexNow.
3. Backlink Verification
When you submit a list of published backlinks, our queue worker fetches the target web page, stream-parses the DOM, and extracts:
- Whether the target link href actually exists.
- The exact anchor text associated with the link.
- Rel attributes: dofollow, nofollow, ugc, or sponsored.
- Page-level robots directives and X-Robots-Tag headers.
4. Bing IndexNow Protocol
IndexNow is an open protocol adopted by Bing, Yandex, Naver, and Seznam. By verifying your domain ownership using an API key hosted at your domain root, URLs are submitted instantly to all participating search engines upon publication or update.
5. Free Developer REST API
Our REST API is available under namespace /wp-json/lwam/v1/. All requests use Bearer API keys generated in your dashboard.
| Method | Endpoint | Description |
|---|---|---|
| GET | /system/status |
Returns platform health, version, and database state |
| GET | /user/profile |
Returns authenticated user info and submission quotas |
| GET | /user/projects |
List projects owned by the authenticated user |
| POST | /user/projects |
Create a new project for campaign organization |
| GET | /user/campaigns |
List campaigns and processing metrics |
6. SSRF & Security Shield
To protect our shared hosting environment, all outbound crawling requests pass through our enterprise SSRF Guard. Loopback (127.0.0.1), private subnets (10.0.0.0/8, 192.168.0.0/16), and cloud metadata endpoints (169.254.169.254) are strictly rejected with zero socket creation.