Connect Getgo GoToTraining and Mastercard MDES Customer
Describe what you want to happen between Getgo GoToTraining and Mastercard MDES Customer 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.
Getgo GoToTraining
21 documented operations. See all Getgo GoToTraining operations
- POSTCreate Training
/organizers/{organizerKey}/trainings - POSTGet Sessions by Date Range
/reports/organizers/{organizerKey}/sessions - DELETEDelete Training
/organizers/{organizerKey}/trainings/{trainingKey} - PUTUpdate Training Times
/organizers/{organizerKey}/trainings/{trainingKey}/times - PUTUpdate Training Organizers
/organizers/{organizerKey}/trainings/{trainingKey}/organizers - POSTRegister for Training
/organizers/{organizerKey}/trainings/{trainingKey}/registrants
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
How a Getgo GoToTraining and Mastercard MDES Customer 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 Getgo GoToTraining and Mastercard MDES Customer, 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
- Getgo GoToTraining and OData for namespace microsoft.graph11,433 operations
- Mastercard MDES Customer and OData for namespace microsoft.graph11,427 operations
- Cloudflare and Getgo GoToTraining3,143 operations
- Cloudflare and Mastercard MDES Customer3,137 operations
- Getgo GoToTraining and NetBox865 operations
- Mastercard MDES Customer and NetBox859 operations
- Getgo GoToTraining and GitHub832 operations
- GitHub and Mastercard MDES Customer826 operations
- Getgo GoToTraining and Mist789 operations
- Mastercard MDES Customer and Mist783 operations
Questions about connecting Getgo GoToTraining and Mastercard MDES Customer
- Can Getgo GoToTraining connect with Mastercard MDES Customer?
- 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 Getgo GoToTraining to Mastercard MDES Customer?
- 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 Getgo GoToTraining and Mastercard MDES Customer?
- 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 Getgo GoToTraining and Mastercard MDES Customer?
- Getgo GoToTraining publishes 21 documented operations and Mastercard MDES Customer publishes 15. 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 Getgo GoToTraining or Mastercard MDES Customer is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Getgo GoToTraining and Mastercard MDES Customer. Descriptions are each provider’s own words, not ours.