post https://ioe.droplit.io/v0/api/ecosystems//claims
Details
Create a server ecosystem claim.
An account token may be used to run this endpoint.
Parameters
path
- id (required): The ID of the ecosystem.
body
- edgeId (required): The ID of the Edge server.
Responses
201
{
"claimType": "CLAIM-TYPE",
"ecosystemId": "ECOSYSTEM-ID",
"edgeId": "EDGE-ID",
"environmentId": "ENVIRONMENT-ID",
"id": "ECOSYSTEM-ID;EDGE-ID;CLAIM-TYPE"
}
400
- Ecosystem Invalid: The standard error structure defines this error as invalid parameters, with an invalid ID linked to the parameter that designates the ecosystem ID. In this context, it means that the ID given for an ecosystem was not valid.
- No Query String Allowed: The standard error structure defines this error as invalid parameters, with additional parameters in the query string. In this context, it means that no query string is allowed at all when calling this endpoint.
- Body Parameters Missing: The standard error structure defines this error as invalid parameters, and contains all required body parameters. If this error occurs when the JSON structure of the body parameters is syntactically correct, this means that the “content-type” header is incorrectly specified. The content-type header should be “application/json.”
404
- Ecosystem Not Found: This error means that an ecosystem with the given ID was not found. This is distinct from an invalid ecosystem ID being specified; this means that the ecosystem ID once existed, but no longer does.
- Edge ID Invalid: The standard error structure defines this error as invalid parameters, with an invalid ID. In this context, it means that the Edge ID given is not valid.
Examples
HTTP
POST https://ioe.droplit.io/api/ecosystems/ECOSYSTEM-ID/claims HTTP/1.1
authorization: TOKEN
content-type: application/json
{
"edgeId": "EDGE-ID"
}
Droplit Console
droplit ecosystem create-claim ECOSYSTEM-ID EDGE-ID
Droplit SDK
droplit.ecosystems.createClaim("ECOSYSTEM-ID", "EDGE-ID");