Connect Mastercard MDES Customer and RAWG Video Games Database
Describe what you want to happen between Mastercard MDES Customer and RAWG Video Games Database in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Mastercard MDES Customer
15 documented operations. See all Mastercard MDES Customer operations
- POSTProvides the ability to search for tokens based on Account PAN
/search - POSTAllows issuers to display customized messages per token within the
/accountholdermessaging - POSTUsed to delete a token so
/token/delete - POSTUsed to suspend an active token so
/token/suspend - POSTUsed to retrieve all comments associated with a token
/token/comments - POSTUsed to unsuspend or resume a suspended token and return it
/token/unsuspend
RAWG Video Games Database
30 documented operations. See all RAWG Video Games Database operations
- GETGet a list of tags
/tags - GETGet a list of games
/games - GETGet a list of video game genres
/genres - GETGet a list of video game storefronts
/stores - GETGet a list of game creators
/creators - GETGet a list of video game platforms
/platforms
How a Mastercard MDES Customer and RAWG Video Games Database automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Mastercard MDES Customer and RAWG Video Games Database, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Mastercard MDES Customer and OData for namespace microsoft.graph11,427 operations
- OData for namespace microsoft.graph and RAWG Video Games Database11,442 operations
- Cloudflare and Mastercard MDES Customer3,137 operations
- Cloudflare and RAWG Video Games Database3,152 operations
- Mastercard MDES Customer and NetBox859 operations
- NetBox and RAWG Video Games Database874 operations
- GitHub and Mastercard MDES Customer826 operations
- GitHub and RAWG Video Games Database841 operations
- Mastercard MDES Customer and Mist783 operations
- Mist and RAWG Video Games Database798 operations
Questions about connecting Mastercard MDES Customer and RAWG Video Games Database
- Can Mastercard MDES Customer connect with RAWG Video Games Database?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Mastercard MDES Customer to RAWG Video Games Database?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Mastercard MDES Customer and RAWG Video Games Database?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Mastercard MDES Customer and RAWG Video Games Database?
- Mastercard MDES Customer publishes 15 documented operations and RAWG Video Games Database publishes 30. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Mastercard MDES Customer or RAWG Video Games Database is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Mastercard MDES Customer and RAWG Video Games Database. Descriptions are each provider’s own words, not ours.