Connect Apigee Marketcheck and Yodlee Core
Describe what you want to happen between Apigee Marketcheck and Yodlee Core 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.
Apigee Marketcheck
71 documented operations. See all Apigee Marketcheck operations
- POSTCompute relative rank for car listings
/search/car/active/rank - POSTCompute relative rank for car listings
/search/car/active/rank/listings - POSTSet client filters
/client/configure/set - GETGets active RV listings for the given search criteria
/search/rv/active - GETGets active car listings for the given search criteria
/search/car/active - GETGets Recent car listings for the given search criteria
/search/car/recents
Yodlee Core
64 documented operations. See all Yodlee Core operations
- DELETEDelete Notification Subscription
/configs/notifications/events/{eventName} - POSTSubscribe For Notification Event
/configs/notifications/events/{eventName} - PUTUpdate Notification Subscription
/configs/notifications/events/{eventName} - PUTUpdate User Details
/user - POSTAdd Manual Account
/accounts - POSTRegister User
/user/register
How a Apigee Marketcheck and Yodlee Core 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 Apigee Marketcheck and Yodlee Core, 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
- Apigee Marketcheck and OData for namespace microsoft.graph11,483 operations
- OData for namespace microsoft.graph and Yodlee Core11,476 operations
- Apigee Marketcheck and Cloudflare3,193 operations
- Cloudflare and Yodlee Core3,186 operations
- Apigee Marketcheck and NetBox915 operations
- NetBox and Yodlee Core908 operations
- Apigee Marketcheck and GitHub882 operations
- GitHub and Yodlee Core875 operations
- Apigee Marketcheck and Mist839 operations
- Mist and Yodlee Core832 operations
Questions about connecting Apigee Marketcheck and Yodlee Core
- Can Apigee Marketcheck connect with Yodlee Core?
- 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 Apigee Marketcheck to Yodlee Core?
- 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 Apigee Marketcheck and Yodlee Core?
- 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 Apigee Marketcheck and Yodlee Core?
- Apigee Marketcheck publishes 71 documented operations and Yodlee Core publishes 64. 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 Apigee Marketcheck or Yodlee Core is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Apigee Marketcheck and Yodlee Core. Descriptions are each provider’s own words, not ours.