SettingsDelete a barrier type

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"
"null"
DELETE
/v1/barrier/{id}
DELETE
Base URLstring

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

Bearer Token
Bearer Tokenstring
Required

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.

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
idstring
Required

BarrierRead.Id (GUID). Refers to BarrierRead.Id. Look up valid values with GET /v1/barrier.

Format: uuid
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

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

idstring
Required

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*