Application user API

Name: Application user API API
Brand: Application user API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer62 EndpointsREST

For Agents

Programmatically application information, authenticate via v1 client token. Covers 62 operations with bearer authentication.

Connect the Application user API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Application user 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.

Install Jentic One Beta (Self-Hosted)

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

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 Application user API API.

Application Information

Authenticate via V1 Client Token

Upload Lab Report

List Lab Reports

Process Lab Report

GET STARTED

Start building with Application user API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Application user API API for, with concrete tasks.

★ Developer Tools Operations

Use the Application user API to perform developer tools operations programmatically. The API provides 62 endpoints covering core functionality including application information, authenticate via v1 client token, authenticate via hmac.

Call GET /applicationinfo to application information

Automated Applicationinfo Management

Automate applicationinfo operations by combining multiple Application user API endpoints. Agents can authenticate via v1 client token and then authenticate via hmac in a single workflow.

Call POST /auth/client_token to authenticate via v1 client token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Application user 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 bearer tokens manually.

Search Jentic for 'application information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

62 endpoints — spikeapi.

METHOD

PATH

DESCRIPTION

GET

/applicationinfo

Application Information

POST

/auth/client_token

Authenticate via V1 Client Token

POST

/auth/hmac

Authenticate via HMAC

POST

/auth/pkcs1

Authenticate via PKCS1

POST

/lab_reports

Upload Lab Report

GET

/lab_reports

List Lab Reports

POST

/lab_reports/process

Process Lab Report

GET

/lab_reports/{lab_report_id}

Get Lab Report

GET

/applicationinfo

Application Information

POST

/auth/client_token

Authenticate via V1 Client Token

POST

/auth/hmac

Authenticate via HMAC

POST

/auth/pkcs1

Authenticate via PKCS1

POST

/lab_reports

Upload Lab Report

GET

Why though Jentic?

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

Credential isolation

Application user API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'application information') and Jentic returns the matching Application user API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Application user API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Application user API API through Jentic.

What authentication does the Application user API use?

The Application user API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I application information with the Application user API?

Yes. Use the GET /applicationinfo endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Application user 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 application information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'application information'. Jentic returns the matching Application user API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Application user API have?

The Application user API exposes 62 endpoints covering applicationinfo, auth, lab_reports operations.