Show payout batch details
GET/payouts/:id
Shows the latest status of a batch payout. Includes the transaction status and other data for individual payout items.
Request
Path Parameters
Possible values: non-empty
and <= 1000 characters
, Value must match regular expression ^.*$
The ID of the payout for which to show details.
Query Parameters
Possible values: non-empty
and <= 1000 characters
, Value must match regular expression ^.*$
Shows details for only the specified fields.
Possible values: <= 1000
A non-zero integer representing the page of the results.
1
Possible values: <= 1000
The maximum number of results to return at one time. Value is a non-negative, non-zero integer. If the user chooses pagination, the maximum page is 1000
.
Indicates whether to show the total items and total pages count in the response.
false
Responses
- 200
- 404
- 500
- default
A successful request returns the HTTP 200 OK
status code and a JSON response body that shows batch payout details.
- application/json
- Schema
- Example (from schema)
Schema
- An integer for currencies like
JPY
that are not typically fractional. - A decimal fraction for currencies like
TND
that are subdivided into thousandths. - An integer for currencies like
JPY
that are not typically fractional. - A decimal fraction for currencies like
TND
that are subdivided into thousandths.
The total number of items in the full result list.
Possible values: <= 15000
The total number of pages.
Possible values: <= 1000
An array of individual items.
Possible values: <= 15000
batch_header
object
A payout header. Includes the generated payout status.
The PayPal-generated ID for a payout.
Possible values: <= 30 characters
, Value must match regular expression ^.*$
The date and time when processing for the payout began, in Internet date and time format.
Possible values: <= 100 characters
The date and time when processing for the payout was completed, in Internet date and time format.
Possible values: <= 100 characters
The date and time when the payout was closed, in Internet date and time format. A payout is considered closed when all items in a batch are processed and the available balance from the temporary hold is released.
Possible values: <= 100 characters
The PayPal-generated payout status. If the payout passes preliminary checks, the status is PENDING
.
Possible values: non-empty
and <= 36 characters
, Value must match regular expression ^[0-9A-Z_]+$
, [DENIED
, PENDING
, PROCESSING
, SUCCESS
, CANCELED
]
sender_batch_header
object
required
The original payout header, as provided by the payment sender.
The sender-specified ID number. Tracks the payout in an accounting system.
Note:PayPal does not process duplicate payouts. If you specify a
sender_batch_id
that was used in the last 30 days, the API rejects the request with an error message that shows the duplicatesender_batch_id
and includes a HATEOAS link to the original payout with the samesender_batch_id
.If you receive an HTTP
5nn
status code, you can safely retry the request with the samesender_batch_id
. The API completes a payment only once for asender_batch_id
that is used within 30 days.
Possible values: <= 256 characters
, Value must match regular expression ^.*$
The subject line for the email that PayPal sends when payment for a payout item completes. The subject line is the same for all recipients. Value is an alphanumeric string with a maximum length of 255 single-byte characters.
Possible values: <= 255 characters
, Value must match regular expression ^.*$
The email message that PayPal sends when the payout item completes. The message is the same for all recipients.
Possible values: <= 1000 characters
, Value must match regular expression ^.*$
The ID type that identifies the payment receiver.
Possible values: non-empty
and <= 36 characters
, Value must match regular expression ^[0-9A-Z_]+$
, [EMAIL
, PHONE
, PAYPAL_ID
]
The ID to differentiate a PayPal balance-funded transaction from a PayPal treasury-funded transaction.
Possible values: non-empty
and <= 36 characters
, Value must match regular expression ^[0-9A-Z_]+$
, [BALANCE
]
amount
object
The currency and total amount requested for the payouts.
The value, which might be:
fees
object
The currency and amount of the total estimate for the applicable payouts fees. Initially, the fee is 0
. The fee is populated after the payout moves to the PROCESSING
state.
The value, which might be:
{
"total_items": 0,
"total_pages": 0,
"items": [
{
"payout_item_id": "string",
"transaction_id": "string",
"activity_id": "string",
"payout_batch_id": "string",
"time_processed": "2024-07-29T15:51:28.071Z",
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
],
"transaction_status": "SUCCESS",
"payout_item_fee": {
"currency": "string",
"value": "string"
},
"payout_item": {
"note": "string",
"receiver": "string",
"sender_item_id": "string",
"recipient_type": "EMAIL",
"amount": {
"currency": "string",
"value": "string"
},
"recipient_name": {
"prefix": "string",
"given_name": "string",
"surname": "string",
"middle_name": "string",
"suffix": "string",
"alternate_full_name": "string",
"full_name": "string"
},
"recipient_wallet": "PAYPAL",
"purpose": "AWARDS"
},
"currency_conversion": {
"exchange_rate": "string",
"from_amount": {
"currency": "string",
"value": "string"
},
"to_amount": {
"currency": "string",
"value": "string"
}
},
"errors": {
"name": "string",
"message": "string",
"debug_id": "string",
"information_link": "string",
"details": [
{
"field": "string",
"value": "string",
"location": "body",
"issue": "string",
"description": "string"
}
],
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
]
}
}
],
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
],
"batch_header": {}
}
Resource Not Found.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
The human-readable, unique name of the error.
The message that describes the error.
The PayPal internal ID. Used for correlation purposes.
The information link, or URI, that shows detailed information about this error for the developer.
details
object[]
An array of additional details about the error.
The field that caused the error. If this field is in the body, set this value to the field's JSON pointer value. Required for client-side errors.
The value of the field that caused the error.
The location of the field that caused the error. Value is body
, path
, or query
.
body
The unique, fine-grained application-level error code.
The human-readable description for an issue. The description can change over the lifetime of an API, so clients must not depend on this value.
links
object[]
An array of request-related HATEOAS links.
The complete target URL. To make the related call, combine the method with this URI Template-formatted link. For pre-processing, include the $
, (
, and )
characters. The href
is the key HATEOAS component that links a completed call with a subsequent call.
The link relation type, which serves as an ID for a link that unambiguously describes the semantics of the link. See Link Relations.
The HTTP method required to make the related call.
Possible values: [GET
, POST
, PUT
, DELETE
, HEAD
, CONNECT
, OPTIONS
, PATCH
]
{
"name": "string",
"message": "string",
"debug_id": "string",
"information_link": "string",
"details": [
{
"field": "string",
"value": "string",
"location": "body",
"issue": "string",
"description": "string"
}
],
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
]
}
An internal server error has occurred.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
The human-readable, unique name of the error.
The message that describes the error.
The PayPal internal ID. Used for correlation purposes.
The information link, or URI, that shows detailed information about this error for the developer.
details
object[]
An array of additional details about the error.
The field that caused the error. If this field is in the body, set this value to the field's JSON pointer value. Required for client-side errors.
The value of the field that caused the error.
The location of the field that caused the error. Value is body
, path
, or query
.
body
The unique, fine-grained application-level error code.
The human-readable description for an issue. The description can change over the lifetime of an API, so clients must not depend on this value.
links
object[]
An array of request-related HATEOAS links.
The complete target URL. To make the related call, combine the method with this URI Template-formatted link. For pre-processing, include the $
, (
, and )
characters. The href
is the key HATEOAS component that links a completed call with a subsequent call.
The link relation type, which serves as an ID for a link that unambiguously describes the semantics of the link. See Link Relations.
The HTTP method required to make the related call.
Possible values: [GET
, POST
, PUT
, DELETE
, HEAD
, CONNECT
, OPTIONS
, PATCH
]
{
"name": "string",
"message": "string",
"debug_id": "string",
"information_link": "string",
"details": [
{
"field": "string",
"value": "string",
"location": "body",
"issue": "string",
"description": "string"
}
],
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
]
}
The error response.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
The human-readable, unique name of the error.
The message that describes the error.
The PayPal internal ID. Used for correlation purposes.
The information link, or URI, that shows detailed information about this error for the developer.
details
object[]
An array of additional details about the error.
The field that caused the error. If this field is in the body, set this value to the field's JSON pointer value. Required for client-side errors.
The value of the field that caused the error.
The location of the field that caused the error. Value is body
, path
, or query
.
body
The unique, fine-grained application-level error code.
The human-readable description for an issue. The description can change over the lifetime of an API, so clients must not depend on this value.
links
object[]
An array of request-related HATEOAS links.
The complete target URL. To make the related call, combine the method with this URI Template-formatted link. For pre-processing, include the $
, (
, and )
characters. The href
is the key HATEOAS component that links a completed call with a subsequent call.
The link relation type, which serves as an ID for a link that unambiguously describes the semantics of the link. See Link Relations.
The HTTP method required to make the related call.
Possible values: [GET
, POST
, PUT
, DELETE
, HEAD
, CONNECT
, OPTIONS
, PATCH
]
{
"name": "string",
"message": "string",
"debug_id": "string",
"information_link": "string",
"details": [
{
"field": "string",
"value": "string",
"location": "body",
"issue": "string",
"description": "string"
}
],
"links": [
{
"href": "string",
"rel": "string",
"method": "GET"
}
]
}