Skip to content
Plune Plune Docs

Fold several tags into one that stays

POST
/v1/settings/tags/merge
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/settings/tags/merge \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "from": [ "Smoke", "SMOKE" ], "into": "smoke" }'

“Keep this one”: every case carrying any tag in from has those tags replaced by into in its title — one occurrence, however many it carried — through the same per-case write as rename (AC-10, AC-23). into need not exist yet; it is checked against the tag rule (400). from must not contain into (400). One transaction; each case gets its own audit entry; text versions do not move.

Authorizations

Section titled “Authorizations ”

Request Body required

Section titled “Request Body required ”
Media type application/json
object
from
required

The tags that disappear. Must not contain into.

Array<string>
>= 1 items
Example 
[
  "Smoke",
  "SMOKE"
]
into
required

The one that stays — “keep this one” (AC-23).

string
Example 
smoke

Responses

Section titled “ Responses ”

200

Section titled “200 ”

How many cases were rewritten

Media type application/json
object
affected
required

Cases whose title was rewritten.

integer
Example generated
{
  "affected": 1
}

400

Section titled “400 ”

into is not a valid tag, from contains into, or the body is invalid

Media type application/json
object
error
required
string
Example 
{
  "error": "validation failed — from: must not contain the tag kept by 'into'"
}

401

Section titled “401 ”

No / invalid token or session

429

Section titled “429 ”

Rate-limited: either the per-route throttle or a tenant quota. Retry-After carries the seconds until the window rolls over.

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

Headers

Section titled “Headers ”
Retry-After
integer

Seconds until the window rolls over