Atrium Sports API SDK
Python module to make use of the Atrium Sports Datacore API
Datacore REST API
from atriumsports import AtriumSports
atrium = AtriumSports(
{
"sport": "basketball",
"credential_id": "XXXXX",
"credential_secret": "YYYY",
"organizations": ["b1a23"],
}
)
datacore = atrium.client("datacore")
response = datacore.get("/o/b1a23/competitions", limit=500)
for data in response.data():
print(data)
or using openapi client
GET endpoints
from pprint import pprint
from atriumsports import AtriumSports
from atriumsports.datacore.openapi import CompetitionsApi
atrium = AtriumSports(
{
"sport": "basketball",
"credential_id": "XXXXX",
"credential_secret": "YYYY",
"organizations": ["b1a23"],
}
)
datacore = atrium.client("datacore")
# prepare api client with access token and connection pool
with datacore as api_client:
# create api instance object for handling input and output of chosen endpoint
api_instance = CompetitionsApi(api_client)
response = api_instance.competition_list(sport="basketball", organization_id="b1a23")
pprint(response)
POST and PUT endpoints
from atriumsports import AtriumSports
from atriumsports.datacore.openapi import EntitiesApi
from atriumsports.datacore.openapi import EntityPostBody
from atriumsports.datacore.openapi import EntityPutBody
atrium = AtriumSports(
{
"sport": "basketball",
"credential_id": "XXXXX",
"credential_secret": "YYYY",
"organizations": ["b1a23"],
}
)
datacore = atrium.client("datacore")
with datacore as api_client:
api_instance = EntitiesApi(api_client)
response = api_instance.entity_insert(
sport="basketball",
organization_id="b1a23",
entity_post_body=EntityPostBody(
name_full_local="Test",
status="INACTIVE",
),
)
entity_id = response.data[0].entity_id
response = api_instance.entity_update(
sport="basketball",
organization_id="b1a23",
entity_id=entity_id,
entity_put_body=EntityPutBody(
status="ACTIVE",
),
)
assert response.data[0].status == "ACTIVE"
Response body
Response body is a pydantic object containing deserialized response data.
Example:
from atriumsports import AtriumSports
from atriumsports.datacore.openapi import LeaguesApi
atrium = AtriumSports(
{
"sport": "basketball",
"credential_id": "XXXXX",
"credential_secret": "YYYY",
"organizations": ["b1a23"],
}
)
datacore = atrium.client("datacore")
with datacore as api_client:
api_instance = LeaguesApi(api_client)
# throws error if response body doesn't pass validation
response = api_instance.league_list("b1a23", "basketball")
print(response.data)
print(response.data[0].region_type)
Datacore Streaming API
import time
from atriumsports import AtriumSports
atrium = AtriumSports(
{
"sport": "basketball",
"credential_id": "XXXXX",
"credential_secret": "YYYY",
"environment": "dev",
}
)
stream_api = atrium.client("datacore-stream")
def on_connect_callback_function(client):
"""example callback when connected"""
print("connected")
def on_read_callback_function(client, topic, message):
"""example callback when message read"""
print("{}: {}".format(topic, message))
connected = stream_api.connect(
{
"fixture_id": "f71dfdd6-51f1-11ea-8889-22953e2ee7e2", # fixture_id
"scopes": ["write:stream_events", "read:stream_events"], # Scopes
"on_read": on_read_callback_function,
"on_connect": on_connect_callback_function,
}
)
if not connected:
print(stream_api.error())
else:
stream_api.publish(
"write:stream_events",
{
"type": "event",
"data": {
"eventClass": "sport",
"eventId": "c2404cc0-9f75-11e8-98d0-529269fb1459",
"entityId": "c24048a6-9f75-11e8-98d0-529269fb1459",
"personId": "c2405b2a-9f75-11e8-98d0-529269fb1459",
"eventType": "2pt",
"subType": "jumpshot",
"clock": "PT08:23",
"shotClock": "PT12.3",
"periodId": 2,
"success": True,
"timestamp": "2018-08-14T16:45:34.34",
"clientId": "c2408302-9f75-11e8-98d0-529269fb1459",
"clientType": "TestApi:1.1.2",
},
},
qos=1, # QoS level 0=at most once, 1=at least once, 2=exactly once
)
time.sleep(40)
stream_api.disconnect()
For the available apis and models please check modules under atriumsports.datacore.openapi.
Using your IDE, navigate to this module to see all details of the generated API classes.
1 maintainer
Metadata
1 maintainer
Release files for atriumsports_sdk 2.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| atriumsports_sdk-2.4.2.tar.gz | 593.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atriumsports_sdk-2.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / atriumsports_sdk-2.4.2.tar.gz
| Download URL | atriumsports_sdk-2.4.2.tar.gz |
|---|---|
| Size | 593.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6e3bd09261ceaeaea2e38f77c25141a8cc478710e7b233791278cdab87abf1d
|
|
BLAKE2b-256 checksum How to use checksums |
5f42c14f849b7539e4a5c35c9b5d1e62bde75f49c9c56c87387d350c7904b2fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.6 {"installer":{"name":"uv","version":"0.11.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / atriumsports_sdk-2.4.2-py3-none-any.whl
| Download URL | atriumsports_sdk-2.4.2-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41228fe0c8cc8f4cec02f1af5a3f8b2d72617ee4e73b47fd49df2e6508290b7c
|
|
BLAKE2b-256 checksum How to use checksums |
2664645ab876b97bda908760976b2f06b4d6f17fb1e90c31b2760f0e584c8b18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.6 {"installer":{"name":"uv","version":"0.11.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for atriumsports_sdk 2.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
