canonical: https://jentic.com/apis/testfire.net/testfire

# Testfire AltoroJ REST API

testfire.net/altoroj version 1.0.2. The API exposes 12 endpoints.

## For AI agents

Programmatically getaccount, getaccountbalance. Covers 12 operations.

## Scope

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

## Capabilities

- getAccount
- getTransactions
- showLastTenTransactions
- addUser
- changePassword
- sendFeedback

## Use cases

### Developer Tools Operations

Use the AltoroJ REST API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including getaccount, getaccountbalance, gettransactions.

Example prompt: Call GET /account to getaccount

### Automated 1. Login Management

Automate 1. login operations by combining multiple AltoroJ REST API endpoints. Agents can getaccountbalance and then gettransactions in a single workflow.

Example prompt: Call GET `/account/{accountNo}` to getaccountbalance, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account` | getAccount |
| GET | `/account/{accountNo}` | getAccountBalance |
| POST | `/account/{accountNo}/transactions` | getTransactions |
| GET | `/account/{accountNo}/transactions` | showLastTenTransactions |
| POST | `/admin/addUser` | addUser |
| POST | `/admin/changePassword` | changePassword |
| POST | `/feedback/submit` | sendFeedback |
| GET | `/feedback/{feedbackId}` | getFeedback |

## Key resources

- **1. Login** — Login mechanism
- **2. Account** — View account information
- **3. Transfer** — Transfer funds between accounts
- **4. Feedback** — Submit and review feedback
- **5. Admin** — Add and change user details

## Why Jentic

- **Setup:** Wiring the AltoroJ REST API by hand means resolving its /api base against your own deployment host and coding each account, transaction, and admin call yourself. Through Jentic you install once, import the AltoroJ REST API from the API Directory, store any required credential once, and your agent calls it.
- **Permission scoping:** AltoroJ puts the account number in the URL path (`/account/{accountNo}/transactions`), so a rule can pin your agent to one account: it can read that account and its transactions and nothing else. You choose the operations it may call, so admin operations like adding a user or changing a password are not included unless you add them.
- **Credential handling:** Any credential for the AltoroJ REST API 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 'read an account balance' or 'list account transactions', and Jentic returns the matching AltoroJ REST 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 AltoroJ REST API use?

The AltoroJ REST API 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 getaccount with the AltoroJ REST API?

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

### What are the rate limits for the AltoroJ REST API?

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

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

### How many endpoints does the AltoroJ REST API have?

The AltoroJ REST API exposes 12 endpoints covering 1. login, 2. account, 3. transfer operations.

### Can I limit what my agent is allowed to do with the AltoroJ REST API?

Yes. Jentic One is self-hosted, so your own rules decide which AltoroJ operations and credentials the agent may use. Because the account number sits in the URL path, such as `/account/{accountNo}/transactions`, you can pin the agent to a single account so it only reads that account and its transactions. You also choose the exact operations it may call, so admin actions like POST `/admin/addUser` or POST `/admin/changePassword` stay off limits unless you explicitly grant them.