ETF Library Subscribe (V3)

The ETF Subscribe API allows you to add ETFs to your ETF Library allowance in the Composites service. It is an optional extra on the baseline Composites subscription. The Subscribe API is write-only: each call adds a single ETF to your usage pool, which you can then query via the details endpoint.

You can access it using the standard API username and password you should have set up already, substituting your tenant name into the below URL and sending the ETF's ISIN or FIGI in the request body.

POST https://{environment_name}-api.fundapps.co/v3/data/composites/subscribe

Where {environment_name} is replaced with your FundApps tenant name.

Authorisation

This endpoint uses Basic authentication, for more information please see Authentication for more details.

You will need an API user in order to use this endpoint, you can create this in the main FundApps platform.

Request

Send exactly one of isin or figi in the JSON body. The identifier can be the ETF itself, the benchmark it tracks, or a variant proxy.

{
    "isin": "DE000A0Q4R36"
}

Response

Our API responds with the ETF that was added and your remaining allowance, a sample is below

{
    "requestedIdentifier": "DE000A0Q4R36",
    "etfIsin": "DE000A0Q4R36",
    "remaining": 7,
    "contracted": 10,
    "message": "DE000A0Q4R36 was added to your ETF library allowance. You have 7 of your 10 ETFs left."
}

If the ETF was already in your allowance, nothing is added and no allowance is used — the response is the same shape, with a message telling you it was already present.

Errors

• 400 — you did not supply exactly one identifier, or the ISIN/FIGI is invalid (error: invalid_identifier).
• 403 — your ETF Library allowance has been used up, so nothing was added (error: allowance_exhausted).
• 404 — we could not find an ETF for the identifier, so nothing was added (error: etf_not_covered). You can check our coverage using the search endpoint.