Endpoint Migration Notice: We’re transitioning to kebab-case endpoints. The new endpoint is
/api/v2/data-app/embeds
. The old endpoint /api/v2/dataApp/embeds
will be deprecated soon. Please update your integrations to use the new endpoint format.Updates to embed configurations take effect immediately for all active embedded dashboards and metrics using this configuration.
Endpoint Formats
- New Endpoint (Recommended)
- Legacy Endpoint (Deprecated Soon)
Authentication
All API requests must include your API key in the Authorization header. Get your API token when creating a data app - see our data app creation guide for details. Finding your API token: For detailed instructions, see the API Token guide.Headers
Bearer token for API authentication. Use your API key from the data app.
Must be set to
application/json
for all requests.Request Body
The unique identifier of the embed configuration to update. Get this from the create embed response or list embeds API.
Updated access control settings for the embedded view. Only provided fields will be updated.
Change the datamart used by this embed configuration.
Update AI pilot features permission.
Update email reports permission.
Update metrics management permission.
Update metric creation permission.
Update metric deletion permission.
Update metric layout change permission.
Update metric modification permission.
Update underlying data access permission.
Update dashboard view creation permission.
Update the metric creation mode.
Response
The ID of the updated embed configuration.
Error object if the request failed, otherwise
null
for successful requests.Examples
Error Codes
Embed configuration not found - The specified embed ID doesn’t exist in the workspace
Workspace not found - The specified workspace doesn’t exist or you don’t have access
Invalid datamart - The specified datamart doesn’t exist in the workspace
Insufficient permissions - You don’t have permission to update this embed configuration
Invalid API key - Check your API key in dashboard settings
HTTP Status Code Summary
Status Code | Description |
---|---|
200 | OK - Embed configuration updated successfully |
400 | Bad Request - Invalid request parameters |
401 | Unauthorized - Invalid or missing API key |
403 | Forbidden - Insufficient permissions to update |
404 | Not Found - Embed configuration not found |
409 | Conflict - Update conflicts with existing configuration |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error - Server error occurred |
Possible Errors
Error Code | HTTP Status | Description | Solution |
---|---|---|---|
EMBED_NOT_FOUND | 404 | Embed configuration not found | Verify embed ID exists in workspace |
INVALID_WORKSPACE_NAME | 404 | Workspace not found | Verify workspace name and access |
INVALID_DATAMART | 404 | Datamart not found | Verify datamart exists in workspace |
INSUFFICIENT_PERMISSIONS | 403 | No permission to update | Contact admin for embed update permissions |
AUTHENTICATION_ERR | 401 | Invalid API key | Verify your API key is correct |
INVALID_ACCESS_SETTINGS | 400 | Invalid access settings | Check accessSettings object structure |
CONFLICTING_UPDATE | 409 | Update conflicts with existing config | Resolve configuration conflicts |
RATE_LIMIT_EXCEEDED | 429 | Too many requests | Implement exponential backoff |
INTERNAL_SERVER_ERROR | 500 | Server error | Contact support if error persists |
Update Strategies
1
Incremental updates
Update only the fields you need to change:
2
Permission escalation
Gradually increase permissions based on user needs:
3
Datamart migration
Move embed to a different datamart:
4
Security tightening
Reduce permissions when needed:
Common Update Scenarios
Enable Advanced Features
Migrate to New Datamart
Temporary Permission Reduction
Best Practices
Change Management
- Document all configuration changes
- Test updates in staging first
- Notify stakeholders of permission changes
- Maintain change history and rollback plans
Security
- Follow principle of least privilege
- Regular permission audits
- Monitor for unauthorized changes
- Validate datamart access before updates
Performance
- Batch multiple updates when possible
- Monitor embed performance after changes
- Test with production data volumes
- Update during low-usage periods
User Experience
- Communicate feature changes to users
- Provide training for new capabilities
- Gradual rollout of new permissions
- Collect feedback on configuration changes
Advanced Configuration
Dynamic Permission Updates
Bulk Updates
Quick Start Guide
1
Find your embed ID
List your existing embed configurations to find the one you want to update:
2
Update specific permissions
Update only the settings you want to change. For example, to enable AI pilot:
3
Migrate to new datamart
Change the datamart associated with your embed:
4
Verify the update
The API will return the embed ID on success: