We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
notes
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.
foo
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!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
But there is no
foo
key in the metadata of the returned response. The docs example says that thefoo
key should be present in the response.When I retrieve the transaction with:
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!
The text was updated successfully, but these errors were encountered: