canonical: https://jentic.com/apis/propexo.com/propexo

# Propexo Configuration APIs

propexo.com/main version 1.0.0. The API exposes 33 endpoints secured with bearer authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get all data diffs
- Query write job logs
- Create an integration

## Use cases

### Developer Tools Operations

Use the Configuration APIs to perform developer tools operations programmatically. The API provides 33 endpoints covering core functionality including get all data diffs, get log by id, get a link to the job log raw request and response data of a write job..

Example prompt: Call GET `/v1/admin/data-diffs`/ to get all data diffs

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

Example prompt: 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.

Example prompt: Search Jentic for 'get all data diffs', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Admin** — Operations for admin
- **Webhooks** — Operations for webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 56 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 32 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/propexo.com/propexo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Propexo Configuration APIs by hand means setting bearer auth, choosing the production or sandbox host, and reading job logs and data diffs yourself. Through Jentic you install once, import the Configuration APIs from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Propexo puts the job log id in the URL path (`/v1/admin/job-logs/{job_log_id}`/), so a rule can pin your agent to reading a specific job log and its data. You choose the operations it may call, so writes like creating an integration are not included unless you add them.
- **Credential handling:** Your Propexo Configuration APIs token 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.
- **Discovery method:** Agents search Jentic by intent such as 'list data diffs' or 'read a job log', and Jentic returns the matching Propexo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Propexo Configuration API?

Yes. Jentic One runs self-hosted, so you set the rules that decide which Propexo operations and credentials your agent may use. Because Propexo carries the job log id in the URL path (for example GET `/v1/admin/job-logs/{job_log_id}`/), you can pin the agent to reading a specific job log and its raw request and response data. You choose the operations it may call, so a write like POST `/v1/admin/integrations`/ to create an integration is not included unless you add it.