Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BaSyx / Documentation / API / Registry"
< BaSyx | Documentation | API
Line 60: | Line 60: | ||
'''Response codes''' | '''Response codes''' | ||
− | * | + | * 200: The Asset Administration Shell’s registration was successfully renewed |
* 400: The syntax of the passed Asset Administration Shell is not valid or malformed request | * 400: The syntax of the passed Asset Administration Shell is not valid or malformed request | ||
* 404: No Asset Administration Shell with passed id found | * 404: No Asset Administration Shell with passed id found | ||
Line 78: | Line 78: | ||
'''Response codes''' | '''Response codes''' | ||
− | * | + | * 200: The Asset Administration Shell was deleted successfully |
* 400: Bad Request | * 400: Bad Request | ||
* 404: No Asset Administration Shell with passed id found | * 404: No Asset Administration Shell with passed id found |
Revision as of 09:31, 11 June 2019
The BaSys 4.0 Registry enables registration and lookup of Asset Administration Shells within defined system boundaries. Entities that provide Asset Administration Shells including their submodels may register and hence enable other participants to find them. The necessary information required for registration amongst others are unique identifiers for the Administration Shell and her respective Asset, endpoint information regarding the Asset Administration Shell's API and their submodel service provider.
GET | /api/v1/registry | Description
|
POST | /api/v1/registry | Description
|
GET | /api/v1/registry/{aasId} | Description
|
PUT | /api/v1/registry/{aasId} | Description
|
DELETE | /api/v1/registry/{aasId} | Description
|
BaSyx project links: Project BaSyx main wiki page | What is BaSyx? | BaSyx Developer Documentation |