Tripletex / Tripletex/tripletex-api2

The "changedSince" query parameter does not work

Open
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi, I am currently using the test environment to develop integration with Tripletex and it seems the changedSince field in the query parameters is ignored. Tested so far the endpoints for Customer and Supplier.

Testing with Postman or directly at https://api-test.tripletex.tech/v2-docs/ return all entity records.

GET https://api-test.tripletex.tech/v2/customer?changedSince=2030-09-09T18:00:00Z&fields=changes

Response: 
{
    "fullResultSize": 193,
    "from": 0,
    "count": 193,
    "versionDigest": "'If-None-Match' header not specified",
    "values": [
        {
            "changes": [
                {
                    "employeeId": 11889083,
                    "timestamp": "2025-03-12T15:09:57+01:00",
                    "changeType": "CREATE"
                },
                {
                    "employeeId": 11890724,
                    "timestamp": "2025-04-30T09:35:45+02:00",
                    "changeType": "UPDATE"
                }
            ]
        },
        {
            "changes": [
                {
                    "employeeId": 11889083,
                    "timestamp": "2025-03-12T15:09:57+01:00",
                    "changeType": "CREATE"
                }
            ]
        },
        {
            "changes": [
                {
                    "employeeId": 11889083,
                    "timestamp": "2025-03-12T15:09:57+01:00",
                    "changeType": "CREATE"
                }
            ]
        },
	...
    ]
}

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the GET requests in Postman or the test API documentation for the Customer and Supplier endpoints, using the shown changedSince value and fields=changes. Trace where these endpoints process changedSince, then verify that responses exclude records changed before the supplied timestamp.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.