import { HttpClient, NonNullablePaths, MaybeContext, BuildRESTFunction } from '@wix/sdk-types'; import { CaptchaResponse } from './index.typings.js'; export { AssessmentResponse, CaptchaEntity, CaptchaRequest, Errors } from './index.typings.js'; declare function authorize$1(httpClient: HttpClient): AuthorizeSignature; interface AuthorizeSignature { /** * Authorizes a CAPTCHA token. * * Following CAPTCHA verification on the client side, you must authorize the generated CAPTCHA * token in the backend. * * `Authorize` checks if the token is valid, making sure it was not tampered with or timed out. * * If you're developing a Wix site or Blocks app, call this method when working with the * [Wix reCAPTCHA](https://dev.wix.com/docs/velo/api-reference/$w/captcha/introduction) element. * * If CAPTCHA token authorization fails, the method returns an error message containing a status code. * The following table lists the possible HTTP error status codes, based on * [RFC 2616](https://datatracker.ietf.org/doc/html/rfc2616#section-10): * * * | Status Code | Name | Description | * |---|---|---| * | 400 | Bad Request | The request could not be understood by the server. This could occur for a number of reasons, such as: | * | 401 | Unauthenticated | No user identity found in passed request. | * | 500 | Internal Server Error | The server encountered an unexpected condition, such as a missing or invalid private CAPTCHA key. | * | 503 | Unavailable | The service is unavailable due to one of the following: | * @param - The CAPTCHA token to authorize. */ (token: string): Promise>; } declare const authorize: MaybeContext & typeof authorize$1>; export { CaptchaResponse, authorize };