Skip to content
Hypamoon

ERP and accounting

Connect Moss to Hypamoon

Yes, with one catch. Moss has an open API that you can use yourself, but it signs in with OAuth only, and that takes more work in a Hypamoon adapter today.

Open

The check

Three questions about the API of Moss, answered from its own docs.

Public API docs
Yes. Read the docs
A key you create yourself
Yes. An admin generates an API key under Settings, Company Settings, API Keys and confirms it in the Moss mobile app. developers.getmoss.com
Versions or a changelog
Yes. Version in the URL path (v1) and a numbered changelog. developers.getmoss.com
How it signs in
Key ID and secret key are exchanged for an OAuth 2.0 client credentials token that lasts one hour, with read or write scope.
Webhooks
Not confirmed.
Hosting
Cloud

Your own spend overview on Moss, built around your suppliers and teams.

  • Card transactions, expenses, suppliers and bank accounts, from the scopes you allow.
  • AI that checks transactions and suggests the right supplier and category, with a person approving.
  • A screen for team leads and a weekly email for finance.

Ask your chat

Answers straight from your Moss data, in Claude or another chat with the full Hypamoon connection.

  • Which card transactions from last week are still missing a receipt?
  • Which suppliers had the biggest spend increase this quarter?

On a schedule

Moss has no webhooks we could confirm, so an agent checks every 15 minutes and decides what happens next.

  1. Every 15 minutes

    New card transactions since the last check.

    AI decides

    AI matches each one to a known supplier and flags amounts that look unusual.

    Then

    Finance gets one email with what needs a look.

A screen for your team or customers

An app on your own address, with sign-in, on top of the same Moss data.

  • For your team

    Team leads see spend per supplier and per month for their own team.

Moss stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in Moss waits for your approval, one call at a time. How adapters work

Good to know

  • Moss signs in with OAuth or signed requests only, with tokens that expire. The Hypamoon vault holds a fixed key today, so an adapter for Moss takes more work: ask your chat to check this first.
  • Only admins can create API keys. Tokens expire after one hour, so the adapter requests a new one when needed.

Try it in your chat

Fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for Moss. API docs: https://developers.getmoss.com/. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 7 November 2026.

Moss is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Moss. Found something that changed? Tell us at support.

More in erp and accounting

All 1094 tools

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect Moss?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot