API Reference

Name: API Reference API
Brand: API Reference
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsWeb AnalyticsapiKey68 EndpointsREST

For Agents

Programmatically create application, list applications. Covers 68 operations with apiKey authentication.

Quickstart

Get started with API Reference in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create application"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with API Reference API.

Create Application

List Applications

Fetch Application

Update Application

Monitor API Reference operational status and events

GET STARTED

Start building with API Reference API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for API Reference, keeping it validated and agent-ready.

Applicant tracking software that’s ready for anything. Get more control with branded careers sites, flexible templates, tailored workflows, beautiful reports, and an easier hiring process—not just for your candidates, but for your own team too. Make better hiring decisions—faster–with Pinpoint. The API exposes 68 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use API Reference API for, with concrete tasks.

★ Analytics Operations

Use the API Reference to perform analytics operations programmatically. The API provides 68 endpoints covering core functionality including create application, list applications, fetch application.

Call POST /api/v1/applications to create application

Automated Custom Fields Management

Automate custom fields operations by combining multiple API Reference endpoints. Agents can list applications and then fetch application in a single workflow.

Call GET /api/v1/applications to list applications, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Reference 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 'create application', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

68 endpoints — applicant tracking software that’s ready for anything.

METHOD

PATH

DESCRIPTION

POST

/api/v1/applications

Create Application

GET

/api/v1/applications

List Applications

GET

/api/v1/applications/{id}

Fetch Application

PUT

/api/v1/applications/{id}

Update Application

POST

/api/v1/comments

Create Comment

GET

/api/v1/comments

List Comments

GET

/api/v1/comments/{id}

Fetch Comment

POST

/api/v1/custom_attributes

Create Custom Attribute

POST

/api/v1/applications

Create Application

GET

/api/v1/applications

List Applications

GET

/api/v1/applications/{id}

Fetch Application

PUT

/api/v1/applications/{id}

Update Application

POST

/api/v1/comments

Create Comment

GET

Why though Jentic?

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

Credential isolation

API Reference apiKey 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., 'create application') and Jentic returns the matching API Reference operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Reference 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

Mixpanel

Alternative analytics API

Choose Mixpanel when you need a different approach to analytics operations

Alternative

Amplitude

Alternative analytics API

Choose Amplitude when you need a different approach to analytics operations

Complementary

Segment

Complementary analytics API

Choose Segment when you need a complementary approach to analytics operations

Complementary

Pendo

Complementary analytics API

Choose Pendo when you need a complementary approach to analytics operations

FAQs

Specific to using API Reference API through Jentic.

What authentication does the API Reference use?

The API Reference uses an API key passed in the `X-API-KEY` 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 create application with the API Reference?

Yes. Use the POST /api/v1/applications endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Reference?

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 create application through Jentic?

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

How many endpoints does the API Reference have?

The API Reference exposes 68 endpoints covering custom fields, departments, divisions operations.