Does RedSky publish a public API?
No public API documentation exists. RedSky, part of JDM Technology Group, has no developer subdomain, no documentation site with an API section, and no published endpoint reference. Nothing in the public record gives an outside application a documented interface to build against.
Is that the same as saying there is no API at all?
No, and the distinction is worth stating honestly. Suites like RedSky often have internal or implementation-time interfaces used during bespoke projects with the vendor's own services team. What matters commercially is that nothing is published — so no card or expense vendor can promise a supported sync, and any that does is describing a services engagement rather than a product capability. Ask for the documentation; if there is none to point at, price the work as a project.
What does that mean for card and expense automation?
Card transactions reach RedSky the way they reach most construction accounting suites without a public interface: keyed in against jobs and cost codes, or imported as a file in a layout the system accepts. Hand-keying is the default, and it is where the month goes. Statements arrive after the work is done, receipts have to be chased from site teams, and every line needs coding before entry. Until that happens, the cost report on each job is short by exactly the amount the sites spent on cards, which is the figure a commercial manager most wants while the job is still live.
How does Vergo work with RedSky?
Vergo moves the coding to the point of spend. Site staff pick the job and cost code in Vergo when the charge happens and photograph the receipt on site. Approvals run in Vergo, so the site or commercial approver corrects anything miscoded before it moves. Vergo then produces a custom-built CSV export matched to the import format RedSky expects, so the accounts team loads one coded batch instead of rekeying a cycle of card activity from a statement.
Vergo does not claim an API sync with RedSky, because RedSky does not publish one. The file path is the honest path, and with coding, receipts, and approvals already attached, it behaves like automation from the accounts team's side of the desk.
What should you ask RedSky or a vendor?
Ask RedSky directly whether an interface is available to you under your contract and what it costs to have one built — that answer is specific to your implementation and your version. Ask any card vendor claiming a RedSky integration what documentation it builds against, and whether the mechanism works for every customer or only after a bespoke engagement. The distinction decides whether your rollout takes a fortnight or a quarter, and it is better established before signature than after.
Does RedSky have a public API?
No public API documentation, developer portal, or endpoint reference exists for RedSky, so third-party software has nothing documented to build against.
Could an interface exist privately?
Possibly, through bespoke implementation work with the vendor. Nothing is published, so no expense vendor can offer a supported sync as a product capability.
How does Vergo get card transactions into RedSky?
Site staff code charges to jobs and cost codes in Vergo with receipts attached, and Vergo generates a custom CSV export matched to RedSky's import format for the accounts team to load.
Who reviews before it reaches the ledger?
Approvals happen in Vergo before the export is generated, and nothing enters RedSky until the accounts team imports the batch.
