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

Papaya Global Groups API

Manage payment groups to consolidate payment requests

Papaya Global Groups API is one of 5 APIs that Papaya Global publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Group. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

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

Requests are made against 2 base URLs: https://api.papayaglobal.com/api/v1, https://sandbox.papayaglobal.com/api/v1.

7 operations 3 paths 7 schemas 2 DELETE2 GET1 PATCH1 POST1 PUT

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.papayaglobal.com/api/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Papaya Global Groups API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Groups 7

Manage payment groups to consolidate payment requests

POST
/payments/groups
Create Payment Group
createGroup body → 201400401
GET
/payments/groups
List Payment Groups
listGroups 7 params → 200401
GET
/payments/groups/{id}
Get Group Details
getGroup 1 param → 200401404
PUT
/payments/groups/{id}
Update Payment Group
updateGroup 1 param body → 200400401404
DELETE
/payments/groups/{id}
Delete Payment Group
deleteGroup 2 params → 200401404
PATCH
/payments/groups/{id}/lock
Lock Payment Group
lockGroup 1 param → 200401404
DELETE
/payments/groups/{id}/lock
Unlock Payment Group
unlockGroup 1 param → 200401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Wallet (9 properties), Group (7 properties), Error (5 properties), GroupCreateRequest (4 properties). Each schema is shown below with its type and property counts.

GroupWithInfo
GroupCreateRequest
object
4 properties 2 required
Error
object
5 properties
Wallet
object
9 properties
Group
object
7 properties
GroupUpdateRequest
object
3 properties
Paging
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

papaya-global-groups-api-openapi.yml Raw ↑

Other APIs Papaya Global publishes across the network.

Papaya Global Authentication API
Papaya Global Beneficiaries API
Papaya Global Payments API
Papaya Global Wallets API
Where this information came from

This is an independent, third-party profile of Papaya Global Groups 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.