LMU Net APIlmunet.edu ↗
Extract published email addresses and surrounding context from LMU web pages. Returns address, label, section heading, and contact card text via one endpoint.
What is the LMU Net API?
The lmunet.edu API exposes one endpoint, get_page_emails, that returns every published email address found on an LMU web page along with 8 structured fields per contact — including the email address itself, its inline label, the surrounding sentence or contact card text, and the nearest section heading. By default it targets the Lincoln Memorial University DVM admissions page, making it straightforward to extract admissions contact information in structured form.
curl -X GET 'https://api.parse.bot/scraper/7f150461-35bd-4598-9a8d-bbda0524fc5e/get_page_emails?page_path=%2Fcollege-of-veterinary-medicine%2Fprofessional-program%2Fadmissions%2F&email=VeterinaryAdmissions%40LMUnet.edu' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns every published email link on one LMU web page together with its exact surrounding text: the section heading (or contact-card title) it appears under, an inline label such as 'Email:' when one precedes it, and the full sentence, list item, or contact card containing it. One row per occurrence, in page order, so the same address appears several times when the page mentions it in several places (casing is preserved as published). Defaults to the College of Veterinary Medicine DVM admissions page; any other page on the same site can be targeted by its path. A single request per call. A page with no email links returns an empty contacts list; a path the site reports as 'Page Not Found' returns a stale_input error.
| Param | Type | Description |
|---|---|---|
| string | Restrict results to this one email address (case-insensitive match). Omitted = all email links on the page. | |
| page_path | string | Site-relative path of the LMU page to scan, starting with '/'. |
{
"type": "object",
"fields": {
"contacts": "array of email occurrences in page order",
"page_url": "full URL of the scanned page",
"page_title": "page H1 heading",
"contacts[].email": "address as published (casing preserved)",
"contacts[].label": "inline bold label preceding the address (e.g. 'Email:'), null when none",
"total_email_links": "integer count of all email links on the page before any email filter",
"contacts[].link_text": "visible text of the email link",
"contacts[].context_text": "exact text of the sentence, list item, or contact card containing the address",
"contacts[].section_heading": "nearest preceding heading, or the contact-card title when the address sits in a contact card"
},
"sample": {
"data": {
"contacts": [
{
"email": "[email protected]",
"label": null,
"link_text": "[email protected]",
"context_text": "If you have extenuating circumstances that require changing your preferred start term during the application cycle, please contact [email protected] .",
"section_heading": "DVM Application Process"
},
{
"email": "[email protected]",
"label": "Email:",
"link_text": "[email protected]",
"context_text": "Request More Information Email: [email protected]",
"section_heading": "Request More Information"
}
],
"page_url": "https://www.lmunet.edu/college-of-veterinary-medicine/professional-program/admissions/",
"page_title": "Doctor of Veterinary Medicine",
"total_email_links": 5
},
"status": "success"
}
}About the LMU Net API
What the API Returns
The single get_page_emails endpoint scans an LMU web page and returns a contacts array, one entry per email link found, in page order. Each entry includes email (address as published, casing preserved), label (the bold inline label preceding the address, e.g. Email:, or null when none exists), link_text (the visible hyperlink text), context_text (the full sentence, list item, or contact card containing the address), and section_heading (the nearest preceding heading or contact-card title). The response also includes page_url, page_title (the H1 of the scanned page), and total_email_links (a count of all email links before any filtering).
Input Parameters
get_page_emails accepts two optional inputs. The page_path parameter takes a site-relative path starting with /, allowing you to target any LMU page beyond the default DVM admissions page — for example /financial-aid/contact/ or /registrar/. The email parameter accepts a single address and restricts the contacts array to occurrences of that address (case-insensitive), while total_email_links still reflects the full unfiltered count.
Practical Details
Because section_heading and context_text are always returned together, you can distinguish between contacts even when multiple email addresses share the same page — for instance, separating an admissions coordinator from a financial aid contact. The label field captures structured patterns like Email: or Contact: that appear as inline bold text, giving you a reliable anchor when building display UIs or populating CRM fields without having to parse free-form text yourself.
The LMU Net API is a managed, monitored endpoint for lmunet.edu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when lmunet.edu changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official lmunet.edu API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Pull DVM admissions contact emails and their section headings into a prospective-student CRM
- Monitor the LMU admissions page for new or changed email addresses over time
- Build a staff directory overlay by collecting contact cards across multiple LMU department pages via
page_path - Validate that published email addresses on specific LMU pages match expected institutional patterns
- Extract inline labels (
Email:,Contact:) alongside addresses to auto-populate structured contact databases - Identify which section heading each admissions contact belongs to, without manually parsing page HTML
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Lincoln Memorial University provide an official developer API for its website data?+
What does the `contacts` array distinguish that a plain email list would not?+
contacts returns up to five fields per address: the raw email, the inline label (e.g. 'Email:'), the visible link_text, the full context_text of the surrounding sentence or card, and the section_heading under which the address appears. This lets you tell apart contacts on the same page — for example an admissions coordinator listed under 'Prospective Students' versus a financial aid contact listed under 'Tuition & Fees' — without post-processing.Can I scan pages other than the DVM admissions page?+
page_path parameter (e.g. /college-of-veterinary-medicine/faculty/) to scan a different page. Omitting the parameter defaults to the DVM admissions page.Does the API cover phone numbers or mailing addresses listed on LMU pages?+
email, label, context_text, section_heading, and link_text. Phone numbers and physical mailing addresses are not extracted. You can fork the API on Parse and revise it to add those fields.How fresh is the data returned for a given page path?+
page_path will pick up any changes LMU has made to that page.