canonical: https://jentic.com/apis/swaggerhub.test4364/apioauth

# Test4364 APIOAuth

Introduction What does your API do? Overview Things that the developers should know about Authentication What is the preferred way of using the API? Error Codes What errors and status codes can a user expect? Rate limit Is there a limit to the number of requests an user can send?. The API exposes 5 endpoints.

## For AI agents

Programmatically get account activities, get account balances. Covers 5 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Get Account Activities
- Create New Account
- Update Account Address
- Query and filter APIOAuth records by parameters
- Monitor APIOAuth operational status and events

## Use cases

### Identity and Authentication Operations

Use the APIOAuth to perform identity auth operations programmatically. The API provides 5 endpoints covering core functionality including get account activities, get account balances, get authorization token.

Example prompt: Call GET /PAPortOdata529/odata/v1.2/RecentActivity to get account activities

### Automated Misc Management

Automate misc operations by combining multiple APIOAuth endpoints. Agents can get account balances and then get authorization token in a single workflow.

Example prompt: Call GET /PAPortOdata529/odata/v1.2/balances(AccountNumber='MTAwMTA=',ValuationDate='9-03-2019',IRRCalculationMethod=1,ShareAdjIRRReturnNull=0,DisplayActsWithNoSubaccounts=0,ReturnAllLinkedAccounts=0,AccountOwnerAndBeneficiaryCombination=1,AccessLinkedAccounts=2,CalculateIRRatAccount=1) to get account balances, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call APIOAuth 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 'get account activities', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /PAPortOdata529/odata/v1.2/RecentActivity | Get Account Activities |
| GET | /PAPortOdata529/odata/v1.2/balances(AccountNumber='MTAwMTA=',ValuationDate='9-03-2019',IRRCalculationMethod=1,ShareAdjIRRReturnNull=0,DisplayActsWithNoSubaccounts=0,ReturnAllLinkedAccounts=0,AccountOwnerAndBeneficiaryCombination=1,AccessLinkedAccounts=2,CalculateIRRatAccount=1) | Get Account Balances |
| POST | /paportoauth529/odata2/token | Get Authorization Token |
| POST | /paportodata529/odata/v1.2/Accounts | Create New Account |
| PUT | /paportodata529/odata/v1.2/Accounts('10010')/Addresses | Update Account Address |

## Key resources

- **Misc** — Operations related to Misc

## Why Jentic

- **Setup:** Wiring the APIOAuth service by hand means targeting the PAPort host, working through its OData token and account endpoints, and handling calls and retries yourself. Through Jentic you install once, import APIOAuth from the API Directory, and your agent calls it.
- **Permission scoping:** APIOAuth takes its targets through OData query and body parameters rather than a resource id in the path, so scope the agent to the operations it needs, such as reading recent activity or fetching balances. You choose which operations it may call, so writes like creating accounts or updating addresses are not included unless you add them.
- **Credential handling:** This API is configured without a credential, so there is no secret for the agent to expose; if a credential is added later it 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 'get account activities' or 'fetch account balances', and Jentic returns the matching APIOAuth operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the APIOAuth use?

The APIOAuth 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 get account activities with the APIOAuth?

Yes. Use the GET /PAPortOdata529/odata/v1.2/RecentActivity endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the APIOAuth?

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 account activities through Jentic?

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

### How many endpoints does the APIOAuth have?

The APIOAuth exposes 5 endpoints covering misc operations.

### Can I limit what my agent is allowed to do with the APIOAuth?

Yes. Because you self-host Jentic One, your own rules decide which APIOAuth operations the agent may call and which credentials it may use. APIOAuth takes its targets through OData query and body parameters rather than a resource id in the path, so you can scope the agent to read-only operations such as getting recent activity or fetching account balances. Write operations like creating a new account or updating an account address stay off limits unless you explicitly allow them.