Delete a barrier type
Permanently deletes a CRM barrier type that no opportunity uses, by its GUID.
Hard delete. Refused (30118) while any opportunity lists the barrier. The id is the barrier's GUID (Id), not the integer BarrierID.
Behaviour:
- Not idempotent.
- Safe to retry only under a condition. A repeat after success hits an unknown id (500 Code 100).
- Changes are visible to the next read immediately.
See also: GET /v1/barrier
Not yet documented: examples.
curl -X DELETE "https://app3.timelog.com/your-account/api/v1/barrier/123e4567-e89b-12d3-a456-426614174000" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/barrier/123e4567-e89b-12d3-a456-426614174000"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.delete(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v1/barrier/123e4567-e89b-12d3-a456-426614174000", {
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://app3.timelog.com/your-account/api/v1/barrier/123e4567-e89b-12d3-a456-426614174000", 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://app3.timelog.com/your-account/api/v1/barrier/123e4567-e89b-12d3-a456-426614174000')
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
"null"
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Error",
"message": "- The route matched, but no action for this HTTP method accepted the request. Observed when a DELETE that needs required (non-nullable) query parameters is sent without them: the versioning layer reports it as an unsupported version / method, although the method is listed in the Allow header. It is a missing-parameter error that looks like a 405. Returned before authentication (also without a token). — When: id is not a GUID (captured).",
"code": 405
}
{
"Code": 100,
"Details": [],
"Message": "Unknown error occur in system, please contact system administrator.",
"Parameters": "id: "00000000-0000-0000-0000-000000000001"",
"Url": "https://app{server-number}.timelog.com/{account}/api/v1/barrier/00000000-0000-0000-0000-000000000001"
}
/v1/barrier/{id}Target server for requests. Edit to use your own host.
OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.
Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.BarrierRead.Id (GUID).
Refers to BarrierRead.Id. Look up valid values with GET /v1/barrier.
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
Not yet documented: how to obtain a token.
Not yet documented: token lifetime.
Path Parameters
BarrierRead.Id (GUID).
Refers to BarrierRead.Id. Look up valid values with GET /v1/barrier.
Responses
*Success without content: HTTP 200 with the literal JSON body null. Literal JSON null (TafSuccessResult).
Order: none
Empty result: none*