Set embargo date API results in internal server error

[LauraHuisintveld]

What steps does it take to reproduce the issue?
I used this curl command in the command line:
export API_TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
export SERVER_URL=https://test.dataverse.nl
export PERSISTENT_IDENTIFIER=doi:10.80227/test-FI6EIR
export JSON='{"dateAvailable":"2022-10-13", "reason":"Testing", "fileIds":[269054]}'

curl -H "X-Dataverse-key: $API_TOKEN" -H "Content-Type:application/json" "$SERVER_URL/api/datasets/:persistentId/files/actions/:set-embargo?persistentId=$PERSISTENT_IDENTIFIER" -d "$JSON" -v

• What happens?
  I get an internal server error back:

• upload completely sent off: 78 out of 78 bytes
  < HTTP/1.1 500 Internal Server Error
  < Date: Wed, 11 May 2022 14:27:47 GMT

• To whom does it occur (all users, curators, superusers)?
  I used an API-token of a superuser.

Which version of Dataverse are you using?
version 5.10.1 (on our DataverseNL test server.)

[pdurbin]

@LauraHuisintveld sorry for the slow reply! Can you reproduce this on https://demo.dataverse.org ? Thanks!

[qqmyers]

FWIW: This API appears to be working as of #12067 (where I tested). That PR has two changes that may be relevant

• the API calls now explicitly set that the expected Content-Type is application/json,
• errors in date parsing are now caught and send a 400 rather than 500 error response.

Since the date above looks OK (YYYY-MM-DD - I triggered the error using "2026-1-20" ), I'm not sure what might have caused the 500 in this case (possibly fixed by other changes since 5.10.1 ?)

In any case - I'd suggest that #12067 close this and a new issue created if there's still a problem after that PR is merged.