EVECelery.tasks.ESI.Assets.post_characters_character_id_assets_locations#
A task definition module with associated response models returned by the task.
This module was automatically generated from Jinja templates with the codegen tool included in the root of this repo. You should not directly modify this module but instead modify the template ‘codegen/Templates/ESI_Task.py’.
Module Contents#
Classes#
Get character asset locations |
- class EVECelery.tasks.ESI.Assets.post_characters_character_id_assets_locations.post_characters_character_id_assets_locations#
Bases:
EVECelery.tasks.BaseTasks.TaskESI.TaskESIGet character asset locations
- request_method() str#
Returns the type of request made to ESI
This method will return the request method (get, post, etc.) made to ESI.
- Returns:
Request method passed to requests.request()
- Return type:
str
- route(character_id: int, **kwargs) str#
ESI route with input request parameters
- Parameters:
character_id (int) – An EVE character ID
- Returns:
ESI route with request path parameters if any
- Return type:
str
- cache_ttl_default() int#
TTL for when cache is unspecified.
- Returns:
The number of seconds to cache a response
- Return type:
int
- get_sync(character_id: int, item_ids: list[int], datasource: str = 'tranquility', token: str | None = None, kwargs_apply_async: dict | None = None, kwargs_get: dict | None = None) EVECelery.tasks.ESI.Assets.Models.post_characters_character_id_assets_locations_200.Response200_post_characters_character_id_assets_locations#
Get character asset locations
Return locations for a set of item ids, which you can get from character assets endpoint. Coordinates for items in hangars or stations are set to (0,0,0)
— Alternate route: /dev/characters/{character_id}/assets/locations/
Alternate route: /v2/characters/{character_id}/assets/locations/
NOTE: This function calls the task and blocks until the result is available. This function is a wrapper around Celery’s task.apply_async() and AsyncResult.get() methods. Instead of a dictionary, this function returns a pydantic model to more easily see what returned data responses look like, what is optionally returned, etc.
If you would instead like to return an async result, use Celery’s apply_async() method on this task.
- Parameters:
character_id (int) – An EVE character ID
item_ids (list[int]) – A list of item ids
datasource (str) – The server name you would like data from – [‘tranquility’]
token (str | None) – Access token to use if unable to set a header
kwargs_apply_async (Optional[dict]) –
Dictionary of keyword arguments passed to task.apply_async()
kwargs_get (Optional[dict]) –
Dictionary of keyword arguments passed to AsyncResult.get()
- Returns:
The response from ESI as a pydantic object. The response model will follow the structure of
Response200_post_characters_character_id_assets_locations.- Return type:
- run(character_id: int, item_ids: list[int], datasource: str = 'tranquility', token: str | None = None, **kwargs) dict#
The task body that runs on the EVECelery worker
This is the task body that runs on the EVECelery worker.
IMPORTANT NOTE: You should not directly call this function from your client code as it will run within the context of your client and won’t be sent to the message broker to run on a worker node. To correctly call this task body, see Celery’s documentation on methods for calling tasks.
See also this task’s
get_sync()which is a wrapper function around Celery’s apply_async().get() call.Get character asset locations
Return locations for a set of item ids, which you can get from character assets endpoint. Coordinates for items in hangars or stations are set to (0,0,0)
— Alternate route: /dev/characters/{character_id}/assets/locations/
Alternate route: /v2/characters/{character_id}/assets/locations/
- Parameters:
character_id (int) – An EVE character ID
item_ids (list[int]) – A list of item ids
datasource (str) – The server name you would like data from – [‘tranquility’]
token (str | None) – Access token to use if unable to set a header
- Returns:
The response from ESI as a JSON dictionary. The response dictionary will follow the structure of
Response200_post_characters_character_id_assets_locations.- Return type:
dict