ConfigRemove a tag assignment

Remove a tag assignment

Remove the tag assignment from this location. The tag stops being served to the SDK once the edge config rebuilds. Agency key (ak_) required.

curl -X DELETE "https://mythic-analytics.gulp.workers.dev/client/v1/config/tags/meta-pixel?location_id=example_string" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "kv_sync": "synced"
}
DELETE
/client/v1/config/tags/{tagId}
DELETE
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key (ak_) or location secret key (sk_). Writes require an agency key. Keys are server-side credentials — this surface serves no CORS headers on purpose. Scoped keys (mcp_) are accepted too and need the tags, snippets or transformers family the route belongs to. See Using an mcp_ key over HTTP.

Agency key (ak_) or location secret key (sk_). Writes require an agency key. Keys are server-side credentials — this surface serves no CORS headers on purpose. Scoped keys (mcp_) are accepted too and need the tags, snippets or transformers family the route belongs to. See Using an mcp_ key over HTTP.
path
tagIdstring
Required

The tag template id of the assignment.

query
location_idstring

Location to scope to. Required for ak_ keys (or send the X-Location-Id header); ignored for sk_.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key (ak_) or location secret key (sk_). Writes require an agency key. Keys are server-side credentials — this surface serves no CORS headers on purpose. Scoped keys (mcp_) are accepted too and need the tags, snippets or transformers family the route belongs to. See Using an mcp_ key over HTTP.

Path Parameters

tagIdstring
Required

The tag template id of the assignment.

Example:
meta-pixel

Query Parameters

location_idstring

Location to scope to. Required for ak_ keys (or send the X-Location-Id header); ignored for sk_.

Responses

successboolean
kv_syncstring

Outcome of the inline edge-config rebuild that follows every write. synced means the location's CFG KV entry was rebuilt from database truth and the SDK will pick the change up; failed: \<reason\> means the database write landed but the edge is still serving the previous config — retry the write (any successful write re-syncs everything) or rebuild via the admin API. This field exists because tenant-config KV sync is not trigger-driven; a write the SDK never sees is the failure mode, so a failed sync is reported instead of silent.