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

PPRO Merchants API

Merchant management

PPRO Merchants API is one of 18 APIs that PPRO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 4 paths, and defines 35 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.sandbox.eu.ppro.com.

8 operations 4 paths 35 schemas 2 DELETE2 GET1 PATCH2 POST1 PUT

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.eu.ppro.com
License
Proprietary
Resource Areas
1

Paths & Operations 8

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

Merchants 8

Merchant management

POST
/v1/merchants
Create a Merchant
createMerchant body → 201400403404405409429500
GET
/v1/merchants/{merchant-id}
Get Merchant Details
getMerchant 1 param → 200400403404405409429500
PATCH
/v1/merchants/{merchant-id}
Update a Merchant
updateMerchant 1 param body → 200400403404405409429500
PUT
/v1/merchants/{merchant-id}
Replace a Merchant
replaceMerchant 1 param body → 200400403404405409429500
DELETE
/v1/merchants/{merchant-id}
Deactivate a Merchant
deactivateMerchant 1 param → 204400403404405409429500
GET
/v1/merchants/{merchant-id}/people
List People for Merchant
listMerchantPeople 1 param → 200400403404405409429500
POST
/v1/merchants/{merchant-id}/people
Associate a person with a Merchant
associatePersonWithMerchant 1 param body → 201400403404405409429500
DELETE
/v1/merchants/{merchant-id}/people/{person-id}
Dissociate a person from a Merchant
dissociatePersonFromMerchant 2 params → 204400403404405409429500

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are CreateMerchantRequest (18 properties), UpdateMerchantRequest (14 properties), ReplaceMerchantRequest (14 properties), PersonDetails (11 properties). Each schema is shown below with its type and property counts.

UpdateMerchantRequest
object
14 properties
LegalEntityType
string
Classification of the business structure. Allowed values: COMPANY, PARTNERSHIP, SOLETRADER, INDIVIDUAL, NONPROFIT.
ExternalReference
string
Unique reference, assigned by external client.
PaymentDescriptor
string
The text customers see on their bank statement for transactions from this store.
CreatedAt
string
Timestamp when the resource was created. UTC timezone. Format YYYY-MM-DDTHH:MM:SS.ssssssZ
PhoneNumber
string
WebsiteUrl
string
An e-commerce website or public-facing digital storefront.
LegalEntityRegistrationNumber
string
A unique identifier assigned to the business upon incorporation by a government or regulatory authority.
PlatformId
string
Unique identifier for the platform
MerchantCategoryCode
string
Merchant Category Code assigned to the business, indicating the type of goods or services sold.
MonthlyTransactionCount
integer
The expected or historical number of transactions processed per month.
CreatePersonRequest
object
8 properties 4 required
CreateMerchantResponse
Merchant created payload including initial people assignments.
MerchantId
string
Unique identifier for the merchant
Error
object
3 properties 3 required
MerchantDetails
Merchant record as returned by Entity .
MerchantPersonDetails
object
Person linked to a merchant with assigned relationship type.
2 properties 2 required
MerchantTradeName
string
The name the business operates under in public-facing contexts. This is the "doing business as" (DBA) name and may differ from the legal name.
Address
object
5 properties 3 required
IncorporationDate
string
The date the business was legally registered or incorporated.
PersonDetails
object
Person record with audit timestamps aligned to Entity .
11 properties 6 required
LegalEntityName
string
The officially registered name of the business as recorded in legal or governmental registries.
EmailAddress
string
An email address.
CreateMerchantRequest
object
18 properties 6 required
Currency
string
ISO-4217 currency code (e.g., EUR, USD)
PersonId
string
Unique identifier for the person
RelationshipType
string
The relationship type of the person in relation to the business (e.g., DIRECTOR, ULTIMATEBENEFICIALOWNER)
ReplaceMerchantRequest
object
14 properties 5 required
PersonLinkRequest
object
Request payload to associate an existing person with a merchant.
2 properties 2 required
AverageTransactionValue
number
The typical value of a single transaction. Major units, example 50.00
UpdatedAt
string
Timestamp when the resource was last updated. UTC timezone. Format YYYY-MM-DDTHH:MM:SS.ssssssZ
PspId
string
Unique identifier for the PSP
CreateMerchantPersonRequest
object
3 properties 1 required
SimpleApiWebhooksUrl
string
The endpoint where Simple API (v1) event webhooks should be sent.
CountryCode
string
ISO 3166-1 alpha-2 Country Code

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ppro-merchants-api-openapi.yml Raw ↑

Other APIs PPRO publishes across the network.

PPRO Authorization Endpoints API
PPRO Capture Endpoints API
PPRO Dispute Reports API
PPRO Disputes API
PPRO Enrollment Endpoints API
PPRO Internal API
PPRO Payment Agreement Revocations API
PPRO Payment Agreements API
PPRO Payment Charge Controller API
PPRO Payment Charges API
PPRO Payment Instruments API
PPRO Payment Sessions API
Where this information came from

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