Griffin Transactions API
A transaction represents funds deposited or withdrawn from a bank account. Read more about transactions [in our guides](/docs/guides/transactions).
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/griffin-transactions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
OpenAPI Specification
openapi: 3.2.0
info:
title: Griffin API keys Transactions API
version: '1.0'
description: "## Introduction\n\nThe Griffin API is based on [REST](https://en.wikipedia.org/wiki/Representational_state_transfer).\nIt has resource-oriented URLs, accepts [JSON](https://www.json.org/json-en.html)-encoded request bodies, returns [JSON](https://www.json.org/json-en.html)-encoded responses, and uses standard HTTP response verbs and response codes.\n\nOur API deviates from strict RESTful principles if it makes sense to do so, such as when we enforce tighter access controls around certain operations.\nFor example, when closing a bank account: rather than send a PATCH request to the [bank account](#tag/Bank-accounts) resource to update it's status to `\"closed\"`, we provide a dedicated account closure resource.\n\nAnyone can [create an account](https://app.griffin.com/register) with Griffin and try out our API in [sandbox mode](/docs/guides/sandbox-vs-live-mode).\n\nNew to Griffin? Check out our [getting started guide](/docs/guides/get-started-with-the-api).\n\n## Navigation\n\nOur API is designed to be navigated programmatically. When you request any resource, you will find the URLs for related resources in the response body.\n\nThe API is structured as a tree with your [organization](#tag/Organizations) at the top. Everything that you own will be a sub-resource of your organization.\n\nTo bootstrap the navigation process, request the [index](#tag/Navigation/paths/~1v0~1index/get) endpoint: the response will contain your `organization-url`.\n\nFor a walkthrough, see our [getting started guide](/docs/guides/get-started-with-the-api).\n\n## Pagination\n\nOur list APIs support pagination (e.g. [list bank accounts](#tag/Bank-accounts/paths/~1v0~1organizations~1%7Borganization-id%7D~1bank~1accounts/get) and [list payments](#tag/Payments/paths/~1v0~1bank~1accounts~1%7Bbank-account-id%7D~1payments/get)).\nBy default, a list API returns up to 25 results. If there are more results available, the response payload will include links to the previous/next pages.\n\n### Change page size\n\nYou can request a different number of results (between 1 and 200, inclusive) by using the `page[size]` query parameter:\n\n```\nGET /v0/organizations/:id/bank/accounts?page[size]=100\n```\n\n### Navigating between pages\n\nList responses will include a `links` object with `prev` and `next` attributes, as shown below.\nPerform a GET request to the value of the attribute to fetch the previous/next page of results.\n\n```\n{\n \"accounts\": [\n // ...\n ],\n \"links\": {\n \"prev\": \"/v0/organizations/og.IG9yZ2FuaXphdGlvbi1pZA/bank/accounts?page[before]=djE6WxSPxfYUTnCU9XtWzj9gGA\",\n \"next\": \"/v0/organizations/og.IG9yZ2FuaXphdGlvbi1pZA/bank/accounts?page[after]=djE6aw79PXZySUOL16LD8HRJ3A\"\n }\n}\n\n```\nIf there is no previous or next page available, the value of the attribute will be null.\n\nAny other query parameters included in the initial request will also be included in the response payload's links.\nIf you want to change parameters (see [filtering and sorting](#section/Filtering-and-sorting)), request the first page and follow the links from there.\n\n## Filtering and sorting\n\n### Sort results\n\nBy default, resources will be listed in descending order, usually based on the `created-at` attribute.\nYou can change the sorting behaviour of a list of results by using the `sort` query parameter.\n\nFor example, to list bank accounts in ascending order (oldest first):\n\n```\nGET /v0/organizations/:id/bank/accounts?sort=created-at\n```\n\nTo _explicitly_ sort in descending order (newest first), prefix the sort attribute with `-`:\n\n```\nGET /v0/organizations/:id/bank/accounts?sort=-created-at\n```\n\n### Filter results\n\nSome list APIs allow you to filter the results.\nFilters are expressed as nested data structures encoded into query parameters.\nFor example, you can list bank accounts that are in either the `opening` or `open` state with:\n\n```\nGET /v0/organizations/:id/bank/accounts?filter[account-status][in][]=opening&filter[account-status][in][]=open\n```\n\nSimilarly, you can list legal persons with a specific `application-status`:\n\n```\nGET /v0/organizations/:id/legal-persons?filter[application-status][eq]=accepted\n```\n\n### Include resources\n\nSome list APIs allow you to include associated resources in the response, reducing the number of requests needed to fetch related data.\nFor instance, when listing bank accounts, you can include each bank account's beneficiary legal person by using the `include` query parameter:\n\n```\nGET /v0/organizations/:id/bank/accounts?include=beneficiary\n```\n\nThe response returns the usual list of bank accounts, but it will also have an `included` object with a `legal-persons` attribute:\n\n```\n{\n \"accounts\": [\n // ...\n ],\n \"links\": {\n // ...\n }\n \"included\": {\n \"legal-persons\": [\n // ...\n ]\n }\n}\n```\n\nCheck the documentation for each list API to see all options for sorting and filtering\n\n## Request limits\n\nEach organization is allowed up to 50 concurrent (in-flight) API requests. Exceeding this threshold results in a 429 - Too Many Requests response. Upon receiving a 429 response, you should implement a backoff strategy, pausing to allow your outstanding requests to complete before attempting new requests. To manage your request rate effectively and avoid surpassing this limit, consider using a controlled approach such as a finite pool of threads or workers.\n\n## Versioning\n\nThe Griffin API is versioned via a prefix in the URL.\nThe current version is v0.\nAn example endpoint is: https://api.griffin.com/v0/index.\n\nWe will not break your integration with a particular version for as long as we support that version.\nIf we release a new version, you will have 12 months to upgrade to it."
servers:
- url: https://api.griffin.com/
security:
- api-key-auth: []
tags:
- name: Transactions
description: "A transaction represents funds deposited or withdrawn from a bank account.\n Read more about transactions [in our guides](/docs/guides/transactions)."
paths:
/v0/bank/accounts/{bank-account-id}/transactions:
get:
tags:
- Transactions
description: 'Lists transactions on a bank account. Use an `Accept: application/vnd.griffin+xero-csv` header to receive transactions in a CSV format suitable for importing into [Xero](https://central.xero.com/s/article/Import-a-CSV-bank-statement).'
parameters:
- in: query
name: sort
description: ''
required: false
schema:
type: string
enum:
- -created-at
- processed-at
- -processed-at
- created-at
- x-allOf:
- type: integer
format: int64
- minimum: 1
maximum: 201
name: page[size]
required: false
description: ''
in: query
schema:
type: integer
format: int64
maximum: 200
minimum: 1
- in: query
name: page[before]
description: A base64 encoded opaque string returned in paginated responses.
required: false
schema:
type: string
format: byte
- in: query
name: page[after]
description: A base64 encoded opaque string returned in paginated responses.
required: false
schema:
type: string
format: byte
- in: query
name: include
description: For each transaction returned, include its payment (if one exists) in the response under the `included` attribute.
required: false
schema:
type: string
enum:
- payment
- in: query
name: filter[processed-at][lte]
description: Return only transactions processed at or before the given timestamp.
required: false
schema:
type: string
format: date-time
- in: query
name: filter[processed-at][lt]
description: Return only transactions processed before the given timestamp.
required: false
schema:
type: string
format: date-time
- in: query
name: filter[processed-at][gte]
description: Return only transactions processed at or after the given timestamp.
required: false
schema:
type: string
format: date-time
- in: query
name: filter[processed-at][gt]
description: Return only transactions processed after the given timestamp.
required: false
schema:
type: string
format: date-time
- required: true
name: bank-account-id
in: path
schema:
type: string
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
account-transactions:
type: array
items:
type: object
properties:
account-transaction-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
title: account-transaction-url
description: Link to the transaction resource.
example: /v0/bank/transactions/tr.ICB0cmFuc2FjdGlvbi1pZA
processed-at:
format: date-time
type: string
description: When the transaction was entered into the account ledger.
title: processed-at
post-datetime:
format: date-time
type: string
description: Deprecated. Please use `processed-at` instead.
title: post-datetime
balance-change-direction:
title: balance-change-direction
enum:
- credit
- debit
type: string
description: Specifies the direction of a balance change.
origin-metadata:
type: object
additionalProperties:
type: string
title: origin-metadata
description: Identifiers from the system that originated the hold or transaction. Keys and values are originator-specific.
effective-at:
format: date-time
type: string
description: When the transaction actually takes effect on the account balance.
title: effective-at
transaction-origin-type:
title: transaction-origin-type
enum:
- interest
- deposit
- manual-payment
- card-transaction
- fee
- transfer
- payment
- commission
type: string
description: Indicates the source of the transaction. For a description of each origin type, see our guide to [transactions](/docs/guides/transactions).
payment-url:
type: string
title: payment-url
example: /v0/payments/pm.ICAgICAgcGF5bWVudC1pZA
description: Link to the payment resource.
reference:
type: string
title: reference
description: This field is provided by the person or entity who made the payment.
example: Restaurant Charge - Sushi Palace
account-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
title: account-url
description: Link to the bank account resource.
example: /v0/bank/accounts/ba.IGJhbmstYWNjb3VudC1pZA
balance-change:
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
value:
type: string
title: value
description: The value as a decimal-formatted string
example: '1000.00'
type: object
additionalProperties: false
title: balance-change
description: Shows the account [balance change](/docs/terms/balance-change).
account-balance:
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
value:
type: string
title: value
description: The value as a decimal-formatted string
example: '1000.00'
type: object
additionalProperties: false
title: account-balance
description: Shows the [account balance](/docs/terms/account-balance).
description:
type: string
title: description
description: "This field is provided by the bank to help customers understand the\n nature of the transaction."
example: Interest earned in April from Alexa account.
required:
- account-url
- account-transaction-url
- account-balance
- balance-change
- balance-change-direction
- transaction-origin-type
- processed-at
- effective-at
title: account-transaction
links:
type: object
properties:
prev:
type:
- string
- 'null'
next:
type:
- string
- 'null'
required:
- prev
- next
title: links
included:
title: ''
description: Present only when the request uses the `include` parameter.
required:
- account-transactions
- links
title: ''
'400':
description: ''
'401':
description: Requires an API key to continue
headers:
www-authenticate:
description: Returns `GriffinSession` if no valid authentication is found.
schema:
type: string
'404':
description: ''
summary: List transactions
/v0/bank/transactions/{transaction-id}:
get:
tags:
- Transactions
description: Yields a bank account transaction
parameters:
- required: true
name: transaction-id
in: path
schema:
type: string
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
account-transaction-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-transaction-id:
type: string
format: ''
title: transaction-id
required: true
name: transaction-id
required:
- bank-account-transaction-id
title: account-transaction-url
description: Link to the transaction resource.
example: /v0/bank/transactions/tr.ICB0cmFuc2FjdGlvbi1pZA
processed-at:
format: date-time
type: string
description: When the transaction was entered into the account ledger.
title: processed-at
post-datetime:
format: date-time
type: string
description: Deprecated. Please use `processed-at` instead.
title: post-datetime
balance-change-direction:
title: balance-change-direction
enum:
- credit
- debit
type: string
description: Specifies the direction of a balance change.
origin-metadata:
type: object
additionalProperties:
type: string
title: origin-metadata
description: Identifiers from the system that originated the hold or transaction. Keys and values are originator-specific.
effective-at:
format: date-time
type: string
description: When the transaction actually takes effect on the account balance.
title: effective-at
transaction-origin-type:
title: transaction-origin-type
enum:
- interest
- deposit
- manual-payment
- card-transaction
- fee
- transfer
- payment
- commission
type: string
description: Indicates the source of the transaction. For a description of each origin type, see our guide to [transactions](/docs/guides/transactions).
payment-url:
type: string
title: payment-url
example: /v0/payments/pm.ICAgICAgcGF5bWVudC1pZA
description: Link to the payment resource.
reference:
type: string
title: reference
description: This field is provided by the person or entity who made the payment.
example: Restaurant Charge - Sushi Palace
account-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
bank-account-id:
type: string
format: ''
title: bank-account-id
required: true
name: bank-account-id
required:
- bank-account-id
title: account-url
description: Link to the bank account resource.
example: /v0/bank/accounts/ba.IGJhbmstYWNjb3VudC1pZA
balance-change:
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
value:
type: string
title: value
description: The value as a decimal-formatted string
example: '1000.00'
type: object
additionalProperties: false
title: balance-change
description: Shows the account [balance change](/docs/terms/balance-change).
account-balance:
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
value:
type: string
title: value
description: The value as a decimal-formatted string
example: '1000.00'
type: object
additionalProperties: false
title: account-balance
description: Shows the [account balance](/docs/terms/account-balance).
description:
type: string
title: description
description: "This field is provided by the bank to help customers understand the\n nature of the transaction."
example: Interest earned in April from Alexa account.
required:
- account-url
- account-transaction-url
- account-balance
- balance-change
- balance-change-direction
- transaction-origin-type
- processed-at
- effective-at
title: account-transaction
'400':
description: ''
'401':
description: Requires an API key to continue
headers:
www-authenticate:
description: Returns `GriffinSession` if no valid authentication is found.
schema:
type: string
'404':
description: ''
summary: Get transaction
components:
securitySchemes:
api-key-auth:
type: apiKey
in: header
name: Authorization
description: 'API token authentication.
It should follow the format: `GriffinAPIKey g-test-MyKey-XXXXXXX`'
x-tagGroups:
- name: Getting started
tags:
- API keys
- Connectivity
- Navigation
- Events
- Webhooks
- Message Signatures
- name: Customer verifications
tags:
- Legal persons
- Legal person history
- Claims
- Workflows
- Verifications
- Decisions
- Companies House
- Reliance onboarding
- name: Banking
tags:
- Bank accounts
- Bank account events
- Bank account restrictions
- Bank account holds
- Pooled account membership
- Payments
- Transactions
- Payees
- Confirmation of payee
- Open banking
- name: Team management
tags:
- Organizations
- Users
- Roles
- Memberships
- Invitations
x-id:
- default