Contact Form 7 to API

Contact Form 7 to API adds an API Integration tab to each form. When the form is submitted, the entry is sent to the URL you set.

What you can send

• Parameters. Map each form field to an API key. GET adds the pairs to the query string and sends no body. POST sends them as the body.
• JSON. The filled template is the request body for both GET and POST.
• XML. The filled template is the request body. XML is always sent as POST, and the method menu is hidden.
• Files. Uploads are sent as base64. A file larger than 8 MB is left out.
• Acceptance. In JSON, an acceptance field is a boolean: true when checked and false when it is not. In XML and in parameter mode it is the text true or false .
• Auth. Basic auth ( user:secret ) or a Bearer token. Bearer is used when both are filled in, and both are sent on GET and POST.
• Headers. One Name: value line each.
• Timeout. Defaults to 15 seconds. You can set 1 to 60 seconds on the form.

A JSON template looks like this:

{ "name": "[your-name]", "email": "[your-email]" }

If the URL already has a query string, mapped fields are added with & . https://example.com/hook?token=abc keeps the token, and the fields follow it.

When the call fails

A response outside HTTP 200–299, a connection error, or a rejected URL fails the submission and skips the Contact Form 7 email. The visitor sees the form’s usual error message.

Turn on Show the API response body as the form message to show a JSON message field, or a shortened copy of any other body.

The last call is saved on the form. Open DEBUG LOG on the API Integration tab. Authorization header values are not stored.

Good to know

• Credentials are stored in the form. Anyone who can edit the form can read them.
• Keep one copy of the plugin active. WordPress.org installs it in cf7-to-api-basic-auth . A GitHub checkout uses cf7-to-api . Version 1.5.0 and newer skip loading when another copy is already active. Delete the extra folder.