> ## Documentation Index > Fetch the complete documentation index at: https://developer.meow.com/llms.txt > Use this file to discover all available pages before exploring further. # List Wire Drawdown Requests > Returns every wire drawdown request made against your accounts, pending ones first. A drawdown is a vendor asking you to wire them funds; nothing moves until you approve it. ## OpenAPI ````yaml GET /wire-drawdowns openapi: 3.1.0 info: title: Meow API description: > ## Overview The Meow API provides financial services and billing capabilities for your business. ### Core Features - **Financial data access**: access account information, transactions, balances, and payment networks. - **Crypto operations**: create and manage crypto contacts, and initiate USDC transfers across blockchain networks. - **Bill pay**: draft bills payable to your vendors and track them through payment. ### Bill Pay API The Bill Pay API lets you create bills for your vendors and track them through payment: - **Bill drafting**: create bills as drafts. Nothing is paid until someone approves the bill in the Meow dashboard. - **Attachments**: upload invoices and supporting documents to a bill. - **Bulk loads**: send an `Idempotency-Key` with every create so a retry never duplicates a bill. Drafting is capped at 500 bills per rolling 24 hours per creator — your entity key, or the user a user-scoped key acts as. Creates past the cap return `429 Too Many Requests`. ### Billing API The Billing API lets you create and manage invoices and collect payments: - **Product management**: create and manage products with custom pricing. - **Customer management**: maintain invoicing customers with their addresses. - **Invoice creation**: generate invoices with line items, discounts, and custom notes. - **Payment options**: accept payments via ACH, wire, international wire, card, and USDC. - **Collection accounts**: configure accounts for payment collection. ### Getting Started Authenticate by sending your API key in the `x-api-key` request header. To scope requests to a specific entity, include the `x-entity-id` header. Use the `/api-keys/accessible-entities` endpoint to list all entities accessible by your API key. ### Rate Limits Each API key has a limit of 1,200 requests per minute, unless Meow has agreed a different limit with you. The limit works as a token bucket: you can spend the whole minute at once, and requests return steadily over the minute. Responses carry the `RateLimit-Policy` and `RateLimit` headers. They show your limit, the requests you have left, and the seconds until your full limit is back. These headers are informational today: going over the limit is logged, not rejected. A separate, coarser safeguard protects the API from abusive traffic and can reject requests with `429 Too Many Requests`. It returns a `Retry-After` header and a body with `error_code` set to `rate_limited` and a `message`, but not the quota headers above. Wait at least `Retry-After` seconds and add a small random delay. If the retry is limited again, back off exponentially. Send an `Idempotency-Key` when you retry a request that creates something or moves money. ### Error Responses Errors return JSON with `code`, `message`, and `debug_message`. The `code` aligns with FDX where possible; use `debug_message` for troubleshooting only. Common error codes: - `500`: Internal server error - `501`: Subsystem unavailable - `503`: Scheduled maintenance - `601`: Data not found - `602`: Customer not authorized - `701`: Account not found - `703`: Invalid input (including invalid date ranges) - `704`: Account type not supported - `705`: Account is closed - `801`: Transaction not found contact: name: Meow url: https://meow.com/ email: support@meow.com version: 1.0.0 license: name: Proprietary url: https://www.meow.com/terms-of-service servers: - url: https://api.meow.com/v1 description: Meow API Production - url: https://api.sandbox.meow.com/v1 description: Meow API Sandbox - url: https://api.dev.meow.com/v1 description: Meow API Development security: - apiKeyAuth: [] tags: - name: API Keys description: Retrieve metadata about API keys and their accessible entities. - name: Accounts description: Access and manage accounts. - name: Approvals - name: Balances description: Retrieve account balances and available funds. - name: Bill Pay - name: Bills description: View and manage bills for vendor payments. - name: Cards description: Manage virtual and physical cards, and view transactions and insights. - name: Collection Accounts description: Manage accounts for payment collection. - name: Contacts description: Manage contacts for crypto and USDC transfers. - name: Customers description: Manage invoicing customers and their details. - name: Entities - name: Feature Access description: >- Request access to restricted features, such as international payments, and track the status of your requests. - name: Invoices description: Create and manage invoices. - name: Limits - name: Line Items description: Manage invoice line items. - name: Partner Onboarding description: Onboard entities using your partner API key. - name: Partner Webhooks - name: Payment Methods description: View available payment method types. - name: Payment Networks description: Manage payment networks and routing information. - name: Products description: Manage products and pricing for invoicing. - name: Reimbursements description: View reimbursement requests by employee. - name: Routing Numbers description: Validate routing numbers and retrieve bank information. - name: Security Policies - name: Simulations description: >- Trigger simulated events (inbound transfers, card authorizations, application approval) to test integrations end-to-end without real money movement. **Not available in production**: these endpoints exist only in sandbox and development environments and return `404 Not Found` in production. - name: Tax Forms description: Retrieve IRS tax forms (1099 family) issued for accounts. - name: Transactions description: Retrieve account transaction history and details. - name: Transfers description: >- Initiate ACH, wire, book, and crypto transfers, and retrieve transfer details. - name: Users description: View active users for your entity. - name: Webhooks description: Manage webhook subscriptions and inspect delivery history. - name: Wire Drawdowns description: >- Review vendor requests to draw funds by wire, and pre-authorize trusted vendors. paths: /wire-drawdowns: get: tags: - Wire Drawdowns summary: List Wire Drawdown Requests description: >- Returns every wire drawdown request made against your accounts, pending ones first. A drawdown is a vendor asking you to wire them funds; nothing moves until you approve it. operationId: list_wire_drawdown_requests_wire_drawdowns_get parameters: - $ref: '#/components/parameters/EntityIdHeader' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/WireDrawdownRequests' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/RateLimited' security: - apiKeyAuth: - accounts:transactions components: parameters: EntityIdHeader: name: x-entity-id in: header required: false schema: type: string format: uuid description: Optional `entity_id` to scope requests to a specific entity. schemas: WireDrawdownRequests: properties: wire_drawdown_requests: items: $ref: '#/components/schemas/WireDrawdownRequest' type: array title: Wire Drawdown Requests description: Every drawdown request across your accounts, pending ones first. type: object required: - wire_drawdown_requests title: WireDrawdownRequests WireDrawdownRequest: properties: id: type: string title: Id description: Pass this to Approve or Reject Wire Drawdown Request. account_id: type: string title: Account Id description: The account the requester wants to draw from. amount: type: string pattern: ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$ title: Amount description: Amount requested, in USD. status: $ref: '#/components/schemas/PublicWireDrawdownRequestStatus' description: >- `pending` until you approve or reject it. Approving sends a wire for the amount; rejecting closes the request without payment. originator_name: anyOf: - type: string - type: 'null' title: Originator Name description: Who is asking to draw the funds. beneficiary_name: anyOf: - type: string - type: 'null' title: Beneficiary Name description: Who receives the wire when you approve. sender_routing_number: anyOf: - type: string - type: 'null' title: Sender Routing Number description: Routing number of the requester's bank. wire_beneficiary_account_number: anyOf: - type: string - type: 'null' title: Wire Beneficiary Account Number description: Account number the wire pays into when you approve. originator_to_beneficiary: anyOf: - type: string - type: 'null' title: Originator To Beneficiary description: Free-text reference the requester sent with the request. approved_by: anyOf: - $ref: '#/components/schemas/Initiator' - type: 'null' description: >- Who approved the request, once approved. Null while pending, and on requests that an authorization approved automatically. approved_at: anyOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' description: When it was approved. rejected_by: anyOf: - $ref: '#/components/schemas/Initiator' - type: 'null' description: Who rejected the request, once rejected. rejected_at: anyOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' description: When it was rejected. failed_at: anyOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' description: When the resulting wire failed, if it did. failure_reason: anyOf: - type: string - type: 'null' title: Failure Reason description: Why the resulting wire failed, when it did. created_at: $ref: '#/components/schemas/Timestamp' description: When the request arrived. updated_at: anyOf: - $ref: '#/components/schemas/Timestamp' - type: 'null' description: When it last changed. type: object required: - id - account_id - amount - status - created_at title: WireDrawdownRequest CustomerApiError: oneOf: - $ref: '#/components/schemas/CustomerApiServiceError' - $ref: '#/components/schemas/CustomerApiGatewayError' CustomerApiGatewayError: type: object required: - error_code - message properties: error_code: type: string message: type: string PublicWireDrawdownRequestStatus: type: string enum: - pending - approved - rejected - failed title: PublicWireDrawdownRequestStatus x-enum-varnames: - pending - approved - rejected - failed Initiator: properties: email: anyOf: - type: string - type: 'null' title: Email description: >- Email address of the person who acted. `null` when the actor is an API key with no user behind it. name: anyOf: - type: string - type: 'null' title: Name description: >- Full name of the person who acted, as it stood when they acted. `null` when the actor is an API key with no user behind it. public_id: anyOf: - type: string format: uuid - type: 'null' title: Public Id description: >- Identifier of the user who acted. `null` when the actor is an API key with no user behind it. api_key_id: anyOf: - type: string - type: 'null' title: Api Key Id description: >- Identifier of the API key used. `null` when the action came from the Meow dashboard. api_key_nickname: anyOf: - type: string - type: 'null' title: Api Key Nickname description: >- Nickname of the API key used. `null` when no key was used, or the key has no nickname. identity_type: $ref: '#/components/schemas/InitiatorIdentityType' description: Credential the action came in on. default: web_user user_id: anyOf: - type: integer - type: 'null' title: User Id description: >- Meow-internal numeric id of the user who acted. Prefer `public_id`, which is the identifier the API accepts elsewhere. display: $ref: '#/components/schemas/DisplayInitiator' description: >- Pre-rendered presentation of this initiator, so every surface names them the same way. readOnly: true type: object required: - display title: Initiator Timestamp: type: string format: date-time title: Timestamp description: >- ISO 8601 date-time in the format `YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]` (per [IETF RFC 3339](https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14)). CustomerApiServiceError: type: object required: - code - message - debug_message properties: code: type: integer message: type: string debug_message: type: string InitiatorIdentityType: type: string enum: - web_user - user_api_key - entity_api_key - mcp_oauth - cli_key - partner_api_key title: InitiatorIdentityType x-enum-varnames: - web_user - user_api_key - entity_api_key - mcp_oauth - cli_key - partner_api_key DisplayInitiator: properties: primary: type: string title: Primary description: >- Ready-to-render name for whoever acted, with the mechanism folded in — "Jane Doe", "Jane Doe's API key", or 'Service API key "Production Cards"'. Drop it straight into a sentence rather than reassembling it from the fields below. type: object required: - primary title: DisplayInitiator responses: BadRequest: description: The request could not be processed. content: application/json: schema: $ref: '#/components/schemas/CustomerApiError' Unauthorized: description: Authentication failed. content: application/json: schema: $ref: '#/components/schemas/CustomerApiGatewayError' Forbidden: description: The API key is not authorized for this operation. content: application/json: schema: $ref: '#/components/schemas/CustomerApiGatewayError' RateLimited: description: Too many requests. headers: Retry-After: schema: type: integer content: application/json: schema: $ref: '#/components/schemas/CustomerApiGatewayError' securitySchemes: apiKeyAuth: type: apiKey in: header name: x-api-key description: Your Meow API key, sent in the `x-api-key` header for authentication. x-scopes: - accounts:read - accounts:write - accounts:payment-networks - accounts:transactions - accounts:balances - accounts:statements - accounts:tax-documents - entity:create - transfers:crypto:write - transfers:usdc:write - transfers:ach:write - transfers:wire:write - transfers:book:write - transfers:international:write - contacts:read - contacts:write - billing:products:read - billing:products:write - billing:customers:read - billing:customers:write - billing:invoices:read - billing:invoices:write - billing:accounts:read - billpay:read - billpay:write - onboarding:read - onboarding:write - cards:read - cards:write - reimbursements:read - users:read - webhooks:read - webhooks:write - partner:onboarding:read - partner:onboarding:write - partner:webhooks:read - partner:webhooks:write - simulations:write - banking:limits:read - banking:limits:write - feature-access:read - feature-access:write ````