Skip to main content
Skip table of contents

End-of-Day API

The EOD Desktop API provides you with End-of-Day or Historical data and can be accessed directly from a 3rd party console.

The Infront End-of-Day service can be used by 3rd party server systems to request end-of-day prices from Infront for a specific set of instruments.

The server system first posts a request for data and then polls the Infront service for the response until it is ready.

To access the EOD Desktop API, you need access to the Infront Professional Terminal, the EOD module and the market data for the API request. The data returns formatted as JSON or XML. The Infront End-of-Day Web API documentation can be found here:

https://eod.infrontservices.com/#documentation

Instruments are identified by using "Operating MIC", "ISIN" and (optional) "currency". Alternatively, instruments can be identified by using the Infront "feed number" and "ticker code". Be aware that instruments that are not found by Infront or that have multiple possible matches (ambiguous) will be marked in the result with an error code. The API is also case sensitive. For example, spelling "operating_mic" as "Operating_MIC" will not work.

The End-of-Day service is HTTP/REST based and uses JSON as data protocol.

The server accepts four types of requests:

Request type

Description

End-of-Day

Service used to make a request for one or multiple instruments.

Historical

Service used to make a request for one or multiple instruments.

Instrument Search

Service used to get information about an instrument.

Accessible Markets

Service used to get information about accessible markets for a given user.

The following data can be retrieved with EOD API:

Data type

Description

EOD

Name, Previous close date, Previous close, Volume, Turnover, Bid, Ask, Currency.

Historical

Last, Volume, Turnover, Bid, Ask, Open, High, Low.

Instrument Search

Operating mic, ISIN, Feed, Instrument type, Feed name, Ticker, Name, Currency.

Accessible Markets

Operating mic, Feed, Feed code, Feed description.

The EOD Desktop API provides you with End-of-Day or Historical data and can be accessed directly from a 3rd party console.

The Infront End-of-Day service can be used by 3rd party server systems to request end-of-day prices from Infront for a specific set of instruments.

The server system first posts a request for data and then polls the Infront service for the response until it is ready.

To access the EOD Desktop API, you need access to the Infront Professional Terminal, the EOD module and the market data for the API request. The data returns formatted as JSON or XML. The Infront End-of-Day Web API documentation can be found here:

eod.infrontservices.com/#documentation+

Instruments are identified by using "Operating MIC", "ISIN" and (optional) "currency". Alternatively, instruments can be identified by using the Infront "feed number" and "ticker code". Be aware that instruments that are not found by Infront or that have multiple possible matches (ambiguous) will be marked in the result with an error code. The API is also case sensitive. For example, spelling "operating_mic" as "Operating_MIC" will not work.

The End-of-Day service is HTTP/REST based and uses JSON as data protocol.

The server accepts four types of requests:

Request type

Description

End-of-Day

Service used to make a request for one or multiple instruments.

Historical

Service used to make a request for one or multiple instruments.

Instrument Search

Service used to get information about an instrument.

Accessible Markets

Service used to get information about accessible markets for a given user.

The following data can be retrieved with EOD API:

Data type

Description

EOD

Name, Previous close date, Previous close, Volume, Turnover, Bid, Ask, Currency.

Historical

Last, Volume, Turnover, Bid, Ask, Open, High, Low.

Instrument Search

Operating mic, ISIN, Feed, Instrument type, Feed name, Ticker, Name, Currency.

Accessible Markets

Operating mic, Feed, Feed code, Feed description.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.