While submitting an issue here I noticed that GitHub is highlighting the contributing guidelines, but that these are for Slate (which looks like the project used to build the docs).

Link: https://github.com/monzo/docs/blob/master/CONTRIBUTING.md

It should probably be mentioned that updating the the notes key in a transaction's metadata applies the value to the transactions top level notes property.

I've signed up for one of your accounts to try this, but it says I'm 70,000 or so behind.
Is there a way to get a test account while I wait please?

Hello,

I'm trying to find the VRP sweeping API docs on docs.monzo.com, and it looks like they have disappeared.

I've checked the history of the master branch of this repo and it doesn't seem like this is intentional, so I wanted to report it in case it wasn't.

Thanks

The usage of the card endpoint appears to be as follows:

List cards
GET /card/list?account_id=$account_id
Gets a list of cards belonging to the given account

Toggle card status
PUT /card/toggle
Arguments: card_id - the ID number of the card to change the status of, status - the new status for the card (INACTIVE or ACTIVE)

I'm guessing there might be a "request replacement card" endpoint as well, but I haven't found it yet...

The documentation for depositing into a pot has request arguments as follows

http --form PUT "https://api.monzo.com/pots/$pot_id/deposit" \ "Authorization: Bearer $access_token" \ "source_account_id=$account_id" \ "amount=$amount" \ "dedupe_id=$dedupe_id"

Making a request with this signature results in the following error;

{"code":"bad_request.missing_param.current_account_id","message":"The field 'current_account_id' is required","retryable":{}}

Replacing source_account_id with current_account_id results in the same error message. Please can the documentation be updated to reflect the correct request arguments

It should be changed to: https://lord.github.io/slate/

Hey there,

I hope that this is a suitable way of getting in contact with the Monzo engineering team - I apologise if not.

The 2023 Google Summer of Code program has recently been announced and is something I am hoping to use as a foot into the world of opensource software once I've finished my degree. When I was thinking about which organisation I'd like to contribute to, Monzo was the first that sprung to mind. I've read a number of Monzo's tech blogs and watched presentations given at the UK Gopher Conference which I've found interesting to see how modern technology solutions are applied in FinTech. Additionally, Monzo is a service I use daily and would love to get the chance to help improve it.

I was therefore wondering if the Monzo team could consider applying to be a mentoring organisation to this program?

I've read the eligibility for mentoring organisations and I believe Monzo meets all of the criteria. Here is timeline of the program: https://developers.google.com/open-source/gsoc/timeline

Many thanks,
Charlie Clarke

It's not documented that merchant can be null. This happens with top-up transactions.

Please can we have the full list of transaction decline reasons? The ones in the docs are incomplete, e.g. I've seen PIN_RETRY_COUNT_EXCEEDED

Hi, was testing the API to try and make an app out of it and hit the rate limit rather soon.

I'm unable to find any information on what are the limits or how long it takes to unblock you, guess that'd be nice to have in the docs 👍

More and more Restful API's are making use of Swagger/OpenAPI for consuming their API Definitions. Is this something in future that you may have planned?

The /accounts API endpoint does not return a current account if it exists for the given user.

I see that the Monzo API allows you to retrieve transaction data; does it allow transactions to be made to other banks? Thanks

I am trying to annotate transactions as documented here: https://docs.monzo.com/#annotate-transaction

Assigning values to the notes key seems to work as expected. However, trying to assign a value to my own custom key does not work.

I send this request

http --form PATCH "https://api.monzo.com/transactions/$transaction_id" \
    "Authorization: Bearer $access_token" \
    "metadata[foo]=bar"

But there is no foo key in the metadata of the returned response. The docs example says that the foo key should be present in the response.

When I retrieve the transaction with:

http "https://api.monzo.com/transactions/$transaction_id" \
    "Authorization: Bearer $access_token" \
    "expand[]==merchant"

I don't see the foo key either. I have tested this with several different transactions.

Could you please explain why this isn't working or where I've gone wrong if I've made a mistake? Thank you!

Is there going to be availability to query current accounts in the near future? If there is a pre-release version of the API I'd love to be able to test it.

Thanks,

Paul

The developer console indicates that applications can specify multiple redirect URLs, which could be particularly useful for developing on localhost and running in production on a public domain.

I have attempted to use URLs in the following formats:

http://localhost:8080/receive, https://prod.foo.com/receive
http://localhost:8080/receive,https://prod.foo.com/receive
http://localhost:8080/receive; https://prod.foo.com/receive
http://localhost:8080/receive;https://prod.foo.com/receive

None of these appear to have worked so far. It would be great to get some documentation on what format these URLs should be in.

Your docs look amazing! I wanted to know if I can use this repo as a template for my own API documentation websites, but unfortunately I didn't find the LICENCE file. Would be awesome if you added the licence.

It would be nice if there was a postman collection someone had somewhere, which could be polished and released to the communityl

I'm not sure whether or not it's possible to verify the source of a webhook event from the POST request. If it's not, there should be a hard-to-guess "password" in the URL you use to register for webhooks, so an application can read it in the POST request.

I have set up a personal project to automatically keep track of Monzo Flex in my finances. I also need to use another card account and would like to automate it too. Unfortunately, not all banks are like Monzo, and this one doesn't provide a nice API. However, it is already integrated with Monzo through Open Finance (I can see my transactions in the Monzo app). Is there any way to get a callback when I make a transaction on this card, similar to how I receive a callback when I make a transaction on my Monzo Flex card?

There's new API endpoint which needs documenting per
https://github.com/monzo/reference-receipts-app/blob/master/main.py#L80-L82
https://github.com/monzo/reference-receipts-app/blob/master/main.py#L122

Related question/request: Do you have any plans on generating this documentation (and potentially SDK for Go and/or other languages) straight from the implementation so it's easier to maintain and always up to date?

What kind of apps can be built on top of Monzo using their API ?

The actual webhook event looks nothing like in the docs and it differs depending on the other party (i.e. webhook for a movement from a pot would be quite different from webhook for a faster payment).

The code below is a cut from a real working app in Rust and as you can see it is very different from one in the docs:

struct Data {
  id: String,
  created: String,
  description: String,
  amount: i64,
  fees: Fees,
  currency: String,
  merchant: ::serde_json::Value,
  notes: String,
  metadata: Metadata,
  labels: ::serde_json::Value,
  account_balance: i64,
  attachments: ::serde_json::Value,
  international: ::serde_json::Value,
  category: String,
  categories: ::serde_json::Value,
  is_load: bool,
  settled: String,
  local_amount: i64,
  local_currency: String,
  updated: String,
  account_id: String,
  user_id: String,
  counterparty: Counterparty,
  scheme: String,
  dedupe_id: String,
  originator: bool,
  include_in_spending: bool,
  can_be_excluded_from_breakdown: bool,
  can_be_made_subscription: bool,
  can_split_the_bill: bool,
  can_add_to_tab: bool,
  amount_is_pending: bool,
}

struct Fees {}

struct Metadata {
  faster_payment: String,
  fps_fpid: String,
  fps_payment_id: String,
  insertion: String,
  notes: String,
  trn: String,
}

struct Counterparty {
  account_number: String,
  name: String,
  sort_code: String,
  user_id: String,
}

API doc should clarify if /transactions always returns a list of transactions sorted in chronological order, or if the order is not guaranteed

As per forum post: https://community.monzo.com/t/monzo-receipt-api-issues/59518

Kieran highlights a documentation issue for the create receipt endpoint.

The interest earned from the Easy Access Savings Pot Cash ISA partnered with OakNorth does not appear in the transactions pulled from https://docs.monzo.com/#list-transactions

Curl is the defacto standard for any automation of any restful api's and it seems counter intuitive to use example systems for the docs that most devs would be used to. I have wrapped a number of REST API's in PowerShell before but have not seen httpie previously

Would be great if your API would support JMESpath querying for transactions.

http://jmespath.org/

As mentioned in the docs, this API is in active development and can change frequently. Coming back to a project for the first time in a few months I found a number of changes in the API that are undocumented, and have found several bugs.

This repository feels like the wrong place to report bugs, so some official documentation on where to report bugs to would be greatly appreciated.

On https://docs.monzo.com/ the "Account Information Services API" section ( https://docs.monzo.com/#account-information-services-api ) lists a number of subsections - each individually linked from the menu. However, since some sections have the same name as the "Monzo Native API" sections (such as "Authentication", "Accounts", "Balances", "Pots", "Direct Debits" etc), the side menu does NOT highlight as you scroll down and if you click on the appropriate item in the side menu, you are taken to the "Monzo Native API" section.

The internal hyperlinks for the Account Information Services API really need to have prefixes appended to them and the relevant "id" fields.

qv: https://community.monzo.com/t/documentation-bug-account-information-services-api-links-incorrect/152141

Looks like the anchor isn't rendered when it's inside the aside element.

This might be just a case of you guys making a change and not updating the documentation. Your /transactions endpoint documentation seems to indicate that each transaction object should contact an account_balance property.

My assumption is that this would be a running total balance, at the point of this transaction. This property doesn't exist in the response though.

Has this been removed and the documentation not updated?

My initial scan of the api docs leads me to think that payment links cannot be created via the api.
Am I correct?

I have deployed an OAuth application that uses https://auth.monzo.com/, but I forgot to add the production redirect URL. This means that login does not work.

When I click the "Submit" button, nothing happens.

Using the web inspector I can see that the button is initiating a web request which is receiving a 400 status code with the payload:

{
    "code": "bad_request.bad_param.redirect_uri",
    "message": "Mismatched redirect_uri"
}

This makes sense given the error I made, but no error message was shown. It would be great to at least have a generic error message, the literal message provided here might be even better (if not understandable by most).