Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Missing support for attachments or metadata

Open
#63 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

The issue names no repository files, tests, or entry points; begin by reviewing the existing invoice API resources and examples, then compare the attachment and metadata capabilities referenced for Fiken and Stripe. The work is complete only when the required invoice attachment or metadata behavior, API surface, and acceptance criteria are defined and implemented.

Written by the indexing model from the issue text.

Description

While APIs like Fiken allow for attachments and Stripe allow for general metadata arrays Trippeltex does not allow for anything like this attached to invoices which makes it a big hassle to work with. Instead of letting your accounting system be a source of truth it will require extra handling of data outside of the system.

Dominant language
No language data
Stars
49
Forks
47
Avg merge
1h 1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Tripletex/tripletex-api2

All issues in Tripletex/tripletex-api2

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.