HumDay

Automate Mastercard Spending Pulse

HumDay reads Mastercard Spending Pulse’s own published API description and derives 4 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 Mastercard Spending Pulse

What Mastercard Spending Pulse is

This API will provide monthly data which includes metrics such as sales volume and growth rate.

API host: api.mastercard.com

What HumDay can read from Mastercard Spending Pulse

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

How automating Mastercard Spending Pulse works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. 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.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Mastercard Spending Pulse account.
  4. Grant access, then go live. You approve the specific Mastercard Spending Pulse operations it may use — and only those.

Automate Mastercard Spending Pulse with these

Questions about Mastercard Spending Pulse automation

Can HumDay connect to Mastercard Spending Pulse?
Yes. HumDay reads Mastercard Spending Pulse's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 4 operations are documented.
Do I need to write code to automate Mastercard Spending Pulse?
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 Mastercard Spending Pulse account.
What can HumDay do in Mastercard Spending Pulse?
0 of the 4 documented operations change something in Mastercard Spending Pulse, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Mastercard Spending Pulse 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 Mastercard Spending Pulse is held behind that approval.

Where this came from

The operations above are read from a published API description for Mastercard Spending Pulse at developer.mastercard.com/devzone/api/portal/swagger/spendingpulse. Descriptions are the provider’s own words, not ours. Last published 2020-08-24.