Transformers.cards card data is stored in an Airtable database, which can be queried using a built-in API. The API closely follows REST semantics, uses JSON to encode objects, and relies on standard HTTP codes to report operation outcomes. Using this API, you can integrate Transformers.cards data with any external system or application.
TDC is maintained by hobbyists who have no idea what they’re doing (and certainly don’t have approval from the relevant copyright holders.) Things will probably break without warning. Sorry.
There are a number of Airtable API clients (none of which are developed by me) available that may help you integrate the API more easily with your existing codebase:
- Ruby: airtable or airrecord
- Python: airtable.py
- .NET: airtable.net
The primary API endpoint URL is: https://api.airtable.com/v0/appVjmNG3AukyOaQn/
The API has three supported card types, which each have their own endpoint suffix.
Combiner Forms: https://api.airtable.com/v0/appVjmNG3AukyOaQn/Combiner%20Forms/
Each card record has a unique identifier. To lookup a card, you add its unique identifier to the relevant endpoint.
For example, Acid Storm’s unique identifier is: recSO4B0zpZIaJ737
Therefore, querying the https://api.airtable.com/v0/appVjmNG3AukyOaQn/Bot%20Cards/recSO4B0zpZIaJ737 endpoint will return a JSON object with Acid Storm’s attributes.
Further reference documents can be found in the sidebar on the left.
I’m not currently equipped to guarantee or offer full-time support for this, but if you run into an issue, jump into the Transformers.cards Discord server and I or another dev can probably help you out.
Below is a sandbox widget that you can use to inspect the structure of returned JSON objects and experiment with test queries. These return results from the live database; you will need a real API Key for this to work!