Add blueprint manufacturing/research to industry endpoints

[Aidansavage]

Feature Request

Route: /latest/industry/manufacture/{type_id}/ standard headers, parameters (including type id obviously), and errors

Auth: None needed

Use Case: This would allow users to reduce dependency on the SDE to collate information about blueprint manufacturing and researching and provide users the ability to build their own data tables. Can be extremely useful for industrial apps as well.

example request url: https://esi.tech.ccp.is/latest/industry/manufacture/12778/ and return body: { "type_id": 12778, "name": "Hail M Blueprint", "manufacture_requirements": [ { "type_id": 11399, "value": 6, }, { "type_id": 16673, "value": 1200, }, { "type_id": 16679, "value": 490, }, { "type_id": 11479, "value": 1, }, ] }

[fuzzysteve]

I'd expand it further, and just serve all the industry data for an item at once.

Like how https://www.fuzzwork.co.uk/blueprint/api/blueprint.php?typeid=11371 returns.

I mean, you could split it up, but that's pretty much everything which is needed for that item.

[jowrjowr]

This would be fantastic to have. Especially for reactions.

[jmsbooth]

Any updates on this/SDE parity conversion?

[kennethjor]

@jmsbooth FWIW I have made a reference data API for a new version of EVE Ref I'm working on. It has a /blueprints endpoint. It's composed of SDE and Hoboleaks data. It might be good enough until it's on the ESI.

For example: https://ref-data.everef.net/blueprints/12778