Delete a credential
Delete a credential for the calling location. Requires an agency (ak_) key. Omitting credential_name deletes all credentials of the given type. Deleting a meta_ads token also removes the client's Ad UTM tagging setup that uses it, cancels its queued runs and frees its ad account for another client; the response then carries data.ad_tagging_removed. Run history stays.
curl -X DELETE "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/credentials/meta_capi?credential_name=John%20Doe" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/credentials/meta_capi?credential_name=John%20Doe"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.delete(url, headers=headers)
print(response.json())
const response = await fetch("https://mythic-analytics.gulp.workers.dev/client/v1/destinations/credentials/meta_capi?credential_name=John%20Doe", {
method: "DELETE",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("DELETE", "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/credentials/meta_capi?credential_name=John%20Doe", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://mythic-analytics.gulp.workers.dev/client/v1/destinations/credentials/meta_capi?credential_name=John%20Doe')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Delete.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"success": true
}
{
"error": "Bad Request",
"message": "The request contains invalid parameters or malformed data",
"code": 400,
"details": [
{
"field": "email",
"message": "Invalid email format"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Forbidden",
"message": "You don't have permission to access this resource",
"code": 403
}
{
"error": "Too Many Requests",
"message": "Rate limit exceeded. Please try again later",
"code": 429,
"retryAfter": 3600
}
{
"error": "Error",
"message": "Upstream data store returned an error.",
"code": 502
}
/client/v1/destinations/credentials/{type}Target server for requests. Edit to use your own host.
Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Destination type the credential belongs to. convert_experiments is a special case: delivering to Convert needs no credential at all, but reading Convert's report to verify a delivery does, so its only valid credential_name is reporting. meta_ads is not a destination at all: it is the Meta Marketing API token (system user, ads_read + ads_management) that Ad UTM tagging reads. Nothing delivers events with it.
Restrict the delete to a single named credential.
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Path Parameters
Destination type the credential belongs to. convert_experiments is a special case: delivering to Convert needs no credential at all, but reading Convert's report to verify a delivery does, so its only valid credential_name is reporting. meta_ads is not a destination at all: it is the Meta Marketing API token (system user, ads_read + ads_management) that Ad UTM tagging reads. Nothing delivers events with it.
meta_capigoogle_adsgoogle_analyticsopenai_adsconvert_experimentsmida_experimentsmeta_adsQuery Parameters
Restrict the delete to a single named credential.