Jive REST API v3: Avatar Delete Returns HTTP 200 and Does Not Remove the Avatar

Overview

If a Jive avatar delete request appears to “not work” (for example, DELETE /people/<person_id>/avatar returns HTTP 200 instead of the documented 204, and the response looks like a default avatar image while the avatar remains unchanged), the request is typically being sent to the wrong URL.

This most commonly happens when the Jive REST API v3 base path /api/core/v3 is missing, so the request does not reach the intended v3 REST endpoint.

Solution

Issue

A request intended to delete a user’s avatar does not delete anything and instead returns an unexpected status code and content.

Reported symptoms

HTTP status code returned: 200 (expected 204 per developer documentation)
Response appears to return an image (often resembling the default avatar)
The user’s avatar does not change/delete

Root cause

The DELETE request was sent to an endpoint missing the Jive REST API v3 base path. Without /api/core/v3, the request may be routed to a different handler than the documented v3 REST API route.

Resolution

Re-issue the DELETE request using the correct Jive REST API v3 URL format that includes /api/core/v3.

Correct endpoint pattern

DELETE https://your_instance.domain.com/api/core/v3/people/<person_id>/avatar

Example (curl)

Use your preferred authentication method; the critical requirement is the URL path.

curl --request DELETE \
  'https://your_instance.domain.com/api/core/v3/people/<person_id>/avatar' \
  --header 'Authorization: <redacted>'

Troubleshooting (if it still fails)

If the behavior persists after correcting the endpoint, capture verbose request/response details and confirm the final URL being reached (redact any credentials/tokens).

Re-run with verbose output:

curl -v --request DELETE \
  'https://your_instance.domain.com/api/core/v3/people/<person_id>/avatar' \
  --header 'Authorization: <redacted>'

Review the -v output to confirm the request path, any redirects, and the exact response returned.

Verification

Re-run the DELETE against:

https://your_instance.domain.com/api/core/v3/people/<person_id>/avatar

Confirm the user’s visible avatar changes as expected after the call (for example, by viewing the profile/avatar in the UI).

Note: In the validated case, correcting the URL resolved the behavior immediately. No product defect was identified, and no engineering or infrastructure escalation was required.

Frequently Asked Questions

1. How do I know I’m hitting the wrong endpoint?

If your request URL looks like https://your_instance.domain.com/people/<person_id>/avatar (missing /api/core/v3) and you see symptoms like HTTP 200 plus content that looks like an image (for example, a default avatar), you are likely not reaching the intended Jive REST API v3 endpoint.

2. What is the correct URL to delete an avatar via the Jive REST API v3?

Use:

DELETE https://your_instance.domain.com/api/core/v3/people/<person_id>/avatar

The critical requirement is including the /api/core/v3 base path.

3. What should I provide if the corrected endpoint still doesn’t work?

Re-run the request with verbose logging (curl -v) and share the output with secrets redacted. The verbose output helps confirm the exact URL reached, whether redirects occurred, and what response was returned.

4. How can I verify the fix worked?

After calling the corrected DELETE endpoint, re-check the user’s avatar (for example, by viewing the profile/avatar in the UI) to confirm it changed as expected. The reported case was resolved immediately after correcting the URL.

Choose files or drag and drop files

ai_initiated

atlas_studio

kb_automation

Tags:

Was this article helpful?

Yes

Priyanka Bhotika
Posted

Comments

Please sign in to comment