How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fave Transactions API

Look up, list, acknowledge and refund transactions.

Fave Transactions API is one of 2 APIs that Fave publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against 2 base URLs: https://omni.myfave.com, https://omni.dino.fave.ninja.

4 operations 3 paths 4 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://omni.myfave.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Fave Transactions API declares 1 security scheme for authenticating requests. An API key is passed in the query as sign (hmacSignature). By default, every request must be authenticated.

  • hmacSignature — HMAC-SHA256 signature computed over the URL-encoded request fields in submission order (excluding sign and countrycode, and excluding outletid on list, id on a…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 4

Look up, list, acknowledge and refund transactions.

GET
/api/fpo/v1/{country_code}/transactions
Retrieve a transaction by reference or receipt ID
getTransaction 6 params → 200401404500
POST
/api/fpo/v1/{country_code}/transactions
Refund a successful payment
refundTransaction 1 param body → 200400401404500
POST
/api/fpo/v1/{country_code}/transactions/{id}
Acknowledge a transaction
acknowledgeTransaction 2 params body → 200401404500
GET
/api/fpo/v1/{country_code}/outlets/{outlet_id}/transactions
List recent transactions for an outlet
listOutletTransactions 7 params → 200401404500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Transaction (39 properties), RefundRequest (5 properties), AcknowledgeRequest (4 properties), Error (2 properties). Each schema is shown below with its type and property counts.

RefundRequest
object
5 properties 4 required
Transaction
object
39 properties
Error
object
2 properties
AcknowledgeRequest
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fave-transactions-api-openapi.yml Raw ↑

Other APIs Fave publishes across the network.

Fave Payments API
Where this information came from

This is an independent, third-party profile of Fave Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.