repo_syncs import fails with "unexpected end of JSON input" in v2.55.0

[horstmannmat]

Description I am encountering a regression when running the repo_syncs import command using phrase-cli version 2.55.0. The command fails immediately with a JSON parsing error.

phrase repo_syncs import --account_id $PHRASE_ACCOUNT_ID --id $GITLAB_SYNC_ID
ERROR: unexpected end of JSON input

When downgrading to version 2.54.3, the exact same command works as expected.

phrase repo_syncs import --account_id $PHRASE_ACCOUNT_ID --id $GITLAB_SYNC_ID 
Please consider updating the Phrase Strings CLI client (2.54.3 < 2.55.0)
You can get the latest version from https://phrase.com/cli.
{
 "id": "$GITLAB_SYNC_ID",
 "type": "import",
 "created_at": "2026-01-28T16:10:59Z",
 "status": "running",
 "auto_import": false
}

I verified the API endpoint directly using curl to ensure the API wasn't returning an empty body. The API returns valid JSON, which suggests the issue is isolated to the CLI client's handling of the response in v2.55.0.

When running the API via curl it work as expected

$ curl "https://api.phrase.com/v2/accounts/$PHRASE_ACCOUNT_ID/repo_syncs/$GITLAB_SYNC_ID/import"   -u  $PHRASE_ACCESS_TOKEN: -X POST    -H 'Content-Type: application/json'
{"id":"$GITLAB_SYNC_ID","type":"import","created_at":"2026-01-28T16:35:07Z","status":"running","auto_import":false}%                     

[jablan]

Thanks @horstmannmat for reporting this. Apparently, this crash occurs before the request is sent, as the app now expects a JSON (even an empty one does the trick) for the import call: https://github.com/phrase/strings-openapi/pull/1033/changes#diff-555e35acea3b4b0f3a404ec1e3ee84117a49dc758c1658980e68fbafb7820a93R49

We'll see if we can and should work around this, but you can make the command work by passing -d '{}' for now.

[horstmannmat]

@jablan thank you for the quick response.

I see that in the https://github.com/phrase/strings-openapi/pull/1033/changes#diff-555e35acea3b4b0f3a404ec1e3ee84117a49dc758c1658980e68fbafb7820a93R50 is not required.
when I use curl I can run it without the -d '{}

I wonder if is possible to add this kind of flag in the cli generator.

[jablan]

Yes, we'll look into making it not mandatory in CLI.