Deprecated Resources
Deprecated meshObject API Endpoints
Please review the table below for the list of deprecated and outdated API endpoints.
| EoL Date | Endpoint | Deprecation Notice |
|---|---|---|
| 2025-03-01 | GET /api/meshobjects/meshusersmeshUser.v1 | Please upgrade to meshUser.v2, which features an updated set of _links reflecting the renaming of meshCustomer to meshWorkspace. |
| 2025-03-01 | GET /api/meshobjects/meshusers/{username}meshUser.v1 | Please upgrade to meshUser.v2, which features an updated set of _links reflecting the renaming of meshCustomer to meshWorkspace. |
| 2025-03-01 | GET /api/meshobjects/meshcustomers/{identifier}meshCustomer.v1 | Replace all uses of the meshCustomer object with meshWorkspace. |
| 2025-03-01 | GET /api/meshobjects/meshcustomersmeshCustomer.v1 | Replace all uses of the meshCustomer object with meshWorkspace. |
| 2025-03-01 | GET /api/meshobjects/meshserviceinstancesmeshServiceInstance.v1 | Please upgrade to meshServiceInstance.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-03-01 | GET /api/meshobjects/meshserviceinstances/{serviceIdentifier}meshServiceInstance.v1 | Please upgrade to meshServiceInstance.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-03-01 | GET /api/meshobjects/meshcustomerusergroupsmeshCustomerUserGroup.v1 | Replace all uses of meshCustomerUserGroup object with meshWorkspaceUserGroup. |
| 2025-03-01 | GET /api/meshobjects/meshcustomerusergroups/{fullCustomerUserGroupIdentifier}meshCustomerUserGroup.v1 | Replace all uses of meshCustomerUserGroup object with meshWorkspaceUserGroup. |
| 2025-07-01 | GET /api/meshobjects/meshpaymentmethods/{identifier}meshPaymentMethod.v1 | Please upgrade to meshPaymentMethod.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshpaymentmethodsmeshPaymentMethod.v1 | Please upgrade to meshPaymentMethod.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshprojectsmeshProject.v1 | Please use meshProject.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshprojects/{fullProjectIdentifier}meshProject.v1 | Please use meshProject.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshtenantsmeshTenant.v1 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshtenants/{tenantIdentifier}meshTenant.v1 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshtenantsmeshTenant.v2 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | GET /api/meshobjects/meshtenants/{tenantIdentifier}meshTenant.v2 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacksmeshChargeback.v1 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacks/{name}meshChargeback.v1 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacksmeshChargeback.v2 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacks/{name}meshChargeback.v2 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacksmeshChargeback.v3 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
| 2025-10-01 | GET /api/meshobjects/meshchargebacks/{name}meshChargeback.v3 | Note: This endpoint is part of the separate metering API service.Please migrate to meshTenantUsageReport.v3 which now contains usage and chargeback data for every report. The meshChargeback object as an aggregation of different usage reports will be removed from the meshObject API. Just like the meshChargeback object, the meshTenantUsageReport.v3 contains line item data at seller-product-group level aggregation. Please be advised that a future change will move the API base url from the metering API to the standard meshObject API endpoint, so it's a good idea to keep the API base url configurable. |
GET /api/meshobjects/meshworkspacesmeshWorkspace.v1 | Please update to meshWorkspace.vv2 at your earliest convenience. | |
GET /api/meshobjects/meshworkspaces/{identifier}meshWorkspace.v1 | Please update to meshWorkspace.vv2 at your earliest convenience. | |
GET /api/meshobjects/meshtenantsmeshTenant.v3 | Please consider upgrading to meshTenant.v4, which uses a UUID to identify a meshTenant. | |
POST /api/meshobjects/meshtenantsmeshTenant.v3 | Please consider upgrading to meshTenant.v4, which uses a UUID to identify a meshTenant. | |
GET /api/meshobjects/meshtenants/{tenantIdentifier}meshTenant.v3 | Please consider upgrading to meshTenant.v4, which uses a UUID to identify a meshTenant. | |
GET /api/meshobjects/meshbuildingblocksmeshBuildingBlock.v1 | Please consider adopting meshBuildingBlock.v2, which supports building blocks on workspace level as well. | |
GET /api/meshobjects/meshbuildingblocks/{buildingBlockUuid}meshBuildingBlock.v1 | Please consider adopting meshBuildingBlock.v2, which supports building blocks on workspace level as well. | |
POST /api/meshobjects/meshbuildingblocksmeshBuildingBlock.v1 | Please consider adopting meshBuildingBlock.v2, which supports building blocks on workspace level as well. | |
GET /api/meshobjects/meshplatforms/{uuid}meshPlatform.v1 | Please update to meshPlatform.vv2-preview at your earliest convenience. | |
PUT /api/meshobjects/meshplatforms/{uuid}meshPlatform.v1 | Please update to meshPlatform.vv2-preview at your earliest convenience. | |
GET /api/meshobjects/meshplatformsmeshPlatform.v1 | Please update to meshPlatform.vv2-preview at your earliest convenience. | |
POST /api/meshobjects/meshplatformsmeshPlatform.v1 | Please update to meshPlatform.vv2-preview at your earliest convenience. |
Deprecated meshObjects in Declarative Import
Please review the table below for the list of deprecated and outdated meshObjects that can no longer be used with the meshObject Declarative Import API.
| EoL Date | meshObject | Deprecation Notice |
|---|---|---|
| 2025-03-01 | meshCustomer.v1 | Replace all uses of the meshCustomer object with meshWorkspace. |
| 2025-03-01 | meshCustomerUserBinding.v1 | Please upgrade to meshWorkspaceUserBinding.v2, which targets a meshWorkspace instead of a meshCustomer. |
| 2025-03-01 | meshCustomerUserGroup.v1 | Replace all uses of meshCustomerUserGroup object with meshWorkspaceUserGroup. |
| 2025-03-01 | meshCustomerGroupBinding.v1 | Please upgrade to meshWorkspaceGroupBinding.v2, which targets a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshUser.v1 | Please upgrade to meshUser.v2, which features an updated set of _links reflecting the renaming of meshCustomer to meshWorkspace. |
| 2025-07-01 | meshPaymentMethod.v1 | Please upgrade to meshPaymentMethod.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshProject.v1 | Please use meshProject.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshProjectUserBinding.v1 | Please upgrade to meshProjectUserBinding.v3. The new version has a metadata.name field and the subjects field has been replaced with a single subject. |
| 2025-07-01 | meshProjectGroupBinding.v1 | Please upgrade to meshProjectGroupBinding.v3. The new version has a metadata.name field and the subjects field has been replaced with a single subject. |
| 2025-07-01 | meshTenant.v1 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshTenant.v2 | Please upgrade to meshTenant.v3, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshServiceInstance.v1 | Please upgrade to meshServiceInstance.v2, which is owned by a meshWorkspace instead of a meshCustomer. |
| 2025-07-01 | meshWorkspaceGroupBinding.v1 | Please upgrade to meshWorkspaceGroupBinding.v2. The new version has a metadata.name field and the subjects field has been replaced with a single subject. |
meshWorkspace.v1 | Please update to meshWorkspace.v2 at your earliest convenience. | |
meshWorkspaceUserBinding.v1 | Please upgrade to meshWorkspaceUserBinding.v2. The new version has a metadata.name field and the subjects field has been replaced with a single subject. | |
meshProjectUserBinding.v2 | Please upgrade to meshProjectUserBinding.v3. The new version has a metadata.name field and the subjects field has been replaced with a single subject. | |
meshProjectGroupBinding.v2 | Please upgrade to meshProjectGroupBinding.v3. The new version has a metadata.name field and the subjects field has been replaced with a single subject. | |
meshTenant.v3 | Please consider upgrading to meshTenant.v4, which uses a UUID to identify a meshTenant. |