ESI API returning malformed response

Today, the contracts/public/items/{contractId} API started returning malformed responses. According to ESI, it should return 204 No Content when the contract has been accepted. I’m instead getting HTTP 200 OK responses with an empty response body, which breaks existing applications that expect a JSON response.

This worked as of yesterday. Anyone know if a change was pushed to the API? It would be really interesting if so, since we haven’t seen much development on the API in a while.

I know they fixed a problem were some pages of paged responses was not updated when the cached expired. I don’t think they have changed anything else recently. I think the change was a few days back, though.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.