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 ghostCard API

The ghostCard API from Payabli — 2 operation(s) for ghostcard.

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

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 14 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.

2 operations 2 paths 14 schemas 1 PATCH1 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 ghostCard 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 2

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

ghostCard 2
POST
/MoneyOutCard/GhostCard/{entry}
Create ghost card
CreateGhostCard 2 params body → 200400401500503
PATCH
/MoneyOutCard/card/{entry}
Update card status
UpdateCard 2 params body → 200400401500503

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are CreateGhostCardRequestBody (16 properties), PayabliErrorBody (4 properties), CreateGhostCardResponse (3 properties), PayabliApiResponse (3 properties). Each schema is shown below with its type and property counts.

UpdateCardRequestBody
object
2 properties 1 required
ResultCode
integer
Result code for the operation. Value 1 indicates a successful operation, values 2 and 3 indicate errors. A value of 10 indicates that an operation has been ini…
Entry
string
The entity's entrypoint identifier. [Learn more](/developers/api-reference/api-overviewentrypoint-vs-entry).
PayabliErrorBody
object
Shape returned by every Payabli API error response. The responseData object carries human-readable error context.
4 properties 2 required
PayabliApiResponse
object
3 properties 1 required
PayabliErrorBodyResponseData
object
Object with detailed error context.
2 properties
Responsedata
object
The object containing the response data.
CardStatus
string
The status to set on the card. Not all transitions are valid: Active can change to Inactive, Cancelled, or Expired. Inactive can change to Active. Expired can…
CreateGhostCardResponseData
object
3 properties
CreateGhostCardRequestBody
object
16 properties 11 required
ResponseText
string
Response text for operation: 'Success' or 'Declined'.
IsSuccess
boolean
Boolean indicating whether the operation was successful. A true value indicates success. A false value indicates failure.
CreateGhostCardResponse
object
Response for creating a ghost card.
3 properties 1 required
Resulttext
string
Text describing the result. If ResultCode = 1, will return Approved or a general success message. If ResultCode = 2 or 3, will contain the cause of the error o…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payabli-ghostcard-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 hostedPaymentPages API
Payabli Import API
Payabli Invoice API
Payabli lineItem API
Where this information came from

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