POST
/
mappings
/
{id}
/
map
  curl --request POST \
    --url  https://mappings.us.stedi.com/2021-06-01/mappings/{mappingId}/map \
    --header "Authorization: ${STEDI_API_KEY}" \
    --data '{ "myData": 1 }'

{ "mappedData": 2 }

This functionality is available in a Stedi module. Contact us for details.

  curl --request POST \
    --url  https://mappings.us.stedi.com/2021-06-01/mappings/{mappingId}/map \
    --header "Authorization: ${STEDI_API_KEY}" \
    --data '{ "myData": 1 }'

{ "mappedData": 2 }

Authorizations

​
Authorization
string
header
required

API key authentication via the 'Authorization' header

Path Parameters

​
id
string
required
Required string length: 26

Query Parameters

​
validation_mode
enum<string>

Validation mode, when not provided - no validation of input and output is applied, for the 'strict' option JSON Schema validation is applied to the input JSON and the output JSON using source and target JSON Schema.

Available options:
strict

Body

application/json · any

The body of the request should be the JSON you want to map. It can take any shape as long as it is valid JSON.

Response

200
application/json
MapDocument 200 response

example {"key": "value"}

Was this page helpful?

OutputMap Transaction Output