Luminjo API

Name: Luminjo API
Brand: Luminjo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer SupportapiKey26 EndpointsREST

For Agents

Manage Luminjo support tickets end to end — create, list, update, tag, attach files, post canned responses, and organise them into folders.

Install Jentic One Beta

Connect the Luminjo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Luminjo 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# 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 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 Luminjo API.

List, create, retrieve, update, and delete support tickets via /api/ticket and /api/ticket/{id}

Organise tickets into folders with full CRUD on /api/folder

Tag tickets and manage the tag catalogue used for filtering and reporting

GET STARTED

Start building with Luminjo API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Luminjo API for, with concrete tasks.

★ Ingest support tickets from email or chat

Inbound channels such as email forwarders or web chat widgets can post each new conversation into Luminjo as a ticket via POST /api/ticket. The created ticket can be placed in a folder and tagged in the same workflow, so the support team sees a fully classified item rather than a raw email blob. Folders and tags are managed through their own CRUD endpoints, keeping the catalogue consistent.

POST /api/ticket with the customer email body and subject, then PATCH /api/ticket/{id} to apply the billing folder and the 'invoice' tag.

Reply with canned typical responses

Support agents reuse a library of typical responses for common questions (refund process, password reset, shipping status). The Typical Responses endpoints expose the catalogue, and the agent or AI assistant picks the right response and posts it onto the ticket. This keeps tone consistent and shortens handle time for repeated issues.

List typical responses, choose the 'refund process' template, and apply it to ticket 12345.

Reporting and tag-based segmentation

Operations teams report on volume and resolution time by tag and folder. Pulling /api/ticket with filters, joined with the tag and folder catalogues, gives a structured dataset for a BI tool or dashboard — without touching the Luminjo UI or scraping its admin pages.

Pull /api/ticket and group by tag to return a count of tickets per tag for the last 7 days.

Agent-driven Luminjo triage via Jentic

An AI triage agent reads each new ticket, decides on a folder and tag, and replies with a typical response when the question is routine — escalating to a human otherwise. Jentic stores the Luminjo Authorization API key in MAXsystem and exposes the create-ticket, update-ticket, and typical-response operations by intent so the agent can chain them without holding the raw key.

Search Jentic for 'update luminjo ticket', load PATCH /api/ticket/{id}, and execute it to set the folder, tag, and assignee on a freshly created ticket.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for luminjo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/ticket

List all tickets

POST

/api/ticket

Create a new ticket

PATCH

/api/ticket/{id}

Update a ticket

DELETE

/api/ticket/{id}

Delete a ticket

GET

/api/folder

List all folders

GET

/api/tag

List all tags

GET

/api/faq

List FAQs

GET

/api/ticket

List all tickets

POST

/api/ticket

Create a new ticket

PATCH

/api/ticket/{id}

Update a ticket

DELETE

/api/ticket/{id}

Delete a ticket

GET

/api/folder

List all folders

GET

/api/tag

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Luminjo Authorization API key is stored encrypted in the Jentic MAXsystem vault. Jentic attaches it as the Authorization header on every request to the Luminjo workspace, keeping the raw key out of the agent's context.

Intent-based discovery

Agents search by intent such as 'create luminjo ticket' or 'apply tag to ticket', and Jentic returns the matching Luminjo operation with its parameter schema for direct execution.

Time to first call

Direct Luminjo integration: 1-2 days to model the ticket, folder, tag, and typical-response objects and handle attachments. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Luminjo API through Jentic.

Why is there no official OpenAPI spec for Luminjo API?

Luminjo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Luminjo API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Luminjo API use?

The Luminjo API uses an Authorization header carrying an API key. Each request to the Luminjo workspace base URL must include the header. Through Jentic, the key is stored encrypted in MAXsystem and injected per request so it never appears in the agent's prompt or logs.

Can I create and tag a ticket in one workflow?

Yes. POST /api/ticket creates the ticket, then PATCH /api/ticket/{id} updates it with the chosen folder and tags, drawn from the catalogues exposed by /api/folder and /api/tag. Doing both in sequence is the standard pattern for ingesting a fully classified ticket.

What are the rate limits for the Luminjo API?

Specific rate limits are not declared in this spec. Expect per-workspace caps consistent with a help-desk product — design clients to back off on 429 responses and avoid polling /api/ticket more aggressively than once per minute per filter.

How do I send a typical response to a ticket through Jentic?

Search Jentic for 'luminjo typical response', load the matching operation against /api/typical-response or apply the chosen template via PATCH /api/ticket/{id}, and execute it with the ticket ID and response payload. Jentic injects the Authorization API key automatically.

Luminjo API

Connect the Luminjo API to your agent

Capabilities

Start building with Luminjo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs