Corporation projects endpoint returning incorrect data

[jasondotsetHacked]

Bug

When requesting my corporation projects, many projects that are completed in-game are returned with state: "Active".

My corporation only has two active projects right now, and I am getting 80+ active projects in the ESI requests.

Request

GET https://esi.evetech.net/corporations/98743678/projects/?state=All&limit=100&after=0
GET https://esi.evetech.net/corporations/98743678/projects/55e64ecd-da3c-48c1-9427-233b63296d92

https://developers.eveonline.com/api-explorer#/operations/GetCorporationsProjectsListing
https://developers.eveonline.com/api-explorer#/operations/GetCorporationsProjectsDetail

Headers sent:

• Authorization: Bearer <redacted>
• Accept: application/json
• X-Compatibility-Date: 2025-12-16
• X-Tenant: tranquility

Response

Status Code

Both resolved 200.

Headers

List endpoint (/corporations/{corporation_id}/projects):

HTTP/1.1 200 OK
date: Wed, 25 Feb 2026 20:39:34 GMT
content-type: application/json
cache-control: private, max-age=0, must-revalidate
etag: W/"e6bba03f6dd5bbf8a96d8baa5e0f1dd74676c5b3a3ba01b7ce4f9a6a98970a66"
last-modified: Wed, 25 Feb 2026 20:39:33 GMT
expires: Wed, 25 Feb 2026 20:39:34 GMT
x-compatibility-date: 2025-08-26
x-esi-cache-status: DYNAMIC
x-ratelimit-group: corp-project
x-ratelimit-limit: 600/15m
x-ratelimit-remaining: 381
x-ratelimit-used: 2

Detail endpoint (/corporations/{corporation_id}/projects/{project_id}):

HTTP/1.1 200 OK
date: Wed, 25 Feb 2026 20:39:34 GMT
content-type: application/json
cache-control: private, max-age=60
etag: W/"10c6fa8aba483ea9f48c6b5157a2b132d7083e106ce34921e2a5e2bae27c2518"
last-modified: Sat, 15 Nov 2025 02:23:35 GMT
expires: Wed, 25 Feb 2026 20:40:34 GMT
x-compatibility-date: 2025-08-26
x-esi-cache-status: DYNAMIC
x-ratelimit-group: corp-project
x-ratelimit-limit: 600/15m
x-ratelimit-remaining: 379
x-ratelimit-used: 2

Body

List response sample (projects returned as Active while complete by progress/reward):

{
  "projects": [
    {
      "id": "55e64ecd-da3c-48c1-9427-233b63296d92",
      "name": "Corp Buyback: Fullerite C84",
      "state": "Active",
      "last_modified": "0001-01-01T00:00:00Z",
      "progress": {
        "current": 6000,
        "desired": 6000
      },
      "reward": {
        "initial": 42084000,
        "remaining": 0
      }
    },
    {
      "id": "a418609d-eba7-42ec-8ed6-220081127ae7",
      "name": "Corp Buyback: Fullerite-C50",
      "state": "Active",
      "last_modified": "0001-01-01T00:00:00Z",
      "progress": {
        "current": 25000,
        "desired": 25000
      },
      "reward": {
        "initial": 103320000,
        "remaining": 0
      }
    }
  ]
}

Detail response for one affected project:

{
  "id": "55e64ecd-da3c-48c1-9427-233b63296d92",
  "name": "Corp Buyback: Fullerite C84",
  "state": "Active",
  "last_modified": "0001-01-01T00:00:00Z",
  "progress": {
    "current": 6000,
    "desired": 6000
  },
  "reward": {
    "initial": 42084000,
    "remaining": 0
  },
  "details": {
    "description": "Deliver Fullerite-C84 Gas to the \"Projects\" Hangar at the Athanor and have ISK deposited automatically into your account.",
    "career": "Industrialist",
    "created": "2025-11-05T16:35:51.296Z"
  },
  "contribution": {
    "reward_per_contribution": 7014
  },
  "creator": {
    "id": 2123835709,
    "name": "Kjalf Frer Ostus"
  },
  "configuration": {
    "deliver_item": {
      "items": [
        {
          "type_id": 30374
        }
      ],
      "office_id": 1051168245291
    }
  }
}

Expected

Projects that are complete in-game should not return state: "Active".
For these examples expected state should be a non-active terminal state (Completed/Closed/Expired as appropriate), and last_modified should not be 0001-01-01T00:00:00Z.

[ccp-pinky]

Tnx for the detailed report, much appreciated!

There are two bugs here:

• last_modified being 0001-01-01. We will fix that later today.
• state of completed projects not updated. We relayed this to our data team to take a look at.

[ccp-pinky]

The data team has fixed the issue; can you check if everything is now how you expect it to be, and close the ticket if it is? (or otherwise comment about what is still wrong, ofc!)