WeTransform Redirect

Redirect to WeTransform

Send your users to a branded WeTransform page to upload and transform their data, then hand them back to your site with the signed result — secured end-to-end with HMAC signatures.

Want the experience embedded directly inside your web app, with no redirect? Use Embed to open WeTransform as a modal or inline widget without leaving your page. Read the Embed documentation →
Why use the redirect flow?

Redirecting to WeTransform lets you offer a professional data transformation experience while maintaining your brand identity. It's perfect for onboarding suppliers, importing product catalogs, or processing client files.

Use Cases
  • Product catalog uploads
  • Supplier data onboarding
  • Custom file layouts conversion
Features
  • White-label branding
  • Secure HMAC redirection
  • Automatic customer creation

Redirect to your branded page

The redirect flow sends users to a dedicated, customizable WeTransform page (e.g., your-company.send-a-file.io) branded with your logo and colors. Once their file is transformed, they are redirected back to your site with a signed download link.

Branded Page Integration

Looking for an inline, in-page experience instead of a redirect? That is now handled by Embed.

The Workflow

The typical user flow involves a secure redirection from your site to WeTransform, followed by a signed return to your application.

sequenceDiagram participant U as User participant YS as Your Website participant WT as WeTransform U->>YS: Clicks "Upload & Transform" YS->>WT: Redirects with HMAC Signature WT->>U: Displays Upload Interface U->>WT: Uploads & Configures File WT->>WT: Processes Transformation WT->>YS: Redirects to Return URL with signed File URL YS->>YS: Downloads & Integrates Data

Configuration

  1. Define Embed URL: Go to Integrations → Embed and set your unique URL (e.g., your-name.send-a-file.io).
  2. Set Return URL: This is where users are sent back after the file is processed.
  3. Generate Signature Secret: This key is used to sign all communications and must be kept secret.

Implementation Steps

1. Create the link

Direct users to https://your-name.send-a-file.io. You can target a specific template or specify a customer_id in the query string.

2. Add HMAC Signature

Every request must include a signature parameter as proof of authentication (see Security section below).

3. Process the results

In your Return URL, verify the incoming signature and download the transformed file from the provided URL.

Security

All interactions are secured using HMAC SHA256 signatures to guarantee authenticity and integrity. The signed message is the used parameters joined with : — only the parameters you actually send are included.

Using demo values

Everything below is computed live in your browser: change any value and the signatures and URLs update everywhere. Authenticate to replace the demo values with your organisation's real embed URL, signature secret and target formats.

Your website WeTransformWeTransform
Then, signature =

The URL at which you should redirect your customer should be:

WeTransformWeTransform Your website
Then, signature =

The callback URL at which we will redirect your customer will be:

Before downloading the file, you must check that the signature is valid to ensure the request comes from us.

Webhooks

If you prefer an asynchronous approach, you can receive notifications when files are ready for download.

Event: file:ready-for-download
{
  "event": "file:ready-for-download",
  "download_url": "https://wetransform.com/download/qxyQYK...",
  "customer_id": "65bd6fc913...",
  "template": "products"
}
Verification: Webhooks include an X-Signature header. Always verify it before processing.

Ready to go?

Configure your branding and start redirecting users to WeTransform today.

Configuration dashboard
© 2026