← Back to Skills Marketplace
mickmicksh

Lap Account And Transaction Api Specification

by mickmicksh · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
363
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install lap-account-and-transaction-api-specification
Description
Account and Transaction API Specification API skill. Use when working with Account and Transaction API Specification for account-access-consents, accounts, b...
README (SKILL.md)

Account and Transaction API Specification

API version: 4.0.0

Auth

OAuth2 | OAuth2

Base URL

/open-banking/v4.0/aisp

Setup

  1. Configure auth: OAuth2 | OAuth2
  2. GET /accounts -- verify access
  3. POST /account-access-consents -- create first account-access-consents

Endpoints

29 endpoints across 12 groups. See references/api-spec.lap for full details.

account-access-consents

Method Path Description
POST /account-access-consents Create Account Access Consents
GET /account-access-consents/{ConsentId} Get Account Access Consents
DELETE /account-access-consents/{ConsentId} Delete Account Access Consents

accounts

Method Path Description
GET /accounts Get Accounts
GET /accounts/{AccountId} Get Accounts
GET /accounts/{AccountId}/balances Get Balances
GET /accounts/{AccountId}/beneficiaries Get Beneficiaries
GET /accounts/{AccountId}/direct-debits Get Direct Debits
GET /accounts/{AccountId}/offers Get Offers
GET /accounts/{AccountId}/parties Get Parties
GET /accounts/{AccountId}/party Get Parties
GET /accounts/{AccountId}/product Get Products
GET /accounts/{AccountId}/scheduled-payments Get Scheduled Payments
GET /accounts/{AccountId}/standing-orders Get Standing Orders
GET /accounts/{AccountId}/statements Get Statements
GET /accounts/{AccountId}/statements/{StatementId} Get Statements
GET /accounts/{AccountId}/statements/{StatementId}/file Get Statements
GET /accounts/{AccountId}/statements/{StatementId}/transactions Get Transactions
GET /accounts/{AccountId}/transactions Get Transactions

balances

Method Path Description
GET /balances Get Balances

beneficiaries

Method Path Description
GET /beneficiaries Get Beneficiaries

direct-debits

Method Path Description
GET /direct-debits Get Direct Debits

offers

Method Path Description
GET /offers Get Offers

party

Method Path Description
GET /party Get Parties

products

Method Path Description
GET /products Get Products

scheduled-payments

Method Path Description
GET /scheduled-payments Get Scheduled Payments

standing-orders

Method Path Description
GET /standing-orders Get Standing Orders

statements

Method Path Description
GET /statements Get Statements

transactions

Method Path Description
GET /transactions Get Transactions

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

  • "Create a account-access-consent?" -> POST /account-access-consents
  • "Get account-access-consent details?" -> GET /account-access-consents/{ConsentId}
  • "Delete a account-access-consent?" -> DELETE /account-access-consents/{ConsentId}
  • "List all accounts?" -> GET /accounts
  • "Get account details?" -> GET /accounts/{AccountId}
  • "List all balances?" -> GET /accounts/{AccountId}/balances
  • "List all beneficiaries?" -> GET /accounts/{AccountId}/beneficiaries
  • "List all direct-debits?" -> GET /accounts/{AccountId}/direct-debits
  • "List all offers?" -> GET /accounts/{AccountId}/offers
  • "List all parties?" -> GET /accounts/{AccountId}/parties
  • "List all party?" -> GET /accounts/{AccountId}/party
  • "List all product?" -> GET /accounts/{AccountId}/product
  • "List all scheduled-payments?" -> GET /accounts/{AccountId}/scheduled-payments
  • "List all standing-orders?" -> GET /accounts/{AccountId}/standing-orders
  • "List all statements?" -> GET /accounts/{AccountId}/statements
  • "Get statement details?" -> GET /accounts/{AccountId}/statements/{StatementId}
  • "List all file?" -> GET /accounts/{AccountId}/statements/{StatementId}/file
  • "List all transactions?" -> GET /accounts/{AccountId}/statements/{StatementId}/transactions
  • "List all transactions?" -> GET /accounts/{AccountId}/transactions
  • "List all balances?" -> GET /balances
  • "List all beneficiaries?" -> GET /beneficiaries
  • "List all direct-debits?" -> GET /direct-debits
  • "List all offers?" -> GET /offers
  • "List all party?" -> GET /party
  • "List all products?" -> GET /products
  • "List all scheduled-payments?" -> GET /scheduled-payments
  • "List all standing-orders?" -> GET /standing-orders
  • "List all statements?" -> GET /statements
  • "List all transactions?" -> GET /transactions
  • "How to authenticate?" -> See Auth section

Response Tips

  • Check response schemas in references/api-spec.lap for field details
  • Create/update endpoints typically return the created/updated object

CLI

# Update this spec to the latest version
npx @lap-platform/lapsh get account-and-transaction-api-specification -o references/api-spec.lap

# Search for related APIs
npx @lap-platform/lapsh search account-and-transaction-api-specification

References

  • Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP

Usage Guidance
This skill is mostly an instruction-only mapping of Account & Transaction endpoints and looks coherent for that purpose, but check two things before installing: (1) clarify what ACCOUNT_AND_TRANSACTION_API_SPECIFICATION_API_KEY is for — is it a Lap/platform API key, a proxy key, or an actual bank/API key? The SKILL.md documents OAuth2 for API calls, yet no OAuth credentials are requested. Do not put broad secrets (like your bank OAuth client secret or unrelated cloud credentials) into that single env var until you confirm its purpose. (2) The CLI examples use npx to fetch @lap-platform/lapsh; running npx will execute code downloaded from npm — verify the package source and your org's policy before running. If you need higher confidence, ask the publisher for a homepage or source repo and documentation explaining the API_KEY vs OAuth2 relationship and inspect references/api-spec.lap before providing credentials.
Capability Analysis
Type: OpenClaw Skill Name: lap-account-and-transaction-api-specification Version: 1.0.1 The skill bundle is a standard API specification for Open Banking (Account and Transaction API). It contains endpoint mappings, authentication requirements, and usage instructions for an AI agent. There is no evidence of malicious code, data exfiltration, or harmful prompt injection; the CLI commands provided in SKILL.md are for maintenance via the legitimate-appearing '@lap-platform/lapsh' tool.
Capability Assessment
Purpose & Capability
The name/description (Account & Transaction API spec, many endpoints) matches the SKILL.md content. The single required env var (ACCOUNT_AND_TRANSACTION_API_SPECIFICATION_API_KEY) is plausibly related to accessing a hosted spec or proxy, but the SKILL.md itself documents OAuth2 as the API auth method — the declared env var and the documented auth approach are not aligned, which could be legitimate (API key for the spec provider vs OAuth2 for the target API) or a configuration mistake.
Instruction Scope
SKILL.md contains endpoint mappings, usage tips, and a short CLI snippet to refresh/search the spec. It does not instruct access to unrelated files, system paths, other credentials, or exfiltrate data. It does reference references/api-spec.lap (a local reference file) which the agent may be expected to read if present.
Install Mechanism
There is no install spec (instruction-only), which is low risk. The SKILL.md suggests using npx @lap-platform/lapsh — that will fetch and run code from npm at runtime if executed by the agent/user. While expected for fetching specs, running npx executes remote package code and is a moderate operational risk to be aware of.
Credentials
Only one env var is required (ACCOUNT_AND_TRANSACTION_API_SPECIFICATION_API_KEY), which is reasonable for an API-spec helper. The inconsistency with the documented OAuth2 auth (no OAuth client id/secret or token env vars declared) is the main proportionality question: it's unclear whether the key is for the spec provider, a proxy, or intended to be an API credential.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always: false, no config paths, no modification of other skills). Autonomous invocation is allowed (default), which is normal; there is no indication the skill forces itself into every agent run.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lap-account-and-transaction-api-specification
  3. After installation, invoke the skill by name or use /lap-account-and-transaction-api-specification
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added a new "CLI" section with LAP commands for updating the spec and searching related APIs. - No other functional or endpoint changes.
v1.0.0
Initial release of the lap-account-and-transaction-api-specification skill. - Provides coverage for 29 endpoints related to accounts, balances, transactions, and consents. - Supports OAuth2 authentication. - Includes detailed endpoint descriptions for account access consents, account details, balances, beneficiaries, direct debits, offers, parties, products, payments, standing orders, statements, and transactions. - Includes guidance for matching user requests to endpoints and tips for using the API. - Requires an API key (ACCOUNT_AND_TRANSACTION_API_SPECIFICATION_API_KEY) for setup.
Metadata
Slug lap-account-and-transaction-api-specification
Version 1.0.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 2
Frequently Asked Questions

What is Lap Account And Transaction Api Specification?

Account and Transaction API Specification API skill. Use when working with Account and Transaction API Specification for account-access-consents, accounts, b... It is an AI Agent Skill for Claude Code / OpenClaw, with 363 downloads so far.

How do I install Lap Account And Transaction Api Specification?

Run "/install lap-account-and-transaction-api-specification" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Lap Account And Transaction Api Specification free?

Yes, Lap Account And Transaction Api Specification is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Lap Account And Transaction Api Specification support?

Lap Account And Transaction Api Specification is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Lap Account And Transaction Api Specification?

It is built and maintained by mickmicksh (@mickmicksh); the current version is v1.0.1.

💬 Comments