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

Payabli Wallet API

The Wallet API from Payabli — 4 operation(s) for wallet.

Payabli Wallet API is one of 33 APIs that Payabli publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Wallets. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 2 base URLs: https://api-sandbox.payabli.com/api, https://api.payabli.com/api.

4 operations 4 paths 33 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.payabli.com/api
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Payabli Wallet API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the header as requestToken (APIKeyAuth).

  • BearerAuth — OAuth2 Bearer access token from the client-credentials flow. See [OAuth authentication](/developers/oauth-authentication).
  • APIKeyAuth — Long-lived API token sent in the requestToken header. See [API token authentication](/developers/api-tokens).

Paths & Operations 4

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

Wallet 4
POST
/Wallet/applepay/configure-organization
Configure Apple Pay for an organization
ConfigureApplePayOrganization 1 param body → 200400401500503
POST
/Wallet/applepay/configure-paypoint
Configure Apple Pay for a paypoint
ConfigureApplePayPaypoint 1 param body → 200400401500503
POST
/Wallet/googlepay/configure-organization
Configure Google Pay for an organization
ConfigureGooglePayOrganization 1 param body → 200400401500503
POST
/Wallet/googlepay/configure-paypoint
Configure Google Pay for a paypoint
ConfigureGooglePayPaypoint 1 param body → 200400401500503

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are AppleWalletData (10 properties), ApplePayOrganizationUpdateData (8 properties), ConfigureApplePaypointApiResponse (6 properties), ConfigureGooglePaypointApiResponse (6 properties). Each schema is shown below with its type and property counts.

ApplePayType
string
The record type.
AppleWalletData
object
The wallet data.
10 properties
JobStatus
string
The cascade process status.
ApplePayId
string
The internal identifier for Apple Pay-related information.
ConfigureGooglePaypointApiResponse
object
6 properties 5 required
IsEnabled
boolean
When true, the service is enabled.
JobId
string
The cascade process ID.
PayabliErrorBody
object
Shape returned by every Payabli API error response. The responseData object carries human-readable error context.
4 properties 2 required
ConfigureOrganizationRequestApplePay
object
3 properties
PayabliErrorBodyResponseData
object
Object with detailed error context.
2 properties
OrganizationUpdates
object
2 properties
WalletIsEnabled
boolean
When true, wallet service is enabled.
ConfigureApplePayOrganizationApiResponse
object
5 properties 1 required
GooglePayPaypointRegistrationData
object
4 properties
Entry
string
The entity's entrypoint identifier. [Learn more](/developers/api-reference/api-overviewentrypoint-vs-entry).
OrganizationId
integer
Organization ID for the target organization.
Cascade
boolean
When true, the wallet service configuration cascades to all paypoints and suborganizations belonging to the parent entity.
LastModified
string
Timestamp of when record was last updated, in UTC.
PageIdentifier
string
Auxiliary validation used internally by payment pages and components.
IsSuccess
boolean
Boolean indicating whether the operation was successful. A true value indicates success. A false value indicates failure.
ConfigureOrganizationRequestGooglePay
object
3 properties
Responsecode
integer
Code for the response. Learn more in [API Response Codes](/developers/api-reference/api-responses).
WalletCascade
boolean
When true, the wallet service configuration cascades to all paypoints and suborganizations belonging to the parent entity.
ConfigurePaypointRequestGooglePay
object
2 properties
ApplePayOrganizationUpdateData
object
8 properties
ConfigureApplePaypointApiResponse
object
6 properties 1 required
DomainName
string
The domain. For example: subdomain.domain.com or domain.com. Must be public. Can't be localhost, hidden by a VPN, or protected by a password.
ApplePayPaypointRegistrationData
object
4 properties
PaypointName
string
The paypoint name.
GoogleWalletData
object
The wallet data.
2 properties
CreatedAt
string
Timestamp of when record was created, in UTC.
ResponseText
string
Response text for operation: 'Success' or 'Declined'.
ConfigurePaypointRequestApplePay
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payabli-wallet-api-openapi.yml Raw ↑

Other APIs Payabli publishes across the network.

Payabli Bill API
Payabli Boarding API
Payabli chargeBacks API
Payabli checkCapture API
Payabli Cloud API
Payabli Customer API
Payabli Export API
Payabli Funding API
Payabli ghostCard API
Payabli hostedPaymentPages API
Payabli Import API
Payabli Invoice API
Where this information came from

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