EDINET API via AIsa

Other

AIsa gateway endpoints for EDINET document list and document download.

About EDINET API via AIsa

Review the Service identity, supported languages, protocol versions, and source metadata discovered by the directory.

Service details

Service Id

a0a969e9-126d-4de8-9e4a-c9b46f657020

Service origin

https://api.aisa.one

ListedSeptember 24, 2026, 6:38 PM

Last checkedSeptember 24, 2026, 7:57 PM

Protocol details

SourceOpenAPI

Endpoints

Endpoint details are saved from the OpenAPI document. Authentication requirements and prices are advertised information, not a verified payment or access guarantee. The document may contain additional endpoints.Open OpenAPI document

GET/edinet/documents.json

List EDINET documents

Lists every disclosure filed with Japan's EDINET on one date. date is required (YYYY-MM-DD). type=2 returns the filings under results — docID, filerName, secCode, JCN, docTypeCode, docDescription, submitDateTime, periodStart and periodEnd per filing — while type=1 returns metadata only, with the day's count under metadata.resultset.count and no results array. Measured at 612 KB for a typical business day (648 filings), and there are no filter parameters, so type=2 always returns the whole day; check the count with type=1 first when in doubt. About two thirds of filings carry a secCode (listed companies), the rest are funds and unlisted filers. A filing's docID feeds get_edinet_document_download.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.

GET/edinet/documents/{docID}

Download an EDINET document

Downloads one filing by docID, taken from get_edinet_documents. The success response is a binary file, not JSON: type=1 returns the filing body and audit report as a ZIP archive (measured 11.9 KB, content-type application/octet-stream), type=2 the PDF (measured 15.0 KB, application/pdf). Errors still come back as JSON, so check the response content type before parsing. Because a tool result cannot usefully carry a binary payload, this endpoint stays REST-only: over MCP, stop at the docID from get_edinet_documents and fetch the file over REST.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.