> ## Documentation Index > Fetch the complete documentation index at: https://developers.wachat.net/llms.txt > Use this file to discover all available pages before exploring further. # Create auto-replies > Creates a keyword auto-reply rule that responds when an inbound message matches its configured trigger. Use it for simple automated answers without creating a full flow. ## OpenAPI ````yaml /openapi.json post /auto-replies openapi: 3.1.0 info: title: Wachat API version: v1 description: >- Wachat REST API. Authenticate with a workspace API key: send it as `Authorization: Bearer `. Generate keys in the dashboard under Developers / API. servers: - url: https://crm.wachat.net/api/v1 security: - http: [] tags: - name: Message description: >- Send a single WhatsApp message — text, media (image / video / document / audio) or a location pin — to one number, then read its delivery status or your message history. A file can be attached directly as a multipart `media` field or referenced by a public URL. - name: Template description: >- Create, list and manage your approved WhatsApp templates, and send a template to one number with your own header, body variables and button values. Use this for utility / marketing sends that need a pre-approved template — including one with a PDF / document header (pass the file's public URL as the header, e.g. from the Media endpoint). - name: Media description: >- Upload a file once (multipart / form-data, field name `file`, up to 16 MB) and get back a hosted public URL you can reuse across sends — for example a PDF to use as a document-header on a template, or an image on a message. - name: Contact description: >- Full create / read / update / delete over your contacts and leads, including search by number, tags and custom attributes. - name: ContactGroup description: >- Organise contacts into groups: create groups, list them, and add or remove members — handy for targeting broadcasts and campaigns. - name: Broadcast description: >- Send the same message to many contacts at once and track each broadcast's progress and per-recipient delivery. - name: Campaign description: >- Create, start, pause and monitor drip / marketing campaigns and their recipients. - name: Scheduled description: >- Schedule a WhatsApp send for a future time, list upcoming scheduled messages, and cancel one before it goes out. - name: AutoReply description: >- Manage keyword auto-replies — the automatic responses that fire when an inbound message matches a rule. - name: Flow description: >- Enroll a contact into an automation flow (chatbot) and manage your flows through the API. - name: Device description: >- List the WhatsApp numbers / devices connected to your workspace and check each one's connection status. - name: Webhook description: >- Register and manage webhook endpoints so Wachat POSTs real-time events (message received / sent / delivered / read / failed, plus campaign and contact events) to your server. When you set a signing secret each delivery carries an HMAC-SHA256 signature header you can verify. - name: Deal description: >- Manage sales-pipeline deals — create, list, update and move deals between stages. - name: Conversation description: >- Read your workspace inbox: list chat threads (conversations) and fetch the messages inside a thread. - name: Account description: Read your account details, plan, limits and message-credit usage. paths: /auto-replies: post: tags: - AutoReply summary: Create auto-replies description: >- Creates a keyword auto-reply rule that responds when an inbound message matches its configured trigger. Use it for simple automated answers without creating a full flow. operationId: v1.auto-replies.store requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/StoreAutoReplyRequest' responses: '201': description: Resource created successfully. content: application/json: schema: type: object properties: data: type: array items: {} meta: type: string required: - data - meta '422': $ref: '#/components/responses/ValidationException' description: Request failed. components: schemas: StoreAutoReplyRequest: type: object description: |- Create a keyword auto-reply. Scramble reads these rules to document the request body. Mirrors the input keys the existing AutoreplyController::store accepts, exposed under public-facing names. A "custom" reply carries one or more `replies[]` text variants; a "flow" reply points at a saved flow_id. properties: keyword: type: string description: Trigger keyword(s). Comma-separated phrases are allowed. Required. maxLength: 255 matching_method: type: - string - 'null' description: >- How the inbound message is matched against the keyword. Defaults to exact. enum: - fuzzy - exact - contains fuzzy_similarity: type: - integer - 'null' description: Fuzzy match threshold 0-100 (only used when matching_method=fuzzy). minimum: 0 maximum: 100 device_id: type: string description: Sending device id. Required. status: type: - boolean - 'null' description: Whether the rule is active. Defaults to true. reply_type: type: - string - 'null' description: >- Reply kind: "custom" (text variants) or "flow" (a saved flow). Defaults to custom. enum: - custom - flow flow_id: type: - integer - 'null' description: |- Flow id to run (required when reply_type=flow). Scope to the caller's workspace so an auto-reply can't reference another tenant's flow (was a bare `integer` with no ownership). replies: type: - array - 'null' description: >- Reply text variants (for reply_type=custom). At least one required for custom. items: type: string maxLength: 4096 required: - keyword - device_id title: StoreAutoReplyRequest responses: ValidationException: description: Validation error content: application/json: schema: type: object properties: message: type: string description: Errors overview. errors: type: object description: A detailed description of each field that failed validation. additionalProperties: type: array items: type: string required: - message - errors securitySchemes: http: type: http scheme: bearer ````