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

Przelewy24 Additional API functionality API

The Additional API functionality API from Przelewy24 — 9 operation(s) for additional api functionality.

Przelewy24 Additional API functionality API is one of 13 APIs that Przelewy24 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Additional API functionality. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.

This API exposes 9 operations across 9 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.6.

Requests are made against 2 base URLs: https://sandbox.przelewy24.pl, https://secure.przelewy24.pl.

9 operations 9 paths 29 schemas 5 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.6
Base URL
https://secure.przelewy24.pl/api/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Przelewy24 Additional API functionality API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

  • basicAuth — This is the default authentication method. User login is API REST key the password assigned to it.

Paths & Operations 9

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

Additional API functionality 9
GET
/api/v1/testAccess
Test Access
→ 200400401
GET
/api/v1/payment/methods/{lang}?amount=150&subgroup=1¤cy=PLN
Payment Methods
4 params → 200403404
POST
/api/v1/transaction/refund
Refund transaction
body → 201400401409500
POST
/api/v1/transaction/registerOffline
Register offline transaction
body → 200400401409500
POST
/api/v1/transaction/register/ttl
Transaction Registration with ttl
body → 200400401
POST
/api/v1/transaction/register/splitpayment
Split Payment
body → 200400401
GET
/api/v1/refund/by/orderId/{orderId}
Refund by OrderID
1 param → 200401404500
GET
/api/v1/transaction/by/sessionId/{sessionId}
Get transaction by sessionID
1 param → 200400401404
GET
/api/v1/payment/methods/{lang}?amount=150¤cy=PLN
Payment Methods
3 params → 200403404

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are TransactionRegisterTtl (28 properties), TranstactionSplitPayment (27 properties), TransactionBySessionIdResponse (18 properties), PaymentMethodsResponseMethod (9 properties). Each schema is shown below with its type and property counts.

TransactionRegistrationOffline200
object
2 properties
TransactionRefund409
object
2 properties
TransactionRegisterOfflineRequest
object
1 property
TransactionRefund201Item
object
6 properties
CartParameters
object
Cart Parameters
7 properties 2 required
TransactionRefund409Item
object
6 properties
InvalidInputDataRefund
object
2 properties
TransactionRegisterTtl
object
28 properties 12 required
BasicResponse
object
2 properties
TransactionBySessionIdSuccessResponse
object
2 properties
UnauthorizedResponse
object
2 properties
TransactionNotFoundResponse
object
2 properties
TransactionRefundsInfoResponse
object
2 properties
TransactionRefund201
object
2 properties
TransactionRegistrationOffline409
object
2 properties
InvalidInputData
object
2 properties
TransactionBySessionIdResponse
object
18 properties
RefundsCollection
object
7 properties
TransactionWithRefundsResponse
object
5 properties
Refund500Response
object
2 properties
availabilityHours
object
An object containing information about the method's availability hours (methods with ID 177, 178 return bool true/false information)
3 properties
TranstactionSplitPayment
object
27 properties 13 required
TransactionTestAccess200
object
2 properties
PaymentMethodsResponseMethod_2
object
9 properties
PaymentMethodsResponseMethod
object
9 properties
ErrorCodeResponse
object
2 properties
TransactionRefundJsonRequestBody
object
4 properties 3 required
TransactionRegistrationResponse
object
2 properties
RefundRequestArrayDataBasic
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

przelewy24-additional-api-functionality-api-openapi.yml Raw ↑

Other APIs Przelewy24 publishes across the network.

Przelewy24 Additional services Mass Payments Transactions API
Przelewy24 APay API API
Przelewy24 BLIK API API
Przelewy24 Card API API
Przelewy24 Ekspres P24 API API
Przelewy24 GPay API API
Przelewy24 Marketplace Management API API
Przelewy24 Marketplace Merchant API API
Przelewy24 Marketplace Partner API API
Przelewy24 Recursion (doPayment) API
Przelewy24 Report API API
Przelewy24 Transaction service API API
Where this information came from

This is an independent, third-party profile of Przelewy24 Additional API functionality 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.