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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
PayFast

PayFast Transaction History API

Query merchant transaction history with date range and aggregations

Documentation Provider Profile APIs.io OpenAPI GitHub

PayFast Transaction History API is one of 13 APIs that PayFast publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://api.payfast.co.za/v1, https://sandbox.payfast.co.za/v1.

4 operations 4 paths 3 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://api.payfast.co.za
Authentication
API Key
Contact
PayFast Developer Support
License
Proprietary
Resource Areas
1

Authentication & Security 1

PayFast Transaction History API declares 1 security scheme for authenticating requests. An API key is passed in the header as merchant-id (merchantAuth). By default, every request must be authenticated.

  • merchantAuth — PayFast API authentication uses an MD5 signature derived from the merchant ID, passphrase, timestamp, and request data. Required headers include merchant-id, v…

Paths & Operations 4

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

Transaction History 4

Query merchant transaction history with date range and aggregations

GET
/transactions/history
Get transaction history for a date range
getTransactionHistoryRange 4 params → 200400401
GET
/transactions/history/daily
Get daily transaction summary
getDailyTransactionHistory 3 params → 200400401
GET
/transactions/history/weekly
Get weekly transaction summary
getWeeklyTransactionHistory 3 params → 200400401
GET
/transactions/history/monthly
Get monthly transaction summary
getMonthlyTransactionHistory 3 params → 200400401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Transaction (14 properties), TransactionHistoryResponse (3 properties), ErrorResponse (3 properties). Each schema is shown below with its type and property counts.

Transaction
object
A single merchant transaction record
14 properties
ErrorResponse
object
3 properties
TransactionHistoryResponse
object
Merchant transaction history results
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payfast-transaction-history-api-openapi.yml Raw ↑

Other APIs PayFast publishes across the network.

PayFast Subscriptions API
AE Profile APIs.io
PayFast Tokenization API
AE Profile APIs.io
PayFast Credit Card Transactions API
AE Profile APIs.io
PayFast Refunds API
AE Profile APIs.io
PayFast Credit Card Transactions API
AE Profile APIs.io
PayFast Notifications API
AE Profile APIs.io
PayFast Onsite Checkout API
AE Profile APIs.io
PayFast Payment Form API
AE Profile APIs.io
PayFast Refunds API
AE Profile APIs.io
PayFast Subscriptions API
AE Profile APIs.io
PayFast Tokenization API
AE Profile APIs.io
#Transaction History
← Back to P APIs
API Details
ID
payfast:payfast-transaction-history-api
Base URL
https://api.payfast.co.za
Docs
https://developers.payfast.co.za/documentation
Provider
PayFast
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=payfast-transaction-history-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/payfast-transaction-history-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of PayFast Transaction History 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.