# Retrieve payout request allocations Retrieves a list of payout request allocations. Endpoint: GET /payout-request-allocations Version: latest Security: SecretApiKey, JWT ## Security: - `SecretApiKey` (unknown) apiKey in header REB-APIKEY - `JWT` (unknown) http bearer JWT ## Query parameters: - `limit` (integer) Limit the number of collection items to be returned. Use `0` to return an empty collection and still receive the count of matching items in `Pagination-Total`. - `offset` (integer) Specifies the starting point within the collection of items to be returned. - `filter` (string) Criteria for filtering collection items. This field requires a special format. Use `,` to specify multiple allowed values. Use `;` to specify multiple fields. For more information, see [Search filters](https://www.rebilly.com/docs/dev-docs/search-filters). - `sort` (array) Sorts and orders the collection of items. To sort in descending order, prefix with `-`. Multiple fields can be sorted by separating each with `,`. ## Response 200: - `200` (unknown) List of payout request allocations retrieved. ## Response 200 fields (application/json): - `id` (string) ID of the resource. Example: pra_0YVDMDE2BMC6KBB5MX76RF6T80 - `payoutRequestId` (string, required) ID of the payout request associated with this allocation. Example: pout_req_0YVDMDE2BMC6KBB5MX76RF6T80 - `batchId` (string | null) ID of the payout request batch that contains the payout request for this allocation. Example: prb_0YVDMDE2BMC6KBB5MX76RF6T80 - `paymentInstrumentId` (string, required) ID of the payment instrument allocated to the payout request. Example: inst_0YVB8KPKNXCBR9EDX7JHSED75N - `paymentMethod` (string) Payment method of the allocation. Enum: "payment-card", "ach", "cash", "check", "paypal", "AdvCash", "Aera", "Affirm", "Afterpay", "Aircash", "Airpay", "Alfa-click", "Alipay", "AmazonPay", "Apple Pay", "AstroPay Card", "AstroPay-GO", "BankSEND", "BankReferenced", "bank-transfer", "bank-transfer-2", "bank-transfer-3", "bank-transfer-4", "bank-transfer-5", "bank-transfer-6", "bank-transfer-7", "bank-transfer-8", "bank-transfer-9", "Baloto", "Beeline", "Belfius-direct-net", "bitcoin", "Bizum", "Blik", "Boleto", "Boleto-2", "Boleto-3", "cash-deposit", "CASHlib", "CashToCode", "CCAvenue", "China UnionPay", "Clearpay", "Cleo", "CODVoucher", "Conekta-oxxo", "Conekta-spei", "cryptocurrency", "Cupon-de-pagos", "CyberSource", "Dimoco-pay-smart", "Directa24Card", "domestic-cards", "Efecty", "echeck", "ecoPayz", "ecoPayzTurkey", "ecoVoucher", "EPS", "ePay.bg", "Ethereum", "e-wallet", "ezyEFT", "eZeeWallet", "FasterPay", "Flexepin", "Giropay", "Google Pay", "Gpaysafe", "iCashOne Voucher", "iDebit", "iDEAL", "ING-homepay", "INOVAPAY-pin", "INOVAPAY-wallet", "InstaDebit", "InstantPayments", "instant-bank-transfer", "Interac-online", "Interac-eTransfer", "Interac-express-connect", "Interac", "invoice", "iWallet", "Jeton", "JetonCash", "jpay", "KakaoPay", "Khelocard", "Klarna", "KNOT", "Litecoin", "loonie", "LPG-online", "LPG-payment-card", "Matrix", "MaxiCash", "Megafon", "MercadoPago", "MiFinity-eWallet", "miscellaneous", "MobilePay", "Mollie", "Multibanco", "Bancontact", "Bancontact-mobile", "MTS", "MuchBetter", "MuchBetterVoucher", "MyFatoorah", "Neosurf", "Netbanking", "Neteller", "Nordea-Solo", "NordikCoin", "OchaPay", "online-bank-transfer", "Onlineueberweisen", "oriental-wallet", "OXXO", "P24", "Pagadito", "PagoEffectivo", "Pagsmile-lottery", "Pagsmile-deposit-express", "PayCash", "Payco", "Payeer", "PaymentAsia-crypto", "Paysafecard", "PayTabs", "Pay4Fun", "Paynote", "Paymero", "Paymero-QR", "PayU", "PayULatam", "Perfect-money", "Piastrix", "PIX", "PIX-Automatico", "PinPay", "phone", "PhonePe", "POLi", "PostFinance-card", "PostFinance-e-finance", "QIWI", "QPay", "QQPay", "Quickpay", "rapyd-checkout", "rebilly-hosted-payment-form", "Resurs", "reverse-withdrawal", "Ripple", "SafetyPay", "Samsung Pay", "SEPA", "Siirto", "Skrill", "Skrill Rapid Transfer", "SMSVoucher", "Sofort", "SparkPay", "SPEI", "swift-dbt", "Tele2", "Telr", "Terminaly-RF", "Tether", "Thunes-Checkout", "ToditoCash-card", "Trustly", "Tupay", "TWINT", "UniCrypt", "UPayCard", "UPI", "USD-coin", "VCreditos", "VegaWallet", "VenusPoint", "Viva", "voucher", "voucher-2", "voucher-3", "voucher-4", "Wallet88", "Webmoney", "Webpay", "Webpay-2", "Webpay Card", "WeChat Pay", "XPay-P2P", "XPay-QR", "Yandex-money", "Zotapay", "Zimpler", "Zip" - `gatewayAccountId` (string, required) ID of the gateway account to use for processing this allocation. Example: gateway_0YVB8KPKNXCBR9EDX7JHSED75N - `gatewayName` (string) Name of the gateway account to use for processing this allocation. Example: TestProcessor - `gatewayPayoutInstruction` (string | null) Payout configuration of the gateway account that processes this allocation. Enum: "all", "covered-payout", "approved-payment", "none", null - `amount` (number, required) Amount allocated to this payment instrument. - `exposureAmount` (number) Approved sales and captures minus approved payouts for the customer, gateway account, and payment instrument, in the allocation currency. The calculation includes only transactions created within the last 180 days. The value is `0` when there are no transactions in the last 180 days, the gateway account is inactive, or its `readyToPayoutInstruction` is `none`. Example: 2 - `currency` (string, required) Currency code in ISO 4217 format. Example: USD - `status` (string) Status of this payout request allocation. Enum: "pending", "queued", "processing", "waiting-completion", "completed", "failed", "canceled", "declined" - `transactionId` (string | null) ID of the transaction that is created when processing this allocation, if applicable. Example: txn_0YVB8KPKNXCBR9EDX7JHSED75N - `transactionResult` (string | null) Result of the transaction created for this allocation, if applicable. Enum: "abandoned", "approved", "canceled", "declined", "unknown", null - `transactionStatus` (string | null) Status of the transaction created for this allocation, if applicable. Enum: "completed", "conn-error", "disputed", "never-sent", "offsite", "partially-refunded", "pending", "refunded", "sending", "timeout", "voided", "waiting-approval", "waiting-capture", "waiting-gateway", "waiting-refund", null - `createdTime` (string) Date and time when the resource is created. This value is set automatically when the resource is created. - `updatedTime` (string) Date and time when the resource is updated. This value is set automatically when the resource is updated. - `_links` (array) Related links. - `_links.href` (string) Link URL. - `_links.rel` (string) Type of link. Enum: "self", "transaction", "gatewayAccount", "payoutRequest", "paymentInstrument" ## Response 200 headers (application/json): - `Pagination-Total` (integer) Total number of items that match the request. The value is independent of `limit`, including when `limit` is `0`. Example: 332 - `Pagination-Limit` (integer) Maximum number of items per page. Example: 100 - `Pagination-Offset` (integer) Specifies the starting point within the collection of resource results. For example, a request with `limit=20` retrieves and displays the first 20 results on a page. A following request with `limit=20` and `offset=20`, retrieves the next page of 20 results. Example: 2 ## Response 401: - `401` (unknown) Unauthorized access. Invalid credentials used. ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403: - `403` (unknown) Access forbidden. If the organization requires multi-factor authentication (MFA) and the session has not passed MFA, `error` is `mfa_required`. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `error` (string) Message that describes why the request is forbidden. Most responses use a descriptive message, such as `Not allowed to change security settings`. If the organization requires multi-factor authentication (MFA) and MFA verification has not been completed for the session, this value is `mfa_required`. If the request sets `requireMfa` to `true` and MFA verification has not been completed for the session, this value is `mfa_required_for_caller`. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.