Spectrumemp Liaison API
✓ Official Vendor SpecEducationLmsapiKey6 EndpointsREST
For Agents
Programmatically get form field requirements, submit a form. Covers 6 operations with apiKey authentication.
Use for: I need to form field requirements, I want to submit a form, Search for submittable forms, Find all all field rule dependencies
Not supported: Does not handle payments, communications, or crm - use for education only.
Liaison (Spectrum EMP) API for managing student enrollment forms, field rules, and student sources. Supports form submission, field requirement retrieval, and source management. The API exposes 6 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Liaison API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Liaison 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.
1
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%2Fspectrumemp.com%2Fspectrumemp" | sh2
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%2Fspectrumemp.com%2Fspectrumemp" | 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.
Capabilities
What an agent can do with Liaison API.
Get form field requirements
Submit a form
List student sources
Query and filter Liaison API records by parameters
Monitor Liaison API operational status and events
Use Cases
Patterns agents use Liaison API for, with concrete tasks.
★ Education Operations
Use the Liaison API to perform education operations programmatically. The API provides 6 endpoints covering core functionality including get form field requirements, submit a form, get submittable forms.
Call GET /forms/requirements to get form field requirements
Automated Field Rules Management
Automate field rules operations by combining multiple Liaison API endpoints. Agents can submit a form and then get submittable forms in a single workflow.
Call POST /forms/submit to submit a form, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Liaison API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get form field requirements', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
6 endpoints — liaison (spectrum emp) api for managing student enrollment forms, field rules, and student sources.
METHOD
PATH
DESCRIPTION
GET
/forms/requirements
Get form field requirements
POST
/forms/submit
Submit a form
GET
/forms/submittable
Get submittable forms
GET
/field_rules/all_client_rules
Get all field rule dependencies
POST
/field_rules/field_options
Get dependent field options (deprecated)
GET
/sources/list
List student sources
GET
/forms/requirements
Get form field requirements
POST
/forms/submit
Submit a form
GET
/forms/submittable
Get submittable forms
GET
/field_rules/all_client_rules
Get all field rule dependencies
POST
/field_rules/field_options
Get dependent field options (deprecated)
GET
/sources/list
List student sources
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Liaison API by hand means passing your key as the IQS-API-KEY query parameter on every request and wiring the form, field-rule, and source operations yourself. Through Jentic you install once, import the Liaison API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Liaison API targets travel in the request body and query, not a resource path, so limit the agent to the operations it needs, such as reading form requirements or submitting a form. You choose the operations it may call, so it only does what you allow and nothing more.
Credential isolation
Your Liaison API key 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 'get form field requirements' or 'submit a form', and Jentic returns the matching Liaison operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe
Complementary API for broader integration workflows
Use alongside Liaison API for multi-service workflows
FAQs
Specific to using Liaison API through Jentic.
What authentication does the Liaison API use?
The Liaison API uses an API key passed in the `IQS-API-KEY` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get form field requirements with the Liaison API?
Yes. Use the GET /forms/requirements endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Liaison API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get form field requirements through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get form field requirements'. Jentic returns the matching Liaison API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Liaison API have?
The Liaison API exposes 6 endpoints covering field rules, forms, sources operations.
GET STARTED