> ## 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. # Resolve an information request > Answer an information request's follow-up questions. Answers are validated against the request's form schema and submitted in one call. There is no draft state on this API. Documents are uploaded separately; `outstanding` reports whatever the request still owes. ## OpenAPI ````yaml POST /entities/{entity_id}/info-requests/{request_id} 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: /entities/{entity_id}/info-requests/{request_id}: post: tags: - Entities summary: Submit Info Request Answers description: >- Answer an information request's follow-up questions. Answers are validated against the request's form schema and submitted in one call. There is no draft state on this API. Documents are uploaded separately; `outstanding` reports whatever the request still owes. operationId: >- submit_info_request_answers_entities__entity_id__info_requests__request_id__post parameters: - name: request_id in: path required: true schema: type: string format: uuid description: >- The information request, as returned in `next_step.info_requests[].request_id`. title: Request Id description: >- The information request, as returned in `next_step.info_requests[].request_id`. - name: entity_id in: path required: true schema: type: string description: The entity being onboarded. title: Entity Id description: The entity being onboarded. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/EntityInfoRequestAnswersRequest' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/EntityInfoRequestAnswersResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/RateLimited' security: - apiKeyAuth: - entity:create components: schemas: EntityInfoRequestAnswersRequest: properties: answers: anyOf: - additionalProperties: anyOf: - type: string - type: boolean - type: integer - type: number - items: {} type: array - additionalProperties: true type: object - type: 'null' type: object - type: 'null' title: Answers description: >- Answers keyed by the element `name` in the request's form schema. Validated against that schema, so send them complete. This submits, it does not save a draft. Omit it when the request asks no questions and you are only explaining an unavailable document. unavailable_proof_explanations: anyOf: - additionalProperties: type: string maxLength: 1000 minLength: 1 propertyNames: $ref: '#/components/schemas/PublicKybProofType' type: object - type: 'null' title: Unavailable Proof Explanations description: >- Why the business cannot provide a requested document, keyed by its `proof_type`. An accepted explanation settles that document the same way an upload does, so use it when no upload will ever satisfy the request. Send every explanation the request should keep: this replaces the set on file rather than adding to it, and an explanation for a document you have since uploaded is dropped. type: object title: EntityInfoRequestAnswersRequest EntityInfoRequestAnswersResponse: properties: request_completed: type: boolean title: Request Completed description: >- Whether the information request is now satisfied in full. False while it still owes documents. outstanding: items: $ref: '#/components/schemas/PublicOutstandingItem' type: array title: Outstanding description: What the request is still waiting on after this submission. type: object required: - request_completed - outstanding title: EntityInfoRequestAnswersResponse PublicOutstandingItem: properties: kind: $ref: '#/components/schemas/PublicOutstandingItemKind' description: >- `document` for a file the request is still missing, `answers` for its follow-up questions. proof_type: anyOf: - $ref: '#/components/schemas/PublicKybProofType' - type: 'null' description: >- The document still owed, as a `proof_type` value to pass to the document upload endpoints. Null on an `answers` item. detail: type: string title: Detail description: >- The item written out for a person to read. Prose, so match on `kind` and `proof_type` rather than on this. type: object required: - kind - detail title: PublicOutstandingItem 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 PublicOutstandingItemKind: type: string enum: - document - answers title: PublicOutstandingItemKind x-enum-varnames: - document - answers PublicKybProofType: type: string enum: - accredited - address - articles_of_organization - bank_statement - client_contract - client_invoice - beneficial_owner_address - beneficial_owner_id - beneficial_owner_id_back - beneficial_ownership_register - bylaws - certificate_of_good_standing - corporate_resolution - drivers_license - due_diligence - ein - final_edd_report - government_issued_business_license - hemp_cultivator_state_license - incorporation - industry_related_license - lease_agreement - llc_resolution - money_service_business_license - money_transmitter_registration - mortgage_statement - national_id - org_chart - partnership_agreement - partnership_agreement_due_diligence - partnership_resolution - personal_address - remote_employees_due_diligence - signed_ss4 - tax_exemption_certificate - uk_officer_passport - officer_registry - uk_registry - shareholder_registry - uk_w8_en - utility_bill - us_based_office_proof_of_address_due_diligence - pitch_deck - active_business_registration - proof_of_ownership_or_banking_authorization - non_profit_bylaws - operating_agreement - flow_of_funds - aml_sanction - registration_or_license - sec_filing - legal_opinion - certificate_of_formation_master_llc - series_operating_agreement - share_subscription_agreement - fund_subscription_agreement - safe_agreement - convertible_note_agreement - loan_promissory_note - token_purchase_agreement - saft_agreement - deal_memo_hybrid_agreement - issuer_due_diligence_report - protocol_ecosystem_questionnaire - investment_company_due_diligence_form - us_based_operations_due_diligence_form - register_of_directors - articles_of_association - memorandum_of_association - non_profit_status - ofac_sanctions_screening_policy - aml_kyc_policy - w8_bene - corporate_structure_chart - custody_safeguarding_agreement - reserve_attestation - sanctions_vendor_service_agreement - contractual_fund_flow_agreements title: PublicKybProofType x-enum-varnames: - accredited - address - articles_of_organization - bank_statement - client_contract - client_invoice - beneficial_owner_address - beneficial_owner_id - beneficial_owner_id_back - beneficial_ownership_register - bylaws - certificate_of_good_standing - corporate_resolution - drivers_license - due_diligence - ein - final_edd_report - government_issued_business_license - hemp_cultivator_state_license - incorporation - industry_related_license - lease_agreement - llc_resolution - money_service_business_license - money_transmitter_registration - mortgage_statement - national_id - org_chart - partnership_agreement - partnership_agreement_due_diligence - partnership_resolution - personal_address - remote_employees_due_diligence - signed_ss4 - tax_exemption_certificate - uk_officer_passport - officer_registry - uk_registry - shareholder_registry - uk_w8_en - utility_bill - us_based_office_proof_of_address_due_diligence - pitch_deck - active_business_registration - proof_of_ownership_or_banking_authorization - non_profit_bylaws - operating_agreement - flow_of_funds - aml_sanction - registration_or_license - sec_filing - legal_opinion - certificate_of_formation_master_llc - series_operating_agreement - share_subscription_agreement - fund_subscription_agreement - safe_agreement - convertible_note_agreement - loan_promissory_note - token_purchase_agreement - saft_agreement - deal_memo_hybrid_agreement - issuer_due_diligence_report - protocol_ecosystem_questionnaire - investment_company_due_diligence_form - us_based_operations_due_diligence_form - register_of_directors - articles_of_association - memorandum_of_association - non_profit_status - ofac_sanctions_screening_policy - aml_kyc_policy - w8_bene - corporate_structure_chart - custody_safeguarding_agreement - reserve_attestation - sanctions_vendor_service_agreement - contractual_fund_flow_agreements CustomerApiServiceError: type: object required: - code - message - debug_message properties: code: type: integer message: type: string debug_message: type: string 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 - users:write - 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 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.