Skip to main content

File downloads

Some files are exposed outside the GraphQL API because their format (XML, ZIP) makes a binary HTTP response a better fit. These REST endpoints live on the same host as /graphql/ and use the same JWT.

Prerequisites

A successful request returns the file directly (application/xml for SEPA files, application/zip for archives). Errors are returned as a JSON body.

Example: download a SEPA file​

curl -X GET "https://api.<client>.vasco.fund/security_operations/123/download-sepa/credit_transfer?moneyMovementIds[]=10" \
  -H "Authorization: Bearer $TOKEN" \
  -o sepa.xml

SEPA files​

Credit transfer (Distribution, Transfer)​

GET /security_operations/{securityOperationId}/download-sepa/credit_transfer — admin only.

  • all=true triggers async generation for all movements (can be combined with search and filter[bankAccountStatus]).
  • Otherwise, pass targeted IDs via moneyMovementIds[]=....
  • Examples:
    • GET /security_operations/123/download-sepa/credit_transfer?all=true&filter[bankAccountStatus]=verified
    • GET /security_operations/123/download-sepa/credit_transfer?moneyMovementIds[]=10&moneyMovementIds[]=11
  • Returns a sepa.xml file, or a 202 Accepted JSON status payload when async generation is triggered.

→ Related concept: Transaction

Direct debit​

GET /security_operations/download-sepa/direct_debit — admin only.

  • Requires the array transactions[transactionId]=securityOperationId listing the transactions to include.
  • Example: GET /security_operations/download-sepa/direct_debit?transactions[42]=1337&transactions[43]=1337
  • Returns a sepa.xml file.

Retrocession invoices​

GET /retrocessions-invoices/download-sepa — admin only.

  • Parameter invoices[]=<invoiceId> for each invoice to include.
  • Example: GET /retrocessions-invoices/download-sepa?invoices[]=9811&invoices[]=9812
  • Returns a sepa.xml file.

→ Related concept: Intermediated placement — distributors and retrocessions.

Subscription packs​

Three routes generate a subscription pack .zip for an investment. The route you call depends on the stage of the subscription flow:

RouteWhen to use it
GET /investments/{investmentId}/download-blank-subscription-pack-for-verification.zipPreview the pack before investment terms are approved. Read-only — does not change the investment state.
GET /investments/{investmentId}/download-blank-subscription-pack.zipAvailable once investment terms are validated. Returns the pack to be signed and marks the investment as manually signed.
GET /investments/{investmentId}/download-blank-subscription-pack-for-electronic-sign.zipSame as above but for electronic signature — does not switch the investment to manual mode.

→ See the Investment Management recipe for where these calls fit into the subscription flow.

Transaction document archives​

Admin and distributor only. Each route returns a .zip archive containing the documents visible for the targeted transaction.

RouteTransaction type
GET /investments/{id}/subscription-pack-documents.zipInvestment
GET /capital-call/{id}/documents.zipCapitalCall
GET /distributions/{id}/documents.zipDistribution
GET /cessions/{id}/documents.zipCession
GET /transfers/{id}/documents.zipTransfer

→ Related concept: Transaction.