How it works

From messy spreadsheet to API-ready payload.

PayloadForge combines field mapping, data transformation, dataset-wide validation and request generation in one workflow.

01

Describe the target API

Paste an existing cURL request or provide an example JSON payload. PayloadForge uses that information to understand the request method, endpoint, headers, target fields and expected data types.

↓

02

Import spreadsheet data

Import CSV data or enter rows manually. Each spreadsheet column becomes a source field that can be connected to the target API.

↓

03

Map source columns

Map spreadsheet columns to API fields. PayloadForge can automatically match straightforward field names while leaving uncertain mappings for review.

↓

04

Transform incompatible values

Create ordered transformation rules such as trimming whitespace, removing formatting, replacing values, changing case or providing defaults.

↓

05

Analyze dataset impact

Every transformation can be evaluated across the entire column. PayloadForge shows how many rows are valid, which rows still fail and the transformed value for each sampled record.

↓

06

Review smart suggestions

For common formatting problems, PayloadForge can propose cleanup rules and simulate the expected improvement before anything is applied.

↓

07

Validate the request

Mappings, transformed values and target data types are checked before the request is considered ready to generate.

↓

08

Generate JSON or cURL

Once the dataset is valid, copy typed JSON or a generated cURL request for use in your API workflow.

Example: cleaning a revenue column

Suppose an API expects a number, but the spreadsheet contains:

₹3,83,000
85000
52000

Two rows already satisfy the numeric type. The first does not. PayloadForge can detect the formatting, propose removing the currency symbol and thousands separators, and simulate the result:

Raw
Result
Status
₹3,83,000
383000
✓ Valid
85000
85000
✓ Valid
52000
52000
✓ Valid

Suggestions are simulated before application

PayloadForge does not need to blindly apply a detected cleanup. A suggestion can be evaluated against the current dataset first. If a proposed transformation does not improve validation, it should not be presented as a useful fix.

Example

Current

2 / 3

valid rows

After

3 / 3

valid rows

Try it with your own data

The current builder supports API configuration, CSV data, field mapping, transformations, validation and JSON/cURL generation.