List available kits
curl --request GET \
--url https://rts-builder.slayers.tech/api/v1/external/kits \
--header 'X-API-Key: <api-key>'import requests
url = "https://rts-builder.slayers.tech/api/v1/external/kits"
headers = {"X-API-Key": "<api-key>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {'X-API-Key': '<api-key>'}};
fetch('https://rts-builder.slayers.tech/api/v1/external/kits', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"kits": [],
"total": 0
}API Reference
List available kits
Return the externally accessible kits for the calling API key.
GET
/
api
/
v1
/
external
/
kits
List available kits
curl --request GET \
--url https://rts-builder.slayers.tech/api/v1/external/kits \
--header 'X-API-Key: <api-key>'import requests
url = "https://rts-builder.slayers.tech/api/v1/external/kits"
headers = {"X-API-Key": "<api-key>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {'X-API-Key': '<api-key>'}};
fetch('https://rts-builder.slayers.tech/api/v1/external/kits', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"kits": [],
"total": 0
}List available kits
Notes
- The response always includes
kitsandtotal. - A
200with an emptykitsarray means the key authenticated successfully but has no externally visible kits. - In live testing, this also occurred for a newly created team API key after a kit had been marked
exposed, which suggests an additional access grant or backend entitlement step beyond simply toggling exposure.
Method behavior
Observed method handling:GET /api/v1/external/kitsreturns200HEAD /api/v1/external/kitsreturns404OPTIONS /api/v1/external/kitsreturns404
