Skip to main content

POST Add Api Key To Projects

Overview


The following table contains important information about the POST method in regards to adding an Api Key to projects.

POST Add Api Key To Projects
MethodPOST
URL or Endpoint/api/organizations/organizationId/api-keys/projects
HeadersAuthorization
ParametersorganizationId, api-version
BodyCheck request body below

The description of the URL parameter is as follows:

URL Parameter NameMandatoryTypeDescription
organizationIdYesstringUnique Id of the organization.
api-versionNostringThe correct api version to use.

Request Body

{
"apiKeyId": 0,
"projectIds": [
"string"
]
}
Field NameTypeDescription
apiKeyIdintegerThe Id of the Api Key.
peojectIdsstringThe Ids of the project.

Response

{
"success": true,
"errors": [
"string"
],
"messages": [
"string"
],
"result": true,
"resultInfo": "string",
"statusCode": 0
}

Information about the fields that appear when you receive the response are displayed in the table below.

Field NameTypeDescription
successboolIf the response is successful it will return true. Otherwise will return false.
errorsarray[]Indicates if there was an error.
messagesarray[]Returns the response message from back-end.
resultarray[Object]Returns the response object.
resultInfostringReturns extra information about the result.
statusCodeinteger($int32)Returns the HTTP Status Code.

If the action is successful, the service sends back an HTTP 200 or 201 response.

Errors

For information about the errors that are common to all actions, see Common Errors:

  • HTTP Status Code 400: Bad Request

  • HTTP Status Code 401: Unauthorized

  • HTTP Status Code 403: Forbidden

  • HTTP Status Code 404: Result Not Found

  • HTTP Status Code 500: Internal Server Error

  • HTTP Status Code 503: Backend Fetch Failed