*post

*post sends selected host data or staged data as a Sercrod JSON request envelope with HTTP POST.

• *keys selects outgoing top-level data.
• *params adds request metadata.
• *dry-run marks the request as dry-run. The receiving API must honor that marker.
• *response maps the parsed response into host data.
• *into remains a compatibility alias for whole-response placement.

<serc-rod data='{"form":{"name":"","message":""},"result":null}'>
  <input *input="form.name">
  <textarea *input="form.message"></textarea>

  <button
    type="button"
    *post="'/api/contact.php'"
    *keys="form"
    *params="{ source: 'contact-form' }"
    *response="'result'">
    Send
  </button>
</serc-rod>

*post does not use the old URL suffix response placement form. Use *response for placement.

Request envelope

{
  "sercrod": {
    "origin": "sercrod",
    "request_type": "post",
    "dry_run": false,
    "target": "/api/contact.php",
    "directive": "*post"
  },
  "data": {},
  "params": {}
}

When *dry-run is present, sercrod.dry_run becomes true and sercrod.request_type becomes "dry-run".

Response placement

Every successful response is mirrored to $response. Without *response, normal host data is not changed.

• *response="'result'" stores the whole response in data.result.
• *response="target" evaluates target and uses the result as the destination key.
• *response="{ user.name: response.profile.name }" maps response fields into data paths.