tcn33/up-banking-api-skill

Overview

This skill connects to the Up Banking API to query accounts, transactions, categories, tags, and webhooks. It requires the UP_API_TOKEN environment variable and provides command-style operations to inspect balances, filter transactions, manage tags, and set up webhooks. Use it to build scripts or automation that need reliable access to Up account data.

How this skill works

The skill authenticates using the UP_API_TOKEN and issues REST requests to Up endpoints to list accounts, fetch transactions, and manage metadata like categories and tags. It supports filtering by date range, category, tag, and transaction status and can return raw JSON for downstream processing. Webhook management and basic spending-summary extraction are also supported.

When to use it

• Check current balances or list all Up accounts.
• Search transactions by date range, category, tag, or status.
• Export transactions as JSON for analysis or reporting.
• Categorize transactions or add/remove tags for bookkeeping.
• Create and manage webhooks for real-time transaction notifications.

Best practices

• Set UP_API_TOKEN as an environment variable before running commands.
• Use RFC-3339 timestamps for --since and --until filters to get accurate ranges.
• Run commands with --json and --all when you need full datasets for analysis.
• Paginate large result sets or use --all cautiously to avoid rate limits.
• Verify webhook endpoints with webhook-ping and inspect logs before relying on production webhooks.

Example use cases

• Get a quick snapshot of account balances and recent activity for a finance dashboard.
• Pull all transactions for a month as JSON to aggregate spending by category.
• Tag business-related transactions automatically for expense reporting.
• Re-categorize transactions in bulk after importing statements to align with accounting categories.
• Create a webhook to trigger alerts or workflows when large transactions occur.