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

# BettrData.io - Public API Specification

swaggerhub.bettrdata/bettr-data-io-api-specification version 1.0. The API exposes 33 endpoints secured with basic authentication.

## For AI agents

Programmatically create a client, get clients. Covers 33 operations with basic authentication.

## Scope

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

## Capabilities

- Create a client
- Get clients
- Update one client by id
- Delete one client by id
- Monitor BettrData.io - Public API Specification operational status and events

## Use cases

### Developer Tools Operations

Use the BettrData.io - Public API Specification to perform developer tools operations programmatically. The API provides 33 endpoints covering core functionality including create a client, get clients, get one client by id.

Example prompt: Call POST /client to create a client

### Automated Client Management

Automate client operations by combining multiple BettrData.io - Public API Specification endpoints. Agents can get clients and then get one client by id in a single workflow.

Example prompt: Call GET /client to get clients, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BettrData.io - Public 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/client` | Create a client |
| GET | `/client` | Get clients |
| GET | `/client/{id}` | Get one client by id |
| PUT | `/client/{id}` | Update one client by id |
| DELETE | `/client/{id}` | Delete one client by id |
| GET | `/client/getOneBy` | Get a single client using query |
| POST | `/profile` | Create a Profile |
| GET | `/profile` | List All Profiles |

## Key resources

- **Client** — Operations for client
- **Converttype** — Operations for converttype
- **Datafile** — Operations for datafile
- **Encrypt** — Operations for encrypt
- **Health** — Operations for health

## Why Jentic

- **Setup:** This BettrData.io Public API uses HTTP basic authentication against a host that embeds your instance domain on port 1338, so hand-wiring it means encoding the basic credentials, filling in your instance host, and handling retries yourself. Through Jentic you install once, import the BettrData.io Public API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** This API puts the client id in the URL path (`/client/{id}`), so a rule can pin your agent to one client. You choose the operations it may call, so destructive ones like deleting or updating a client are not included unless you add them.
- **Credential handling:** Your BettrData.io Public API basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a client' or 'look up a client by field', and Jentic returns the matching BettrData.io Public 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 - Public API Specification use?

The BettrData.io - Public API Specification uses HTTP Basic authentication with username and password. 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 create a client with the BettrData.io - Public API Specification?

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

### What are the rate limits for the BettrData.io - Public 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 create a client through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a client'. Jentic returns the matching BettrData.io - Public 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 - Public API Specification have?

The BettrData.io - Public API Specification exposes 33 endpoints covering client, converttype, datafile operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which BettrData.io operations and credentials the agent may use, and you can leave destructive calls like DELETE `/client/{id}` or PUT `/client/{id}` out of that set so the agent only reads or creates. Since the client id sits in the URL path at `/client/{id}`, a rule can pin the agent to a single client rather than every client on your account. The agent can call only the operations you have granted, and its stored credentials are injected at execution time without entering the agent context.