Tamu APIvetmed.tamu.edu ↗
Retrieve Texas A&M CVM DVM admissions contact emails, staff directory, roles, and program inquiry lines in a single API call.
What is the Tamu API?
The Texas A&M Vet Med Admissions API exposes 1 endpoint — get_admissions_contacts — returning 5 structured fields covering the DVM Professional Program's primary admissions mailbox, staff directory with exact role titles, general-inquiry contact lines, and footer email presence. It consolidates contact data from both the admissions and contact pages into one response, giving applications a reliable source for current program staff names, emails, and labeled roles.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/15a53c10-2270-4ca8-bd8b-fe0449d31491/get_admissions_contacts' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace vetmed-tamu-edu-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Texas A&M VMBS DVM Admissions Contacts — fetch and explore."""
from parse_apis.vetmed_tamu_edu_api import VetMed, ParseError
client = VetMed()
# Fetch the full contact directory in one call.
try:
directory = client.contact_directory.get()
except ParseError as e:
print("Extraction failed:", e.code)
raise
# Primary admissions mailbox.
print(directory.admissions_email.role, directory.admissions_email.email,
directory.admissions_email.phone)
# Staff cards — filter to admissions-related contacts.
for member in directory.staff:
if member.admissions_related:
print(member.name, "|", member.role, "|", member.email)
# General-inquiry lines (some fields nullable).
if directory.general_inquiries is not None:
for inquiry in directory.general_inquiries:
phone = inquiry.phone or "n/a"
print(inquiry.label, phone)
# Mailto links scraped from the admissions page.
for link in directory.admissions_page_email_links:
print(link.link_label, "->", link.email)
print("exercised: contact_directory.get")
Returns the publicly listed DVM admissions contact email and related program contacts in one call (two page loads: the DVM 'Apply Now!' admissions page and the DVM 'Contact Us' page). admissions_email is the primary admissions mailbox with the exact role label the site publishes for it ('Admissions & Application') and its phone number. admissions_page_email_links lists every mailto link found in the body of the admissions page with its link text. footer_contact_emails holds any email addresses found in the site footer (the footer currently contains only navigation and social links, so this list is normally empty and footer_has_contact_email is false). general_inquiries lists each line of the Contact Us 'General Inquiries' section (label, email, phone; email/phone are null when that line has none). staff lists every DVM Professional Program staff card with name, exact role title, unit, email, profile_url (null when no profile link exists) and an admissions_related flag that is true when the role title mentions admissions. No input parameters; an empty staff list is not expected.
No input parameters required.
{
"type": "object",
"fields": {
"staff": "array of DVM Professional Program staff cards: name, role (exact title), unit, email, profile_url (nullable), admissions_related (boolean)",
"admissions_email": "object: the primary admissions mailbox with email, role (site's published label) and phone",
"general_inquiries": "array of Contact Us general-inquiry lines: label, email (nullable), email_link_text (nullable), phone (nullable)",
"footer_contact_emails": "array of email strings found in the site footer (normally empty)",
"footer_has_contact_email": "boolean: whether the footer contains any email address",
"admissions_page_email_links": "array of mailto links from the admissions page body: email, link_label, source_page"
},
"sample": {
"data": {
"staff": [
{
"name": "Jane Doe",
"role": "Assistant Dean for Professional Programs Admissions",
"unit": "DVM Professional Program | VMBS",
"email": "[email protected]",
"profile_url": "https://vetmed.tamu.edu/person/1532/",
"admissions_related": true
},
{
"name": "John Doe",
"role": "Admissions Coordinator",
"unit": "DVM Professional Program | VMBS",
"email": "[email protected]",
"profile_url": "https://vetmed.tamu.edu/person/22923/",
"admissions_related": true
}
],
"admissions_email": {
"role": "Admissions & Application",
"email": "[email protected]",
"phone": "+1 (555) 012-3456"
},
"general_inquiries": [
{
"email": null,
"label": "DVM Professional Program Office",
"phone": "+1 (555) 012-3456",
"email_link_text": null
},
{
"email": "[email protected]",
"label": "Admissions & Application",
"phone": "+1 (555) 012-3456",
"email_link_text": "[email protected]"
}
],
"footer_contact_emails": [],
"footer_has_contact_email": false,
"admissions_page_email_links": [
{
"email": "[email protected]",
"link_label": "Questions? Email DVM Admissions!",
"source_page": "admissions"
}
]
},
"status": "success"
}
}About the Tamu API
What the Endpoint Returns
The get_admissions_contacts endpoint returns a single JSON object covering all publicly listed contact points for the Texas A&M College of Veterinary Medicine & Biomedical Sciences DVM Professional Program. The admissions_email field contains the primary admissions mailbox as the site labels it, including the published role name and associated phone number. The staff array delivers one card per DVM Professional Program staff member, each with name, role (exact title as published), unit, email, profile_url (null when not listed), and an admissions_related flag to help callers filter staff relevant to the application process.
Additional Contact Fields
The general_inquiries array mirrors the Contact Us page's general-inquiry section, with each entry carrying a label, optional email, optional email_link_text, and optional phone. The admissions_page_email_links array lists every mailto link found in the admissions page body, each annotated with email, link_label, and source_page — useful for catching any secondary contact addresses that appear inline. Two footer fields, footer_contact_emails and footer_has_contact_email, confirm whether any email address is present in the site footer; normally both return empty and false.
Coverage Scope
All inputs are optional; the endpoint takes no parameters and always returns the full contact set. Response freshness reflects the current published state of the admissions and contact pages. The API covers only publicly visible contact information — application portals, deadlines, prerequisite requirements, and enrolled student data are not included.
The Tamu API is a managed, monitored endpoint for vetmed.tamu.edu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when vetmed.tamu.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 vetmed.tamu.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?+
- Auto-populate a veterinary school application tracker with the current DVM admissions email and phone number.
- Monitor the
staffarray for changes in DVM admissions personnel and role titles over time. - Build a pre-vet advising tool that surfaces the correct program contact using the
admissions_relatedflag. - Sync the
general_inquiriescontact lines into a CRM or advising platform for prospective students. - Audit published contact consistency by comparing
admissions_email,admissions_page_email_links, andfooter_contact_emailsin one call. - Populate a veterinary school directory with verified staff names, exact role titles, and profile URLs from the
staffarray.
| 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 Texas A&M Vet Med have an official developer API for admissions data?+
How does the `admissions_related` flag on staff cards work?+
staff array includes an admissions_related boolean. It is set based on whether the staff member's published role or unit indicates direct involvement with the DVM admissions process. Use it to filter the full staff list down to contacts most relevant to application inquiries.Does the API return DVM application deadlines, prerequisites, or program statistics?+
What does `footer_has_contact_email` indicate, and when is it true?+
footer_contact_emails is an empty array, since the program's contact emails are in the page body rather than the footer. If the site layout changes and an email is added to the footer, both fields will update accordingly.