Fave

Fave is a Malaysia- and Singapore-based lifestyle and payments app offering deals, cashback, rewards, eCards, and QR-code payments, operated by Fave Asia Technologies and owned by Pine Labs. For merchants and platforms, Fave exposes the FavePay Omni (FPO) partner API: create single-use QR codes or payment URLs, process customer-presented (merchant-scan) charges, look up, list, and acknowledge transactions, issue full or partial refunds, and receive signed webhook callbacks on every status change. Every request is signed with HMAC-SHA256 using a secret key Fave issues during partner onboarding. FavePay Omni operates across Malaysia (MY), Singapore (SG), and Indonesia (ID).

Fave publishes 2 API contracts indexed on the APIs.io network: Payments API and Transactions API. Tagged areas include Company, Payments, Fintech, QR Payments, and Loyalty.

The Fave catalog on APIs.io includes 2 event-driven AsyncAPI specifications and 1 Spectral governance ruleset.

Fave’s developer surface includes documentation, API reference, support, engineering blog, signup flow, authentication, sandbox, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.1/100 thin ▬ flat Agent 34/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 3 Agent Skills

Company Payments Fintech QR Payments Loyalty Cashback Merchant Services Southeast Asia Webhook

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.1/100 · thin

Contract Quality 4.1 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 4.1 / 15

Operational Transparency 0.8 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 34/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/fave/"><img src="https://apis.io/badge/fave/card.svg" alt="Fave on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 21.9 — up to +19.5 composite points
Access Clarity scores 27.6 — up to +14.5 composite points
Operational Transparency scores 7.9 — up to +12.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/fave/apis.yml: open an issue on github.com/api-evangelist/fave to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Fave Payments API

Create charges via QR code or merchant scan.

Fave Transactions API

Look up, list, acknowledge and refund transactions.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

FavePay Omni (FPO) Payments API

OPEN COLLECTION

FavePay Omni (FPO) Payments Transactions API

OPEN COLLECTION

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Accept a FavePay Omni payment and refund it

Create a QR-code charge, confirm it succeeded via transaction lookup, then issue a full refund. All operationIds are verified against the FavePay Omni OpenAPI.

ARAZZO

Merchant-scan charge and reconcile

Charge a customer via merchant scan, then list the outlet's recent transactions and acknowledge the new one. All operationIds are verified against the FavePay Omni OpenAPI.

ARAZZO

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Accept a FavePay Omni QR payment

AGENT SKILL

Charge via merchant scan

AGENT SKILL

Refund and reconcile transactions

AGENT SKILL

Event Specifications 2

AsyncAPI definitions for this provider's event-driven and streaming APIs.

FavePay Omni Webhooks

Webhook (callback) event surface for FavePay Omni. Fave POSTs the transaction object to the partner's callback_url whenever a transaction changes status. Each payload carries a ...

ASYNCAPI

Fave Favepay Omni Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Fave API Rules

62 rules · 60 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Fave Favepay Omni Overlay

2 actions · update · fave-favepay-omni-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Fave Authentication

apiKey · 1 scheme

SECURITY

Fave Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Fave Agentic Access

6 operations · 4 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 4

Reference material describing how the API behaves

Documentation

APIReference

OpenAPI

AsyncAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

AgenticAccess

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Webhooks

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Arazzo

Arazzo

Scroll for all 8

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: fave
name: Fave
description: 'Fave is a Malaysia- and Singapore-based lifestyle and payments app offering deals, cashback, rewards, eCards,
  and QR-code payments, operated by Fave Asia Technologies and owned by Pine Labs. For merchants and platforms, Fave exposes
  the FavePay Omni (FPO) partner API: create single-use QR codes or payment URLs, process customer-presented (merchant-scan)
  charges, look up, list, and acknowledge transactions, issue full or partial refunds, and receive signed webhook callbacks
  on every status change. Every request is signed with HMAC-SHA256 using a secret key Fave issues during partner onboarding.
  FavePay Omni operates across Malaysia (MY), Singapore (SG), and Indonesia (ID).'
url: https://raw.githubusercontent.com/api-evangelist/fave/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: profiled
x-tier-reason: enriched-api-provider
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://myfave.com/banner.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Payments
- Fintech
- QR Payments
- Loyalty
- Cashback
- Merchant Services
- Southeast Asia
- Webhook
tags_raw:
- Company
- Payments
- Fintech
- QR Payments
- Loyalty
- Cashback
- Merchant Services
- Southeast Asia
- Webhooks
apis:
- aid: fave:fave-payments-api
  name: Fave Payments API
  description: Create charges via QR code or merchant scan.
  humanURL: https://developers.myfave.com/fpo-guide.html
  baseURL: https://omni.myfave.com
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/fave-payments-api-openapi.yml
  - type: Documentation
    url: https://developers.myfave.com/fpo-guide.html
  - type: AsyncAPI
    url: asyncapi/fave-favepay-omni-asyncapi.yml
- aid: fave:fave-transactions-api
  name: Fave Transactions API
  description: Look up, list, acknowledge and refund transactions.
  humanURL: https://developers.myfave.com/fpo-guide.html
  baseURL: https://omni.myfave.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/fave-transactions-api-openapi.yml
  - type: Documentation
    url: https://developers.myfave.com/fpo-guide.html
  - type: AsyncAPI
    url: asyncapi/fave-favepay-omni-asyncapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://myfave.com
- type: DeveloperPortal
  url: https://developers.myfave.com/
- type: Documentation
  url: https://developers.myfave.com/
- type: APIReference
  url: https://developers.myfave.com/fpo-guide.html
- type: Support
  url: https://help.myfave.com/hc/en-us
- type: Blog
  url: https://www.favebiz.com/blog/
- type: SignUp
  url: https://app.favebiz.com/sign-up?ref=favebiz
- type: Login
  url: https://app.favebiz.com/?ref=favebiz
- type: TermsOfService
  url: https://help.myfave.com/hc/en-us/sections/205050988-Terms-of-Use
- type: PrivacyPolicy
  url: https://help.myfave.com/hc/en-us/sections/205051008-Privacy-Policy
- type: Authentication
  url: authentication/fave-authentication.yml
- type: OpenAPI
  url: openapi/_original/fave-favepay-omni-openapi.yml
- type: AsyncAPI
  url: asyncapi/fave-favepay-omni-asyncapi.yml
- type: Webhooks
  url: asyncapi/fave-favepay-omni-webhooks.yml
- type: Conventions
  url: conventions/fave-conventions.yml
- type: ErrorCatalog
  url: errors/fave-problem-types.yml
- type: Lifecycle
  url: lifecycle/fave-lifecycle.yml
- type: Sandbox
  url: sandbox/fave-sandbox.yml
- type: Conformance
  url: conformance/fave-conformance.yml
- type: DataModel
  url: data-model/fave-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/fave-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/fave-favepay-omni-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/fave-llms.txt
- type: Arazzo
  name: Accept a FavePay Omni payment and refund it
  url: arazzo/fave-accept-and-refund.yml
- type: Arazzo
  name: Merchant-scan charge and reconcile
  url: arazzo/fave-scan-and-reconcile.yml
- type: AgenticAccess
  url: agentic-access/fave-agentic-access.yml
- type: DomainSecurity
  url: security/fave-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Fave API — frequently asked questions

Does Fave have an API?

Yes. APIs.io lists 2 APIs from Fave, including Fave Payments API and Fave Transactions API.

Is there an OpenAPI specification for the Fave API?

Yes. APIs.io indexes 2 OpenAPI specifications for Fave, each linked for download from this page.

How do I authenticate with the Fave API?

Fave uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Fave Authentication.

Is the Fave API ready for AI agents?

Fave has a Kin Score of 32.1 out of 100 (thin) and an Agent Readiness score of 33.8 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/fave"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/fave/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/fave/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.