canonical: https://jentic.com/apis/enquirytracker.net/enquirytracker # Enquiry Tracker Partner API 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. ## For AI agents Read student, contact, and enquiry data from the Enquiry Tracker admissions CRM and push new enquiries or request document and export packages. ## Scope 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. ## Capabilities - 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 - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance. Multi-step asynchronous flows like requestStudentExport plus checkRequest are easy to compose. Example prompt: Search Jentic for 'create an enquiry in Enquiry Tracker', load POST /?action=populateEnquiry, and execute it with the captured prospect details. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/?action=getKeyInfo` | Verify the API key and return its scope | | GET | `/?action=getSchoolInfo` | Return school metadata | | GET | `/?action=getStudents` | Retrieve student records | | POST | `/?action=getStudentsFields` | List the available student field definitions | | POST | `/?action=getContacts` | Fetch contact records | | POST | `/?action=populateEnquiry` | Create a new enquiry | | POST | `/?action=requestApplicationDocuments` | Request an application document package | | POST | `/?action=checkRequest` | Poll the status of an asynchronous request | ## Key resources - **School and Key Info** — Verify the API key and read the attached school identifier and metadata. - **Students** — Retrieve student records and discover the available student field definitions. - **Contacts** — Fetch family and applicant contact records. - **Enquiries** — Populate new enquiry records in the admissions pipeline. - **Document and Export Requests** — Asynchronous request endpoints for application documents, student exports, and transfers, with a status-check endpoint. ## Why Jentic - **Setup:** Wiring Enquiry Tracker by hand means handling its bearer-token auth and its action-style calling convention, where the operation rides in an action query parameter rather than a REST path. Through Jentic you install once, import the Enquiry Tracker Partner API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** Enquiry Tracker selects the operation through an action query parameter rather than a resource in the URL path, so scope the agent to the operations it needs, such as reading students or populating an enquiry. You pick that allowed set, so an action like requesting application documents is only reachable if you include it. - **Credential handling:** Your Enquiry Tracker bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an enquiry in Enquiry Tracker' or 'list students', and Jentic returns the matching action with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **HubSpot** — General-purpose CRM repurposed for some school admissions teams - **Salesforce** — Education Cloud and Salesforce CRM as a heavyweight admissions alternative - **Calendly** — Schedule school tours and admissions interviews from a captured enquiry ## FAQ ### 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 your Jentic One instance 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Enquiry Tracker Partner API? Yes. The Enquiry Tracker Partner API selects each operation through an action query parameter rather than a resource path, and because Jentic One is self-hosted your own rules decide which of those actions the agent may call. You choose the allowed set, so you can grant read-only actions like getStudents and getContacts while withholding others. An action such as requestApplicationDocuments or populateEnquiry is only reachable by the agent if you include it, and the stored bearer token is injected at execution time rather than exposed to the agent.