If you plan on supplying us with constituent data you hold on site, for example custom baskets or Index data used elsewhere within the business you should supply this using the endpoint:
https://NAME-svc.fundapps.co/api/adapptr/v2/composites
Where NAME is replaced with your FundApps tenant name
- Use a POST request
- Authenticate using the same Rapptr API credentials used for file upload currently, in Basic Authentication format
- Upload a CSV (format below) in the body using a
composites
key and a Content-Type of multipart/form-data
- CSV format
CompositeId |
CompositeIdType |
ComponentId |
ComponentIdType |
Weighting |
.KS100EWI |
DataProviderId |
005930.KS |
DataProviderId |
0.2 |
.KS100EWI |
DataProviderId |
KR7005930003 |
Isin |
0.3 |
KOSPI100 Index |
DataProviderId |
005930 KS Equity |
DataProviderId |
0.2 |
- CompositeIdType / ComponentIdType fields are used to describe the code you wish to match the parent/constituent on, the supported values are:
- InstrumentId (XML / ExPost only)
- DataProviderId (Adapptr only)
- Isin
- Sedol
- Cusip
BYOD File Validation
- You can specify additional fields within this CSV, they will be ignored for processing
- Weighting should be provided as a value between 0-1
- Underweight Composites are OK, validation will check if a composite is overweight (sum of all components is >1.0)
- BYOD data is persisted until the next BYOD upload occurs, you do not need to upload it each day or run of the service
- If the file passes validation you should see a return status of 201 with a message:
{
"message": "Upload Successful"
}