Your data, your API

Read your own MoreBack data from a spreadsheet, a script or a chatbot with a personal key. Keys are read-only, only see your own account, only read what you tick, and you can revoke them any time.

Make a key

  1. Sign in to MoreBack and open Profile, then Browser extension & shortcuts, then API and chatbots.
  2. Name the key and tick what it can read: wallet (cards you hold, which card to use), baskets (spending and money back), offers, bills, points.
  3. Copy the key. It starts mbk_ and is shown once; we keep only a scrambled copy. You can have up to 5.

Send it as a header on every request: Authorization: Bearer mbk_…. Keys never work in a web address, and a signed-in browser can't use these endpoints, so a page you visit can't read them.

JSON endpoints

All are GET on https://moreback.co.uk and return JSON with the date the figures are for.

curl -H "Authorization: Bearer mbk_…" \
  "https://moreback.co.uk/api/v1/baskets?period=last_month"

Chatbots (MCP)

MoreBack is a remote MCP server over Streamable HTTP at https://moreback.co.uk/api/mcp. Add it as a custom connector in a chatbot that supports remote MCP servers, with your key as the Bearer token. It answers with JSON (no event stream).

Tools (each needs the matching tick on the key): get_spending (baskets), get_bills (bills), get_points (points), get_saved_offers (offers), which_card and list_cards (wallet). They return the same figures Ask Mags uses in the app. Every tool is read-only.

curl -X POST https://moreback.co.uk/api/mcp \
  -H "Authorization: Bearer mbk_…" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_bills","arguments":{"within_days":30}}}'

Limits and errors

What it is, and is not

The API reads the cards you already hold and what you've typed into MoreBack. It never returns card numbers, your email or anyone else's data, and it can't change anything. MoreBack is an information tool, not a lender or broker: nothing here is advice to apply for a card. See Privacy and terms.

Back to the homepage