Annotate transaction not working for custom key
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api, documentation
Research direction
Start with the annotate-transaction section at https://docs.monzo.com/#annotate-transaction and compare its documented response with the PATCH and GET transaction requests shown here. Reproduce the metadata update with a test transaction, then determine whether the API behavior or the documentation conflicts with the example. Done means the expected behavior is explained and the documentation or issue guidance is corrected.
Written by the indexing model from the issue text.
Description
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!
- Dominant language
- SCSS
- Stars
- 116
- Forks
- 51
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from monzo/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Postman Collection Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
area/sessions comp/cron comp/gateway P2 sweeper:risk-message-delivery sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#118863 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·