Details

Create a client.

An account token or server token may be used to run this endpoint.

Parameters

body

ecosystemId (required): The ID of the ecosystem.
type (required): The type of the client. This may be “application” or “server.”
name (optional): The name of the client.
description (optional): The description of the client.

Responses

201

{
    "createdAt": "YYYY-MM-DD HH:MM:SS ENCODED",
    "description": "CLIENT-DESCRIPTION",
    "ecosystemId": "ECOSYSTEM-ID",
    "id": "CLIENT-ID",
    "name": "CLIENT-NAME",
    "type": "CLIENT-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.
Ecosystem Missing: The standard error structure defines this error as both an invalid parameter name and a missing parameter. In this context, it means that the parameter which is used to specify an ecosystem ID is not present.
Query Field Not Allowed: The standard error structure defines this error as invalid parameters, with additional parameters in the query string. In this context, it means that one or more query string fields are incorrect. They do not match the name(s) of the query string field(s) that are allowed for 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.”
Client Type Invalid: The standard error structure defines this error as invalid parameters, with a list of valid client type options. In this context, it means that the value given for the client type is not one of the valid options.
Client Type Missing: The standard error structure defines this error as invalid parameters. In this context, it means that the client type is missing, and was required.

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.

Examples

HTTP

POST https://ioe.droplit.io/api/clients HTTP/1.1
authorization: TOKEN
content-type: application/json
{
    "ecosystemId" "ECOSYSTEM-ID"
    "type": "CLIENT-TYPE",
    "name": "CLIENT-NAME",
    "description": "CLIENT-DESCRIPTION"
}

Droplit Console

droplit client create --ecosystemId ECOSYSTEM-ID

Droplit SDK

droplit.clients.create("ECOSYSTEM-ID", "TYPE", "NAME", "DESCRIPTION");