Can HumDay connect to TCGdex?

Yes. HumDay reads TCGdex's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 33 operations are documented.

Do I need to write code to automate TCGdex?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your TCGdex account.

What can HumDay do in TCGdex?

0 of the 33 documented operations change something in TCGdex, and 33 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my TCGdex account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to TCGdex is held behind that approval.

Automate TCGdex

HumDay reads TCGdex’s own published API description and derives 33 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate TCGdex

What TCGdex is

A Multilanguage Pokémon TCG Database with Cards Pictures and most of the informations contained on the cards. You can find out more about TCGdex at [https://www.tcgdex.net](https://www.tcgdex.net) or on [Discord](https://discord.gg/NehYTAhsZE).

API host: api.tcgdex.net

What HumDay can read from TCGdex

These are the operations a schedule or a trigger can watch.

GETfetch the list of cards/cards
GETFinds Card by Global ID/cards/{cardId}
GETRead hp/hp
GETRead sets/sets
GETRead types/types
GETRead series/series
GETRead stages/stages
GETRead dex ids/dex-ids
GETRead rarities/rarities
GETRead retreats/retreats
GETRead suffixes/suffixes
GETRead variants/variants
GETRead categories/categories
GETRead energy types/energy-types
GETRead illustrators/illustrators
GETRead trainer types/trainer-types
GETRead regulation marks/regulation-marks
GETRead hp/hp/{hp}
GETRead set/sets/{set}
GETRead type/types/{type}
GETRead serie/series/{serie}
GETRead stage/stages/{stage}
GETRead dexId/dex-ids/{dexId}
GETRead rarity/rarities/{rarity}
GETRead suffix/suffixes/{suffix}
GETRead retreat/retreats/{retreat}
GETRead variant/variants/{variant}
GETRead category/categories/{category}
GETRead energy type/energy-types/{energy-type}
GETRead illustrator/illustrators/{illustrator}
GETRead trainer type/trainer-types/{trainer-type}
GETRead regulation mark/regulation-marks/{regulation-mark}
GETRead cardLocalId/sets/{set}/{cardLocalId}

How automating TCGdex works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live TCGdex account.
Grant access, then go live. You approve the specific TCGdex operations it may use — and only those.

Questions about TCGdex automation

Can HumDay connect to TCGdex?: Yes. HumDay reads TCGdex's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 33 operations are documented.
Do I need to write code to automate TCGdex?: No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your TCGdex account.
What can HumDay do in TCGdex?: 0 of the 33 documented operations change something in TCGdex, and 33 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my TCGdex account safe?: Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to TCGdex is held behind that approval.

Where this came from

The operations above are read from a published API description for TCGdex at api.tcgdex.net/v2/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.