Does TRAMPS publish an API?
No. Trace Solutions — the independent, employee-owned UK firm behind the TRAMPS property management accounting system — does not publish API documentation or developer specifications. Web services exist within the product, but they are delivered as bespoke per-client integrations: Trace builds them for a specific customer engagement, and there is no public spec another platform can develop against.
The distinction matters. "Web services exist" and "there is an API you can connect to" are different claims, and only the first is true of TRAMPS today.
What does that mean for expense automation?
No expense platform can offer an off-the-shelf live sync with TRAMPS. A managing agent or property company that wants card transactions flowing into TRAMPS programmatically would need to commission bespoke integration work from Trace — a project, with a project's cost and timeline — or use the system's import routines.
The import route is the practical one, and the question becomes how the import file gets built: by hand from card statements, or automatically from spend that is already coded.
How does Vergo connect to TRAMPS?
Vergo integrates by producing structured CSV exports custom-built to match the import format TRAMPS expects. Card transactions are captured in Vergo as they happen, coded by the cardholder with the receipt attached, and exported as a file shaped for the system's import. Property teams get spend into TRAMPS without re-keying and without commissioning bespoke development.
Could a bespoke web-services integration be worth it?
For some clients, perhaps — that is between you and Trace. But it is a commissioned project, not a connector you switch on. The matched CSV export works from day one, and nothing about it precludes deeper integration later.
What should a property team ask any expense vendor about TRAMPS?
First: are they claiming a live connection? If so, ask to see the published TRAMPS API documentation it relies on — there is none, so the claim rests on either bespoke commissioned work or wishful marketing. Second: does their export match the import format TRAMPS expects, or is it a generic file your accounts team must still rework? Third: where do receipts live once the import runs? Vergo's answers are straightforward — no API claim, a custom-built matched export, and receipts stored permanently against each transaction.
Does Trace Solutions TRAMPS have a public API?
No. Web services exist in TRAMPS, but only as bespoke per-client integrations built by Trace Solutions. No public API specifications are published.
Can Vergo sync live with TRAMPS?
No platform can, off the shelf — there is no published API to connect to. Vergo provides custom-built CSV exports matched to the import format TRAMPS expects.
What is the difference between TRAMPS web services and an API?
TRAMPS web services are commissioned per client with no public spec. A public API is documented and open for any platform to build against. TRAMPS offers the former, not the latter.
How does card spend get into TRAMPS with Vergo?
Cardholders code transactions and attach receipts in Vergo as they spend; Vergo exports a CSV shaped for TRAMPS's import, which your accounts team loads as a routine step.
