> ## Documentation Index > Fetch the complete documentation index at: https://platform.doodocs.kz/llms.txt > Use this file to discover all available pages before exploring further. # Test Webhook Endpoint > Synchronously delivers a signed ping to the endpoint and returns the HTTP status the receiver responded with (or a connection error). Useful for verifying signature handling before real events flow. Required scope: webhooks:manage ## OpenAPI ````yaml /api-reference/openapi.yaml post /developer/v1/webhook_endpoints/{id}/_test openapi: 3.0.3 info: description: >- Публичный Developer API Doodocs People. Аутентификация — заголовок X-API-Key. title: Doodocs People API version: 1.0.0 servers: - description: Production url: https://app.doodocs.kz/api security: - ApiKeyAuth: [] tags: - description: ApiKeyService exposes Developer API key utilities. name: ApiKeyService - description: >- DocumentService is the public Developer API for documents: reading, creating, downloading, routing, and signing. Authentication: X-API-Key. Every call runs as the key's owner within the key's tenant — the owner's document permissions decide what is visible and which actions are allowed, exactly as they would in the web app. Fields that carry personal data of other participants (names, IIN, positions) are never exposed; participants are identified by id only. Typical flow: discover a template with ListDocumentTemplates / GetDocumentTemplate (to learn its variable_schema), create a draft with CreateDocument, set its route with SetDocumentRoute, launch it with SendDocument, then apply signatures with SignDocument as slots become active. To circulate a document produced elsewhere, upload it with FileService and pass the confirmed file_id to CreateDocument instead of a template. name: DocumentService - description: |- EmployeeService is the public Developer API for reading employees. Authentication: X-API-Key. The key's tenant and the key owner's data scope determine which employees and fields are visible; sensitive fields the caller may not view are omitted and listed in `redacted_fields`. name: EmployeeService - description: |- FileService uploads the files documents are created from. Authentication: X-API-Key. An upload belongs to the key's owner, and only their key can attach it to a document. Flow: CreateFileUpload reserves the file and returns a presigned POST form, the client sends the bytes straight to storage, ConfirmFileUpload marks the upload complete, and CreateDocument attaches it by id. name: FileService - description: IngestService accepts batches of external records into the tenant. name: IngestService - name: LoginService - description: |- WebhookService lets a tenant manage subscriptions to Developer API events. Authentication: X-API-Key with the webhooks:manage scope. name: WebhookService paths: /developer/v1/webhook_endpoints/{id}/_test: post: tags: - WebhookService summary: Test Webhook Endpoint description: >- Synchronously delivers a signed ping to the endpoint and returns the HTTP status the receiver responded with (or a connection error). Useful for verifying signature handling before real events flow. Required scope: webhooks:manage operationId: WebhookService_TestWebhookEndpoint parameters: - description: Endpoint id (UUID) to send the test ping to. in: path name: id required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TestWebhookEndpointRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/TestWebhookEndpointResponse' description: OK default: content: application/json: schema: $ref: '#/components/schemas/Status' description: Default error response components: schemas: TestWebhookEndpointRequest: properties: id: description: Endpoint id (UUID) to send the test ping to. type: string required: - id type: object TestWebhookEndpointResponse: properties: error: description: Connection or transport error, empty on a completed request. readOnly: true type: string status_code: description: >- HTTP status returned by the receiver, or 0 if the request could not be sent. format: int32 readOnly: true type: integer type: object Status: description: >- 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](https://github.com/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](https://cloud.google.com/apis/design/errors). properties: code: description: >- The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. format: int32 type: integer details: description: >- A list of messages that carry the error details. There is a common set of message types for APIs to use. items: $ref: '#/components/schemas/GoogleProtobufAny' type: array message: description: >- 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. type: string type: object GoogleProtobufAny: additionalProperties: true description: >- Contains an arbitrary serialized message along with a @type that describes the type of the serialized message. properties: '@type': description: The type of the serialized message. type: string type: object securitySchemes: ApiKeyAuth: in: header name: X-API-Key type: apiKey ````