Integration
Connect Mapulus to Marketplace Fee Data
When something happens in Mapulus, your agent does the next thing in Marketplace Fee Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mapulus and Marketplace Fee Data to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Mapulus and Marketplace Fee Data
Triggers and actions 2 triggers ยท 7 actions
Trigger
New LocationTriggers when a new location is added in Mapulus.
- New Map
Triggers when a new map is created in Mapulus.
- Create Location
Adds a location pin to a layer on a Mapulus map, from an address or from coordinates.
- Delete Location
Removes a location pin from a Mapulus map.
- Find Location
Returns Mapulus locations, optionally limited to one map or to the location with a given external ID.
- Find Map
Returns the maps in your Mapulus account, so you can pick the one to add locations to.
- Update Location
Updates a location pin in Mapulus. Only the fields you supply are changed.
Action
Get marketplace fees by platformRetrieve the published fee schedule (percentage rates and fixed charges) for one named marketplace or payment processor, e.g. Etsy or Stripe (GET /data/fees/{platform}.json).
- List all marketplace fees
Retrieve the full fee schedule dataset for all 21 supported marketplaces and payment processors in one document (GET /data/fees.json).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.