ToolsService_UpdateExclusiveContent
const url = 'https://dictionary.example.invalid/api/v1/exclusive-content/update';const options = {method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://dictionary.example.invalid/api/v1/exclusive-content/update \ --header 'Content-Type: application/json' \ --data '{}'Request Bodyrequired
Заголовок раздела «Request Bodyrequired»object
Example
{}Responses
Заголовок раздела «Responses»OK
object
Example
{ "requestId": "DEMO_VALUE"}default
Заголовок раздела «default»Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example
{ "code": 1, "message": "DEMO_VALUE", "details": [ { "@type": null } ]}