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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Loopay

Loopay Payout API

The Payout API from Loopay — 6 operation(s) for payout.

Documentation Provider Profile APIs.io OpenAPI GitHub

Loopay Payout API is one of 15 APIs that Loopay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.2.0.

Requests are made against a single base URL, https://api.loopay.com.

6 operations 6 paths 3 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.2.0
Base URL
https://api.loopay.com
Contact
Loopay Team
Resource Areas
1

Paths & Operations 6

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

Payout 6
POST
/payout/create
Create a payOut Create a single payout given a payout object
Payout.createSelfPayOut 2 params body → 200202
GET
/payout/{id}
Get a payOut Get a single payout given a payout id
Payout.selfPayOut 2 params → 200
POST
/payouts/byExternalIdentifierList
Get self payOuts by externalIdentifier Get a list of payOuts by a list of externalIdentifier and companyProductId
Payout.getSelfPayOutsByExternalIdentifierList 1 param body → 200
POST
/payouts/create
Create payOuts Create several payouts given a company id, company product id and a data array of payout objects
Payout.createSelfPayOutMany 2 params body → 200202
POST
/payouts/sign
Sign payOuts Sign several payouts given an array of payout ids
Payout.createManySignedPayouts 1 param body → 200
GET
/payouts
Get all payOuts Gets all payOuts created by the currently registered user, belonging to the company of the user
Payout.selfPayOuts 3 params → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are PayOut (23 properties), PayOutWithRelations (23 properties), CreaateSelfPayOut (15 properties). Each schema is shown below with its type and property counts.

PayOutWithRelations
object
(tsType: PayOutWithRelations, schemaOptions: { includeRelations: true })
23 properties 11 required
PayOut
object
23 properties 11 required
CreaateSelfPayOut
object
(tsType: CreateSelfPayOutInput, schemaOptions: { title: 'CreaateSelfPayOut' })
15 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loopay-payout-api-openapi.yml Raw ↑

Other APIs Loopay publishes across the network.

Loopay Affiliate API
AE Profile APIs.io
Loopay Bank API
AE Profile APIs.io
Loopay Company API
AE Profile APIs.io
Loopay CompanyProduct API
AE Profile APIs.io
Loopay Country API
AE Profile APIs.io
Loopay Currency API
AE Profile APIs.io
Loopay DocumentType API
AE Profile APIs.io
Loopay Movements API
AE Profile APIs.io
Loopay PaidMethods API
AE Profile APIs.io
Loopay PayIn API
AE Profile APIs.io
Loopay PhysicalPoint API
AE Profile APIs.io
Loopay SourcesOfPayment API
AE Profile APIs.io
#Payout
← Back to L APIs
API Details
ID
loopay:loopay-payout-api
Base URL
https://api.loopay.com
Docs
https://api.loopay.com/explorer
Provider
Loopay
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=loopay-payout-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/loopay-payout-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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