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

SumUp Receipts API

The Receipts model obtains receipt-like details for specific transactions.

SumUp Receipts API is one of 10 APIs that SumUp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.sumup.com.

1 operations 1 paths 12 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sumup.com
Authentication
HTTP Bearer, OAuth 2.0
License
Resource Areas
1

Authentication & Security 2

SumUp Receipts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (apiKey). It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 8 scopes.

  • apiKey — API keys allow you easily interact with SumUp APIs. API keys are static tokens. You can create API keys from the [Dashboard](https://me.sumup.com/settings/api-…
  • oauth2 — SumUp supports [OAuth 2.0](https://tools.ietf.org/html/rfc6749) authentication for platforms that want to offer their services to SumUp users. To integrate via…

Paths & Operations 1

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

Receipts 1

The Receipts model obtains receipt-like details for specific transactions.

GET
/v1.1/receipts/{transaction_id}
Retrieve receipt details
GetReceipt 3 params → 200400401404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ReceiptTransaction (20 properties), ReceiptEvent (7 properties), Problem (5 properties), Receipt (4 properties). Each schema is shown below with its type and property counts.

ReceiptCard
object
Payment card details displayed on the receipt.
2 properties
ReceiptReader
object
Card reader details displayed on the receipt.
2 properties
Error
object
Error message structure.
2 properties
ReceiptEvent
object
Transaction event details as rendered on the receipt.
7 properties
Receipt
object
Receipt details for a transaction.
4 properties
TransactionID
string
Unique ID of the transaction.
EventStatus
string
Status of the transaction event. Not every value is used for every event type. - PENDING: The event has been created but is not final yet. Used for events that…
Problem
object
A RFC 9457 problem details object. Additional properties specific to the problem type may be present.
5 properties 1 required
ReceiptTransaction
object
Transaction information.
20 properties
EventType
string
Type of the transaction event.
EventID
integer
Unique ID of the transaction event.
ReceiptMerchantData
object
Receipt merchant data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sumup-receipts-api-openapi.yml Raw ↑

Other APIs SumUp publishes across the network.

SumUp Checkouts API
SumUp Customers API
SumUp Members API
SumUp Memberships API
SumUp Merchants API
SumUp Payouts API
SumUp Readers API
SumUp Roles API
SumUp Transactions API
Where this information came from

This is an independent, third-party profile of SumUp Receipts 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.