Get corporation wallet journal
Retrieve the given corporation's wallet journal for the given division going 30 days back
Path parameters
The ID of the corporation
Wallet key of the division to fetch journals from
Query parameters
Which page of results to return.
Headers
The language to use for the response.
The ETag of the previous request. A 304 will be returned if this matches the current ETag.
The compatibility date for the request.
The tenant ID for the request.
The date the resource was last modified. A 304 will be returned if the resource has not been modified since this date.
Response
OK
The amount of ISK given or taken from the wallet as a result of the given transaction. Positive when ISK is deposited into the wallet and negative when ISK is withdrawn
Wallet balance after transaction occurred
An ID that gives extra context to the particular transaction. Because of legacy reasons the context is completely different per ref_type and means different things. It is also possible to not have a context_id
The type of the given context_id if present
Date and time of transaction
The reason for the transaction, mirrors what is seen in the client
The id of the first party involved in the transaction. This attribute has no consistency and is different or non existant for particular ref_types. The description attribute will help make sense of what this attribute means. For more info about the given ID it can be dropped into the /universe/names/ ESI route to determine its type and name
Unique journal reference ID
The user stated reason for the transaction. Only applies to some ref_types
"The transaction type for the given. transaction. Different transaction types will populate different attributes. Note: If you have an existing XML API application that is using ref_types, you will need to know which string ESI ref_type maps to which integer. You can look at the following file to see string->int mappings: https://github.com/ccpgames/eve-glue/blob/master/eve_glue/wallet_journal_ref.py"
The id of the second party involved in the transaction. This attribute has no consistency and is different or non existant for particular ref_types. The description attribute will help make sense of what this attribute means. For more info about the given ID it can be dropped into the /universe/names/ ESI route to determine its type and name
Tax amount received. Only applies to tax related transactions
The corporation ID receiving any tax paid. Only applies to tax related transactions