Install Jentic One Beta

Connect the Enquiry Tracker Partner API to your agent

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fenquirytracker.net%2Fenquirytracker" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fenquirytracker.net%2Fenquirytracker" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Enquiry Tracker Partner 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

Start building with Enquiry Tracker Partner API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Enquiry Tracker Partner 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 your Jentic One instance. 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.

Key Endpoints

11 endpoints — enquiry tracker is an admissions crm used by independent and international schools to manage enquiries, applications, and student records.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Enquiry Tracker Partner 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 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.

Enquiry Tracker Partner API

Name: Enquiry Tracker Partner API
Brand: Enquiry Tracker Partner API
Availability: InStock

Official vendor OpenAPI document · agent-readyEducationStudent Managementbearer11 EndpointsREST

For Agents

Read student, contact, and enquiry data from the Enquiry Tracker admissions CRM and push new enquiries or request document and export packages.

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.

Jentic One on Github View OpenAPI Document

Connect the Enquiry Tracker Partner API to your agent

Capabilities

Start building with Enquiry Tracker Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Enquiry Tracker Partner API