Export Email Resend

Introduction

When an export is generated in DJUST PAY (transaction events, supplier payouts, funding transfers, or marketplace payouts), an email with the download link is automatically sent to the requester. If this email is lost, not received, or needs to be forwarded to additional recipients, the export email resend feature allows you to resend it without regenerating the CSV file.

This is a generic endpoint that works for all export types.

Key Concepts

• No file regeneration — the resend only re-sends the notification email. The original CSV file is reused.
• Status requirement — only exports at status READY can have their email resent.
• Recipient — the primary recipient is always the connected user (the user calling the API). This cannot be changed.
• CC recipients — the list of CC recipients can be redefined in the request body. If no body is provided, the original CC list is preserved.

Endpoint

Requires dj-client and dj-api-key headers.

How It Works

flowchart LR
  %% Styles (Readme)
  classDef create   fill:#e8f1ff,stroke:#2f6feb,stroke-width:2px,color:#0b3d91;
  classDef read     fill:#ede9fe,stroke:#7c3aed,stroke-width:2px,color:#1e1b4b;
  classDef update   fill:#e0f7fa,stroke:#06b6d4,stroke-width:2px,color:#0c4a6e;
  classDef add      fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#064e3b;
  classDef remove   fill:#fee2e2,stroke:#ef4444,stroke-width:2px,color:#7f1d1d;
  classDef decision fill:#fff4e5,stroke:#f59e0b,stroke-width:2px,color:#7a3e00;
  classDef place    fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#14532d;
  classDef sys      fill:#f2f4f7,stroke:#475569,stroke-width:2px,color:#111827;
  classDef ok       fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#064e3b;
  classDef stop     fill:#fee2e2,stroke:#ef4444,stroke-width:2px,color:#7f1d1d;

  A["📘 Export is READY"]:::read
  B["🔄 POST resend-email"]:::update
  C{{"✅ Status = READY?"}}:::decision
  D["📩 Email resent<br>to user + CC"]:::place
  E["❌ 409 Conflict<br>Export not READY"]:::stop
  F["❌ 403 Forbidden<br>Not your export"]:::stop

  A --> B --> C
  C -->|Yes| D
  C -->|Not READY| E
  C -->|Wrong owner| F

  style A rx:8,ry:8
  style B rx:8,ry:8
  style D rx:8,ry:8
  style E rx:8,ry:8
  style F rx:8,ry:8

API Usage

Request

POST /v1/exports/{exportId}/resend-email
dj-client: OPERATOR
dj-api-key: {{apiKey}}
Content-Type: application/json

Request Body (optional)

If no body is provided (or the cc field is omitted), the original CC recipients are preserved.

Example — Resend with updated CC list

{
  "cc": ["[email protected]", "[email protected]"]
}

Example — Resend with original CC list

No body required:

POST /v1/exports/{exportId}/resend-email
dj-client: OPERATOR
dj-api-key: {{apiKey}}

Response — 200 OK

The response confirms the recipients:

{
  "to": "[email protected]",
  "cc": ["[email protected]", "[email protected]"]
}

Error Cases

For the complete list of DJUST error and warning codes, refer to the dedicated page: Error / Warning codes

Supported Export Types

This endpoint works for all DJUST PAY export types:

Regardless of the export type, the resend endpoint is the same: POST /v1/exports/{exportId}/resend-email.

Best Practices

1. Use resend instead of re-export — if the email was lost, resend it rather than generating a new export. This is faster and avoids unnecessary load.
2. Update CC recipients as needed — the resend feature lets you add new recipients who were not included in the original export request.
3. Limit CC to 20 addresses — the maximum number of CC recipients per resend is 20.

Common Mistakes

Related Documentation

• Transactions - Export
• Supplier Payouts - Export
• Funding Transfers - Export
• Marketplace Payouts - Export