Core concepts

/process

Chain operations over one record set.

POST /api/v1/process chains record-stream operations over a single working set in one synchronous request. All steps are validated before any runs.

Record-transforming steps (e.g. impute, rank, normalize-address) rewrite the working set.
Analysis steps attach results under artifacts keyed by operation id and pass records through unchanged.
Two-dataset ops (schema-diff, link) use the working set as source A and the step's against array as source B.
Cost: sum of each step's records_in × the operation's per-record weight.

Chainable operations (38)

anonymizechange-pointsclusterconvertcorrelationsdistributionsflattenhashimputelinkmissingnormalize-addressnormalize-phonenormalize-urlpatternspii-detectpii-scanpivotpolicy-checkprofilepseudonymizequality-scorerankrisk-scoresafe-outputschema-diffschema-validatesecret-detectsegmentsimilaritysplit-namestatisticstokenizetrendsunflattenunpivotvalidate-emailvalidate-format

Text, document, series and single-string operations are not chainable — call their own endpoints. Build chains visually in the Workflow builder.

curl -X POST https://messyapi.com/api/v1/process \
  -H "Authorization: Bearer $MESSYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "data": [
    {
      "phone": "(555) 123-4567",
      "email": "Ana@Example.com"
    }
  ],
  "steps": [
    {
      "operation": "normalize-phone",
      "options": {
        "field": "phone"
      }
    },
    {
      "operation": "validate-email",
      "options": {
        "field": "email"
      }
    }
  ]
}'

Each step's options use the same names as that operation's own endpoint — see the API reference.

Other orchestration endpoints

/analyze, /pipeline, /pipelines/{id}/run, /workflows/run and /execute remain available and unchanged. /workflows/run and /execute are limited preview, gated per account.