Manage file attachments and folders across Rentman projects, tasks, and purchase orders
domain: api.rentman.net · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Rentman API token.
List files attached to a resource with the resource-scoped endpoint, e.g. GET /tasks/{id}/files or GET /purchaseorders/{id}/files.
List the folder structure a resource uses with the matching file_folders endpoint, e.g. GET /tasks/{id}/file_folders or GET /contacts/{id}/file_folders.
Create or rename a folder with POST /folders or PUT /folders/{id} (added in API 1.12.0).
Use the generated parent_api_path field on /files and /file_folders responses to walk back up to the parent record without a second lookup.
Known gotchas
Folder creation/update (POST and PUT /folders) and File Folder read endpoints were added in different API versions (1.7.0 for folder read, 1.12.0 for folder write) — confirm your account is on a recent enough API version.
The item field on /files and /file_folders was changed from a string to an integer ID, and itemtype from an integer to a string enum, in API 1.12.0 — older integration code that parsed these as the old types will break.
Files/folders are exposed per parent resource (tasks, purchase orders, contacts, contact persons, etc.) rather than through one global search-all-files endpoint for every resource type.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?