Up API

Name: Up API
Brand: Up API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer20 EndpointsREST

For Agents

Programmatically list accounts, retrieve account. Covers 20 operations with bearer authentication.

Use for: I need to accounts, I want to account, Search for attachments, Find all attachment

Install Jentic One Beta

Connect the Up API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Up API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fup.com.au%2Fup-com-au" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fup.com.au%2Fup-com-au" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Up API.

List accounts

Retrieve account

Categorize transaction

Query and filter Up API records by parameters

GET STARTED

Start building with Up API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Up API for, with concrete tasks.

★ Payments Operations

Use the Up API to perform payments operations programmatically. The API provides 20 endpoints covering core functionality including list accounts, retrieve account, list attachments.

Call GET /accounts to list accounts

Automated Accounts Management

Automate accounts operations by combining multiple Up API endpoints. Agents can retrieve account and then list attachments in a single workflow.

Call GET /accounts/{id} to retrieve account, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Up 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 bearer tokens manually.

Search Jentic for 'list accounts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — the up api gives you programmatic access to your balances and transaction data.

METHOD

PATH

DESCRIPTION

GET

/accounts

List accounts

GET

/accounts/{id}

Retrieve account

GET

/attachments

List attachments

GET

/attachments/{id}

Retrieve attachment

GET

/categories

List categories

GET

/categories/{id}

Retrieve category

PATCH

/transactions/{transactionId}/relationships/category

Categorize transaction

GET

/util/ping

Ping

GET

/accounts

List accounts

GET

/accounts/{id}

Retrieve account

GET

/attachments

List attachments

GET

/attachments/{id}

Retrieve attachment

GET

/categories

List categories

GET

/categories/{id}

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Up API by hand means attaching a bearer token on every call, matching each account, transaction, and category operation to its request shape, and handling pagination yourself. Through Jentic you install once, import the Up API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Up puts the account and transaction ids in the URL path (/accounts/{id} and /transactions/{transactionId}/...), so a rule can pin your agent to one account: it can read that account and nothing else. You choose the operations it may call, so a write like changing a transaction's category is not included unless you add it.

Credential isolation

Your Up 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.

Intent-based discovery

Agents search Jentic by intent such as 'list accounts' or 'read a transaction', and Jentic returns the matching Up operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Up API through Jentic.

What authentication does the Up API use?

The Up API 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 list accounts with the Up API?

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

What are the rate limits for the Up 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 list accounts through Jentic?

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

How many endpoints does the Up API have?

The Up API exposes 20 endpoints covering accounts, categories, tags operations.

Up API

Connect the Up API to your agent

Capabilities

Start building with Up API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs