Propexo Configuration APIs

Name: Configuration APIs
Brand: Configuration APIs
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer33 EndpointsREST

For Agents

Programmatically get all data diffs, get log by id. Covers 33 operations with bearer authentication.

Install Jentic One Beta

Connect the Configuration APIs to your agent

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

Get all data diffs

Query write job logs

Create an integration

Use Cases

GET STARTED

Start building with Configuration APIs

Explore with Jentic

View OpenAPI Document

Automated Admin Management

Automate admin operations by combining multiple Configuration APIs endpoints. Agents can get log by id and then get a link to the job log raw request and response data of a write job. in a single workflow.

Call GET /v1/admin/job-logs/{job_log_id}/ to get log by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Configuration APIs 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 'get all data diffs', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — propexo.

METHOD

PATH

DESCRIPTION

GET

/v1/admin/data-diffs/

Get all data diffs

GET

/v1/admin/job-logs/{job_log_id}/

Get log by ID

GET

/v1/admin/job-logs/{job_log_id}/data

Get a link to the job log raw request and response data of a write job.

GET

/v1/admin/logs/writes/

Query write job logs

GET

/v1/admin/logs/jobs/

Get logs

GET

/v1/admin/logs/jobs/{id}

Get logs by job ID

POST

/v1/admin/integrations/

Create an integration

GET

/v1/admin/integrations/

Get all my integrations

GET

/v1/admin/data-diffs/

Get all data diffs

GET

/v1/admin/job-logs/{job_log_id}/

Get log by ID

GET

/v1/admin/job-logs/{job_log_id}/data

Get a link to the job log raw request and response data of a write job.

GET

/v1/admin/logs/writes/

Query write job logs

GET

/v1/admin/logs/jobs/

Get logs

Why Jentic?

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

Credential isolation

Configuration APIs 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., 'get all data diffs') and Jentic returns the matching Configuration APIs operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Configuration APIs 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 Configuration APIs through Jentic.

What authentication does the Configuration APIs use?

The Configuration APIs 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 get all data diffs with the Configuration APIs?

Yes. Use the GET /v1/admin/data-diffs/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Configuration APIs?

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 all data diffs through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get all data diffs'. Jentic returns the matching Configuration APIs operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Configuration APIs have?

The Configuration APIs exposes 33 endpoints covering admin, webhooks operations.