Payload transformation
Preview a declarative reshape before forwarding.
These pages describe ShellOrbit as it runs today. Breaking changes to the HTTP API are announced before they ship, and existing request and response shapes stay supported.
What changes?
Transformations run on the outbound copy. Stored original bytes and inbound signature checks remain unchanged. The same saved specification applies to replay, so disable it to deliver the original payload.
The workbench supports rename, pick, drop, wrap, and add. It does not execute JavaScript or JSONPath expressions.
{
"rename": {"customer_email": "email"},
"drop": ["internal_note"],
"add": {"source": "stripe"},
"wrap": "event"
}Rename sources support dotted paths; pick and drop use top-level field names. Use pick to retain an explicit set of fields. Added constants are strings. Preview with a reviewed JSON sample in endpoint settings; preview does not send requests or change the endpoint.
Verification and failure behavior
The ShellOrbit signature covers the exact outgoing body, including a transformation. A provider signature generally will not verify against that changed body. Verify the provider at ingest and ShellOrbit at your handler.
If applying a saved transformation fails, delivery uses the original body and logs the transformation error. This fallback can include fields you intended to remove. Use privacy controls for inspection masking; they are separate from outbound transformations and do not delete stored original data.