Get Vendors
GET/v1/sandbox/:sandbox_id/vendor
Get Vendors by filters. All filters must be true for a Vendor to be returned. Requires any of permissions: sandbox:config:view, sandbox:config:edit
Request
Path Parameters
Sandbox ID
Query Parameters
Vendor IDs to filter by
Legacy Vendor IDs to filter by
Possible values: [recipe, randomly_sampled]
Vendor types to filter by
Possible values: non-empty and <= 128 characters
Filter by case insensitive name
Possible values: non-empty and <= 128 characters
Filter by case insensitive name
Filter by last modified account ID
Sort results by
Sort order
Possible values: non-empty and <= 128 characters
Default value: 0
Cursor to designate where you are in iterating through values. Start with '0', and pass this on subsequent calls to continue iteration
Possible values: >= 1 and <= 10000
Default value: 50
The maximum number of elements to be returned per call
Responses
- 200
- 422
Successful Response
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
- check_greater_then_or_equal/check_less_than
- check_greater_than_or_equal_and_subtract/subtract
- add/set
]
]
data
object[]
The Vendors.
custom_data
object
Custom data associated with the resource
Possible values: non-empty and <= 125 characters
Name of the resource
Possible values: <= 250 characters
Description of the resource
Account ID of the user who last modified the resource
Timestamp of when the resource was last modified
Timestamp of when the resource was created
ID of the Sandbox
The ID of the Vendor.
Default value: 0
The legacy ID of the Vendor.
Possible values: [recipe, randomly_sampled]
Determine how the Vendor fulfills the Loot.
loot
object[]
The Loot the Vendor will fulfill.
custom_data
object
Custom data associated with the resource
Possible values: non-empty and <= 125 characters
Name of the resource
Possible values: <= 250 characters
Description of the resource
The Item ID. Optional Item that will be granted to the player if Sub Vendor ID is not specified.
The Sub Vendor ID. Optional Vendor ID that will be used to fulfill the Loot instead of granting the Item.
Default value: 1
The quantity of the Item or Sub Vendor to fulfill. This will be multiplied by the quantity of fulfilled Loot and the parent Loot if quantity_type is relative.
Possible values: [own, rent, rent_timeframe_locked, own_transient, inherit_entitlement_inventory]
Determines way Inventory is selected and how it is to be modified.
Possible values: [add, subtract, set, check_greater_than_or_equal, check_less_than, check_greater_than_or_equal_and_subtract]
Determines how the Inventory Quantity will be acted upon and the sort order of Loot in a Vendor if the Loot has the same sort order.
Sort Order:
Determines if the Loot is active. Inactive Loot will not be fulfilled.
Default value: 0
The sort order of the Loot. Lower sort order will be fulfilled first. Inventory Operation is used as a tie breaker when sort_order is the same.
Default value: 0
The drop weight of the Loot. Higher drop weight will be more likely to be fulfilled.
When dropped in a randomly sampled vendor, will this create a new order or fill inline?. The primary use case for this is when you want the same loot to be dropped multiple times in a randomly sampled vendor.
Default value: true
When dropped in a randomly sampled vendor, will the sub vendor allow dropping part of the the bundle? False means it will only drop if the entire sub vendor can be given to the player
Item required to be owned/rented to drop this Loot in a randomly sampled vendor
Default value: 0
Amount of the required_item_id to be owned/rented to drop this Loot in a randomly sampled vendor
Default value: 0
Amount of owned/rented of this Loot's item that will prevent this Loot from dropping in a randomly sampled vendor
Possible values: [relative, absolute]
Determines how the quantity is to be modified.
Relative looks at the context in which is fulfilled; e.g. If Loot A has a quantity of 2 and 5 is being fulfill, the resulting quantity modification will be 10.
Absolute ignores the context in which it is fulfilled; e.g. If Loot B has a quantity of 3 and 5 is being fulfill 5, the resulting quantity modification will be 3.
When fulfilling Loot if this is set the quantity will be multiplied by the quantity of this Item in the Player's Inventory.
Determines if the Loot can be claimed by the client. This is dangerous without the correct loot confiuration as a client could claim Loot multiple times.
The Time Frame ID. Optional Time Frame ID that will be used for the expiration of inventory records when Loot when it is fulfilled.
The Time Frame ID. Optional Time Frame ID that will be used for the expiration of inventory records when Loot when it is fulfilled.
Possible values: [free, sweat, none, anon, amazon, steam, psn, xbox_live, google, twitch, nintendo_switch, apple, nintendo, epic, google_play, nintendo_ppid]
Grouping of Inventory Items. Inventory items are grouped into different buckets as each Platform that is supported has different requirements on how Inventory can be used on their Platform and other Platforms.
Possible values: [none, from_current_xp_to_target_additional_level_min_xp, from_current_level_min_xp_to_target_additional_level_min_xp, from_zero_to_target_exact_level_min_xp]
Allows granting xp levels as Loot. If the player is already max level, the Loot will not be fulfilled. Requires the Item assigned to the Loot to have an XP Table ID.
The following examples assume the player is level 3 with 150 total xp. The quantity configured on the Loot being fulfilled is 1. The XP Table is configured like so: 1: 20 2: 50 3: 100 4: 200 5: 400
from_current_xp_to_target_additional_level_min_xp - The Loot will grant the player enough xp to reach min xp of the next level. Example 1: fulfill quantity 1 Player will be level 4 with 200 total xp. Example 2: fulfill quantity 2 Player will be level 5 with 400 total xp. Example 3: fulfill quantity 3 Player will be level 5 with 400 total xp.
from_current_level_min_xp_to_target_additional_level_min_xp - The Loot will grant the player the amount of xp required to reach the min xp of the next level from the min xp of the current level. Example 1: fulfill quantity 1 Player will be level 4 with 250 total xp. Example 2: fulfill quantity 2 Player will be level 5 with 450 total xp. Example 3: fulfill quantity 3 Player will be level 5 with 450 total xp.
from_zero_to_target_exact_level_min_xp - The Loot will grant the player the amount of xp required to reach the min xp of the target level from zero xp. Example 1: fulfill quantity 1 Player will be level 3 with 170 total xp. Example 2: fulfill quantity 2 Player will be level 4 with 200 total xp. Example 3: fulfill quantity 3 Player will be level 4 with 250 total xp.
The current price point id. Optional Price Point ID that will be used to determine the price of the Loot when it is fulfilled.
The pre sale price point id. Optional Price Point ID that will be used to show the previous price of the Loot.
Default value: 0
Hard cap on quantity of an item this Loot can give. Disabled with 0
Default value: 0
The legacy ID of the Loot.
ID of the Sandbox
Account ID of the user who last modified the resource
Timestamp of when the resource was last modified
Timestamp of when the resource was created
The Loot ID
The Vendor ID
Name corresponding Vendor ID
Name corresponding Sub-Vendor ID
Name corresponding Item ID
Name corresponding Required Item ID
Name corresponding Quantity Multi Inventory Item ID
Name corresponding Current Price Point ID
Name corresponding Pre-sale Price Point ID
page_meta
object
required
Possible values: non-empty and <= 128 characters
Cursor to designate where you are in iterating through values. Start with '0', and pass this on subsequent calls to continue iteration
Possible values: >= 1 and <= 10000
Default value: 50
The maximum number of elements to be returned per call
Default value: 0
The total number of entities.
{
"data": [
{
"custom_data": {},
"name": "string",
"description": "string",
"last_modified_account_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"last_modified_timestamp": "2024-07-29T15:51:28.071Z",
"created_timestamp": "2024-07-29T15:51:28.071Z",
"sandbox_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"vendor_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"legacy_vendor_id": 0,
"vendor_type": "recipe",
"loot": [
{
"custom_data": {},
"name": "string",
"description": "string",
"item_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"sub_vendor_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"quantity": 1,
"inventory_selector_type": "own",
"inventory_operation": "add",
"active": false,
"sort_order": 0,
"drop_weight": 0,
"fill_in_new_order": false,
"allow_partial_bundles": true,
"required_item_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"required_item_count": 0,
"stack_limit": 0,
"quantity_type": "relative",
"quantity_multi_inventory_item_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"is_claimable_by_client": false,
"legacy_time_frame_id": 0,
"time_frame_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"use_inventory_bucket": "free",
"xp_quantity_transform_type": "none",
"current_price_point_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"pre_sale_price_point_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"hard_quantity_maximum": 0,
"legacy_loot_id": 0,
"sandbox_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"last_modified_account_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"last_modified_timestamp": "2024-07-29T15:51:28.071Z",
"created_timestamp": "2024-07-29T15:51:28.071Z",
"loot_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"vendor_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"vendor_name": "string",
"sub_vendor_name": "string",
"item_name": "string",
"required_item_name": "string",
"quantity_multi_inventory_item_name": "string",
"current_price_point_name": "string",
"pre_sale_price_point_name": "string"
}
]
}
],
"page_meta": {
"cursor": "string",
"page_size": 50,
"total": 0
}
}
Validation Error
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
- MOD1
- MOD2
]
]
detail
object[]
loc
object[]
required
anyOf
string
integer
{
"detail": [
{
"loc": [
"string",
0
],
"msg": "string",
"type": "string"
}
]
}