---
title: "Requests a new notification message related to account information"
method: POST
path: "/account-info/requests"
tags: ["Notifications"]
---

# Requests a new notification message related to account information

`POST /account-info/requests`

Requests either an account_statement or account_report notification with account information

## Request body

- union
  - AccountInfoNotificationRequestAccountReport — Requests for a new notification to be generated with a new account report
    - `request_id` string, required — UUID Unique identifier for the request.
    - `requested_notification_type` string, required — Always `account_report` for requesting account reports.
    - `account` string, required — The account number
    - `financial_institution` object, required — The financial institution
      - `fin_id_schema` string, required — The schema of the financial institution ID. Can be one of: - `SHINKANSEN`: The ID is a Shinkansen ID.
      - `fin_id` string, required — The financial institution ID
  - AccountInfoNotificationRequestAccountStatement — Requests for a new notification to be generated with a previous, existing account statement
    - `request_id` string, required — UUID Unique identifier for the request.
    - `requested_notification_type` string, required — Always `account_statement` for requesting account statements.
    - `account` string, required — The account number
    - `financial_institution` object, required — The financial institution
      - `fin_id_schema` string, required — The schema of the financial institution ID. Can be one of: - `SHINKANSEN`: The ID is a Shinkansen ID.
      - `fin_id` string, required — The financial institution ID
    - `account_statement_date` string, date, required — The date of the requested account statement. If it doesn't match the date when an account statement was officially issued, the financial institution will still generate a notification with the statement containing the requested date.

## Response `200`

Message correctly received. Does NOT mean the transaction was succesful. Further responses might be sent back on another message.

## Other responses

- `400` — Invalid message (e.g: invalid signature)
- `409` — Message ignored, because it was already seen and processed before by the receiver. Typically happens when a message is re-sent because the sender isn't sure if it was correctly received (e.g: network failure when the 2xx response was in flight)'

---

[API](https://skmtc.net/shinkansen/apis/payouts-shinkansen-endpoints.md) · [All operations](https://skmtc.net/shinkansen/apis/payouts-shinkansen-endpoints/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/shinkansen/payouts-shinkansen-endpoints/revisions/1e4a6760b7e8/schema)