Developer

Appearance

Troubleshooting

Common integration issues when embedding the rooomAvatars Editor and using the API.

Use this page to diagnose common issues in editor embedding, API authentication, origin validation, and avatar export.

Editor does not load ​

Check that:

  • The iframe src includes #token=API_TOKEN in the URL hash.
  • The editor host URL is correct and reachable.
  • The allow attribute grants the permissions the editor needs. Use allow="camera *; clipboard-read; clipboard-write" for the full feature set (camera-based avatar creation, copy/paste). Drop entries you do not need.

Replace API_TOKEN with the token for your rooomAvatars integration.

Unauthorized (HTTP 401) ​

POST /avatar returns 401 Unauthorized when the bearer token is missing or incorrect.

Check that the request uses this header format:

http
Authorization: Bearer API_TOKEN

CORS or forbidden origin (HTTP 403) ​

403 Forbidden can occur when the request origin is not allowed for your integration. Verify that the origin of your embedding page matches the allowed origin configured for your rooomAvatars API access.

Model generation fails ​

If GET /model/:id.glb returns a JSON error, the avatar model could not be generated. Retry the request with the AVATAR_ID returned by POST /avatar or the rooom-avatars-completed message.

bash
# AVATAR_ID is the registered avatar ID.
curl -o avatar.glb "https://api.avatars.rooom.com/model/AVATAR_ID.glb"

Replace AVATAR_ID with the registered avatar ID.