canonical: https://jentic.com/apis/swaggerhub.bettrdata/bettrdataio---internal-api-specification

# BettrData.io - Internal API Specification

swaggerhub.bettrdata/bettr-data-io-internal-api-specification version 1.0.0. The API exposes 27 endpoints.

## For AI agents

Programmatically verisons, mapping of client name and id. Covers 27 operations.

## Scope

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

## Capabilities

- Verisons
- Mapping of Client name and ID
- Persist email templates
- Profile a file
- Return id, name, and attributes of all clients

## Use cases

### Developer Tools Operations

Use the BettrData.io - Internal API Specification to perform developer tools operations programmatically. The API provides 27 endpoints covering core functionality including verisons, mapping of client name and id, persist email templates.

Example prompt: Call GET /versions to verisons

### Automated Client Management

Automate client operations by combining multiple BettrData.io - Internal API Specification endpoints. Agents can mapping of client name and id and then persist email templates in a single workflow.

Example prompt: Call GET /ownermap to mapping of client name and id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BettrData.io - Internal API Specification 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 none tokens manually.

Example prompt: Search Jentic for 'verisons', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/versions` | Verisons |
| GET | `/ownermap` | Mapping of Client name and ID |
| POST | `/email/update-templates` | Persist email templates |
| POST | `/file/profile` | Profile a file |
| GET | `/owner` | Return id, name, and attributes of all clients |
| GET | `/{logType}/log/{id}` | returns log |

## Key resources

- **Client** — Operations for client
- **Compile** — Operations for compile
- **Convert** — Operations for convert
- **Count** — Operations for count
- **Datafile** — Operations for datafile

## Why Jentic

- **Setup:** This BettrData.io Internal API is published as a SwaggerHub mock with no authentication, so wiring it by hand still means pointing at the virtual host and coding your own request handling and retries. Through Jentic you install once, import the BettrData.io Internal API from the API Directory, and your agent calls it directly.
- **Permission scoping:** This API puts the log type and log id in the URL path (/{logType}/log/{id}), so a rule can pin your agent to reading one log entry of a given type. You choose the operations it may call, so writes like updating email templates or uploading a profile file are not included unless you add them.
- **Credential handling:** This API declares no authentication, so there is no secret to hand the agent. If you point it at a protected deployment, the credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list versions' or 'read a log entry', and Jentic returns the matching BettrData.io Internal API 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 BettrData.io - Internal API Specification use?

The BettrData.io - Internal API Specification uses no authentication. 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 verisons with the BettrData.io - Internal API Specification?

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

### What are the rate limits for the BettrData.io - Internal API Specification?

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 verisons through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verisons'. Jentic returns the matching BettrData.io - Internal API Specification operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BettrData.io - Internal API Specification have?

The BettrData.io - Internal API Specification exposes 27 endpoints covering client, compile, convert operations.

### Can I limit what my agent is allowed to do with the BettrData.io API?

Yes. Jentic One is self-hosted, so you run it and your own rules decide which BettrData.io operations and credentials the agent may use. Because this API carries the log type and log id in the path (/{logType}/log/{id}), you can pin the agent to reading a single log entry of a given type, and you choose the operations it may call. Write operations such as updating email templates (POST `/email/update-templates`) or uploading a file profile (POST `/file/profile`) stay off limits unless you explicitly add them.