IntegrationsGet an integration conflict

Get an integration conflict

Returns one integration conflict by its integer ConflictID.

Reads a single conflict, including its current status and the resolve options for its type. Create answers with this same representation.

Use it to:

  • Follow up a conflict your integration reported: has someone resolved or ignored it yet?

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

Call first: GET /v1/integration-conflicts

See also: POST /v1/integration-conflicts

Not yet documented: examples (success).

curl -X GET "https://app3.timelog.com/your-account/api/v1/integration-conflicts/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "ConflictID": 123,
    "ID": "123e4567-e89b-12d3-a456-426614174000",
    "ConflictDateTime": "2024-12-25T10:00:00Z",
    "ConflictType": 42,
    "ConflictStatusType": 42,
    "ResolveOptionTypes": [
      "null"
    ],
    "ResolveOptionTypeUsed": 42,
    "ResolvedByUserID": "null",
    "OriginalErrorCode": 42,
    "OriginalErrorMessage": "example_string",
    "ExternalSystemID": 123
  },
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ],
  "Actions": [
    {}
  ]
}
GET
/v1/integration-conflicts/{integrationConflictID}
GET
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
integrationConflictIDinteger
Required

The conflict's integer ID.

Format: int32
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

integrationConflictIDinteger
Required

The conflict's integer ID.

Responses

Propertiesobject

A record that a change coming from an external system could not be applied in TimeLog because of a TimeLog business rule, kept so that someone can decide how to resolve it. At this commit exactly one kind is supported: a task that cannot be deleted because it sits in a completed task-driven revenue contract (TimeLog error 37886). Conflicts are created Active and carry the resolve options TimeLog offers for their type; REST v1 has no operation to change their status.

Linksarray
Actionsobject[]