For Agents
Read student, contact, and enquiry data from the Enquiry Tracker admissions CRM and push new enquiries or request document and export packages.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Enquiry Tracker Partner API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Enquiry Tracker Partner API API.
Retrieve school and API key information to verify the partner integration is correctly scoped
Pull student records along with their available custom fields for synchronisation with a SIS
Fetch contact records associated with families and applicants
Push a new enquiry into Enquiry Tracker via the populateEnquiry action
GET STARTED
Use for: Get the school information attached to my Enquiry Tracker API key, Retrieve all students from Enquiry Tracker for a specific school year, List the available student field definitions before requesting an export, Push a new enquiry into Enquiry Tracker from our marketing landing page
Not supported: Does not handle finance, fee billing, or LMS course delivery — use for school admissions enquiries, student and contact records, and document and export requests only.
Enquiry Tracker is an admissions CRM used by independent and international schools to manage enquiries, applications, and student records. The Partner API exposes school-side integration points for retrieving school and key information, fetching student and contact records, populating new enquiries, requesting application document packages, and orchestrating asynchronous student exports and transfers. The 11 endpoints are designed for partner systems such as student information systems and marketing platforms that need to read or push admissions data into the Enquiry Tracker pipeline.
Request application document packages for an applicant for downstream review
Initiate a student export or student transfer job and poll its status with checkRequest
Discover the available student fields before building an export payload
Patterns agents use Enquiry Tracker Partner API API for, with concrete tasks.
★ Marketing Form to Admissions Enquiry
Capture web enquiries on a school website and push them into Enquiry Tracker via POST /?action=populateEnquiry so admissions staff see new prospects in their normal pipeline view. The integration eliminates manual re-keying from form notification emails. Most schools wire this up with a single serverless function in under a day.
Submit POST /?action=populateEnquiry with the prospective family's name, email, year-of-entry, and source 'website-info-pack-form'.
SIS Synchronisation
Synchronise student and contact records from Enquiry Tracker into a school's student information system by polling POST /?action=getStudents and POST /?action=getContacts on a schedule. Use POST /?action=getStudentsFields first to discover which custom fields the school maintains so the SIS schema can be aligned before each pull.
Call POST /?action=getStudentsFields to load the schema, then POST /?action=getStudents and stage the rows for the SIS upsert.
Application Document Package Retrieval
Admissions teams trigger document package generation with POST /?action=requestApplicationDocuments to assemble PDFs and forms for a specific applicant. The request is asynchronous, so the integration polls POST /?action=checkRequest with the returned request ID until the package is ready to download. Common in workflows that bundle review packs before an admissions committee meeting.
Submit POST /?action=requestApplicationDocuments for applicantId 4471, then poll POST /?action=checkRequest until status is 'ready'.
AI Agent Admissions Assistant Through Jentic
An AI assistant for admissions teams uses Jentic to discover Enquiry Tracker operations by intent and answers staff questions like 'how many enquiries did we receive last week?' or pushes a new enquiry from a chat conversation. The bearer token stays in the Jentic vault. Multi-step asynchronous flows like requestStudentExport plus checkRequest are easy to compose.
Search Jentic for 'create an enquiry in Enquiry Tracker', load POST /?action=populateEnquiry, and execute it with the captured prospect details.
11 endpoints — enquiry tracker is an admissions crm used by independent and international schools to manage enquiries, applications, and student records.
METHOD
PATH
DESCRIPTION
/?action=getKeyInfo
Verify the API key and return its scope
/?action=getSchoolInfo
Return school metadata
/?action=getStudents
Retrieve student records
/?action=getStudentsFields
List the available student field definitions
/?action=getContacts
Fetch contact records
/?action=populateEnquiry
Create a new enquiry
/?action=requestApplicationDocuments
Request an application document package
/?action=checkRequest
Poll the status of an asynchronous request
/?action=getKeyInfo
Verify the API key and return its scope
/?action=getSchoolInfo
Return school metadata
/?action=getStudents
Retrieve student records
/?action=getStudentsFields
List the available student field definitions
/?action=getContacts
Fetch contact records
Three things that make agents converge on Jentic-routed access.
Credential isolation
Enquiry Tracker bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents call /?action=populateEnquiry, /?action=getStudents, and /?action=requestApplicationDocuments through scoped tokens — the partner bearer token never enters the agent context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create an enquiry in Enquiry Tracker') and receive the matching action-style endpoint with its input schema, so the agent calls the right action parameter without parsing the developer documentation.
Time to first call
Direct Enquiry Tracker integration: 1-2 days for auth, sync, and the request-then-poll flow on document and export endpoints. Through Jentic: under an hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
HubSpot
General-purpose CRM repurposed for some school admissions teams
Choose HubSpot only when the school has standardised on it and does not need school-specific fields. Use Enquiry Tracker when the workflow expects admissions-specific concepts like applicants, year-of-entry, and document packages.
Salesforce
Education Cloud and Salesforce CRM as a heavyweight admissions alternative
Pick Salesforce when the school needs broad customisation across the institution. Stick with Enquiry Tracker for a focused admissions pipeline with a much smaller integration surface.
Calendly
Schedule school tours and admissions interviews from a captured enquiry
Use Calendly after creating an enquiry in Enquiry Tracker to book a tour with admissions staff.
Specific to using Enquiry Tracker Partner API API through Jentic.
What authentication does the Enquiry Tracker Partner API use?
The Enquiry Tracker Partner API uses HTTP bearer token authentication. Each request must include an Authorization header with the partner bearer token issued by Enquiry Tracker. Through Jentic, the token is stored in the vault (MAXsystem) and injected at execution time so it never enters the agent context.
How do I create a new enquiry through the Enquiry Tracker API?
Call POST /?action=populateEnquiry with the prospective family's details. The endpoint writes a new enquiry into the admissions pipeline so staff see it alongside enquiries captured directly in Enquiry Tracker.
Are the export and document endpoints synchronous?
No. requestStudentExport and requestApplicationDocuments are asynchronous — they return a request identifier that you pass to POST /?action=checkRequest to poll until the job is ready. Plan the integration as a request-then-poll workflow.
What are the rate limits for the Enquiry Tracker API?
The OpenAPI spec does not publish explicit rate limits. Enquiry Tracker applies fair-use limits at the partner-account level; if you need to run high-volume sync jobs, schedule them off-peak and contact Enquiry Tracker partner support for guidance.
How do I sync student records to a SIS through Jentic?
Search Jentic for 'list students from Enquiry Tracker', load POST /?action=getStudents, and execute it on a schedule into the SIS upsert flow. Pair with POST /?action=getStudentsFields to discover the schema first. Get started at https://app.jentic.com/sign-up.
Can I see the custom student fields a school has configured?
Yes. POST /?action=getStudentsFields returns the field definitions including custom fields, so partner systems can discover the school's schema before requesting student data.
/?action=populateEnquiry
Create a new enquiry
/?action=requestApplicationDocuments
Request an application document package
/?action=checkRequest
Poll the status of an asynchronous request