Conflict

What it means

The action collides with something that already exists, or the organization isn't in a state where the action makes sense.

This usually points at your integration's setup rather than anything the end user did. Show the end user a generic message like "Something went wrong on our end.", and log detail for your own debugging.

How to fix it

1. 1.

   Creating or updating a target so its type and metadata match an existing target, because targets deduplicate on those two fields.

   Fetch the existing target from GET /api/v0/targets and use it instead of creating a duplicate.

2. 2.

   Creating a token with a label that's already in use (and not revoked) in this organization.

   Pick a different label, or revoke the existing token first.

3. 3.

   Revoking or fetching a token ID that's malformed or already revoked.

   Re-fetch the current token list. The ID in use is stale.

4. 4.

   Calling POST /api/v0/routing/test when the organization has no active buffers.

   Create at least one buffer, then run the routing test again.

Where this happens

• POST/api/v0/routing/test· Test the routing logic
• POST/api/v0/targets· Create a target
• PATCH/api/v0/targets/{target_id}· Update a target