The Pemo API lets you connect Pemo to other systems and pull data out of Pemo automatically. It is mainly used for integrations with custom ERP solutions, automating your month-end close, and exporting transaction data into accounting tools.
Pemo provides secure REST APIs. Your ERP, accounting system or internal platform pulls the data it needs from Pemo; Pemo does not push data into your systems. Pemo and your systems stay fully independent, with no shared databases and no direct system access.
Before you start
You must be on the Enterprise plan to create and use API keys. On Starter or Premium, select Request API access in the dashboard to open a conversation with the Pemo team about upgrading.
Add your payment account, import your vendors, and import your chart of accounts. See How to import a Chart of Accounts to Pemo and Add a vendor.
What you can pull from the API
The API is read-only and cursor-paginated, with five endpoints: transactions, reimbursements, cards, users and organizations. Each endpoint needs its own scope: transactions:read, reimbursements:read, cards:read, users:read and organizations:read.
Transactions and reimbursements apply no status or approval filter by default: every transaction and reimbursement record in the organization is returned, sorted by creation date with the newest first. Filtering is opt-in, so you pass status, approval status, type, card, date and search filters yourself. Results are always limited to what the calling token's own user role is allowed to see.
Available data includes card transactions and expenses, merchant names, transaction references, cardholder names and emails, transaction amounts and currencies, and each record's export status. The cards endpoint also returns spending limits, the amount spent this period and the remaining amount. Receipt documents come through secure, time-limited download URLs. Live balances are not available through the API.
Because receipt URLs expire, download the receipt files, store them in your own storage environment, and reference them internally as needed.
Security
All API communication is encrypted. Authentication uses scoped API keys, which may be rotated.
Supported systems
Any system that can consume RESTful APIs can integrate with Pemo, including but not limited to:
Microsoft Dynamics (Business Central, Finance & Operations)
Oracle NetSuite
SAP
Sage
Custom or in-house ERPs
Native integrations may also be available for selected platforms.
How to create an API key
Select Developers at the bottom of the sidebar.
Select Create API key or Request API key.
Add a name for the key, such as "Pemo Key".
Copy the API key shown on screen.
Important: You will only see the key once, and it can only be generated one time. Copy it and store it somewhere safe. The key stays listed under Developers, but you cannot view its value again.
Marking data as exported
After you pull transactions using the API, your system can send an acknowledgement back to Pemo. Once acknowledged, those transactions are marked as Exported inside Pemo. What a connected accounting system stores or shows is decided in that system.
How to delete an API key
Select Developers at the bottom of the sidebar.
Find the key, then open Actions.
Select Delete.
Confirm the deletion.
Note: Once deleted, the key stops working immediately.