Multiple find and replace

What multiple find and replace means and when to use it

An empty find string in any pair raises invalid_input, which protects bulk jobs from the classic empty-string replace-everywhere footgun.

Input contract, ordered pairs, and reading the response

Missing replace defaults to the empty string, which deletes every match for that pair. Inside each pair, find also accepts search, needle, from, or old; replace accepts replacement, with, to, or new. At most one hundred pairs are accepted in a single request. Send a JSON body with the required string field text set to the source you want edited and the required array field replacements set to at least one object with a non-empty find string and an optional replace string. Optional case_insensitive defaults to false for exact case; set it true when mixed-case drafts should still match on every pair. Aliases are accepted for older clients: text also as input, value, s, content, or source; replacements as pairs, rules, or substitutions; case_insensitive as ignore_case, ci, or insensitive. Missing text, missing replacements, a non-array list, an empty list, a non-object pair, a non-string find, or an empty find string all raise invalid_input with a message that names the problem, and those failures are not charged on the prepaid API. Use result alone when you only need the cleaned string; use per-pair count when a pipeline logs which glossary entry fired; use total_count when a dashboard tracks edit volume. Keep payloads to ordinary phrase, paragraph, and short document sizes suitable for a Worker isolate rather than multi-megabyte dumps.

API usage, pricing, workflows, and practical limits

Call the free in-browser multiple find and replace tool for paste cleanup, glossary trials, classroom demos, content QA, and multi-token renames without installing a desktop utility or writing nested split-join snippets in every language. Another workflow fills template tokens such as company, product, and plan code by listing each find/replace pair in one request, or deletes a set of deprecated markers by sending empty replace values. Do not expect HTML-aware rewriting that skips tags, structured document merge fields, parallel longest-match resolution, or locale-specific collation beyond standard ignore-case matching—those are separate problems. Authors shipping SDKs can document text and replacements as required fields and show a multi-pair success example plus an empty-find error example so integrators see both sides of the contract. Use the prepaid KIT API when a CMS, ETL job, form backend, support desk, or mobile client needs the same multi-pair transform under balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. A typical workflow ships a brand rename pack that first rewrites the full legal name, then short forms, then contact addresses, and checks total_count to confirm every expected hit was updated. Pair this endpoint with space tidy or case converters when the next step is style cleanup, but keep multiple find and replace as its own landing so the SEO intent is not mixed with single-pair tools or regex playgrounds.