# Mautic 4.4 API call failures with Fluent Forms

**URL:** <https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224>\
**Category:** Product Support\
**Created:** [August 30, 2022, 5:48am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224 "2022-08-30T05:48:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![roblefko](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/roblefko/32/4958_2.png) [@roblefko](https://forum.mautic.org/u/roblefko)\
**Post date:** [August 30, 2022, 5:48am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224/1 "2022-08-30T05:48:53Z")

</div>

**Your software**  
My Mautic version is:4.4.0  
My PHP version is:7.4.3  
My Database type and version is:10.3.34-MariaDB

**Your problem**  
My problem is: I’ve been using Fluent Forms for a while, which uses the api to import my contact information from its form data from Wordpress to Mautic. This was working well until I upgraded to Mautic 4.4.0. As soon as I upgraded, the calls to the api started failing. Fluent Forms doesn’t say anything more than that the call failed. If I go back to calling Mautic 4.2.2 (I never installed Mautic 4.3), the api calls work successfully, so the change causing the problem must have been on the Mautic side. I know that it’s not something stupid, like an authentiction failure, because most of my data appears to be getting transferred, despite the failure message.

1. Is this a known issue?
2. Where can I find more details about the nature of the failure? Is there a log of this?

These errors are showing in the log:

Steps I have tried to fix the problem: I’ve tested against older Mautic versions, and confirmed that the contact information is transferred properly.

---

<div class="post-metadata">

**Author:** ![roblefko](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/roblefko/32/4958_2.png) [@roblefko](https://forum.mautic.org/u/roblefko)\
**Post date:** [January 5, 2023, 6:33am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224/2 "2023-01-05T06:33:20Z")

</div>

The good news: This was fixed in v4.4.2  
The bad news: It is broken again in 4.4.5.

Not sure when it broke, but the current version doesn’t work.

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [January 5, 2023, 7:11am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224/3 "2023-01-05T07:11:32Z")

</div>

It would make sense to check the release notes and try to figure out what could cause the issue.

> **[Releases · mautic/mautic](https://github.com/mautic/mautic/releases)**
>
> Mautic: Open Source Marketing Automation Software. - mautic/mautic

Which call fails? Creating contact?

---

<div class="post-metadata">

**Author:** ![roblefko](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/roblefko/32/4958_2.png) [@roblefko](https://forum.mautic.org/u/roblefko)\
**Post date:** [January 5, 2023, 7:23am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224/4 "2023-01-05T07:23:38Z")

</div>

Yes, it’s the call to create a new contact.

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [January 5, 2023, 7:32am UTC](https://forum.mautic.org/t/mautic-4-4-api-call-failures-with-fluent-forms/25224/5 "2023-01-05T07:32:11Z")

</div>

No idea. Maybe this?

> <https://github.com/mautic/mautic/pull/11420>
>
> \<!-- ## Which branch should I use for my PR?
> 
> Assuming that:
> 
> a = current ma…jor release
> b = current minor release
> c = future major release
> 
> \* a.x for any features and enhancements (e.g. 5.x)
> \* a.b for any bug fixes (e.g. 4.4, 5.1)
> \* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) --\>
> 
> | Q | A
> | -------------------------------------- | ---
> | Bug fix? (use the a.b branch) | \[y\]
> | New feature/enhancement? (use the a.x branch) | \[n\]
> | Deprecations? | \[n\]
> | BC breaks? (use the c.x branch) | \[n\]
> | Automated tests included? | \[y\] 
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes https://github.com/mautic/mautic/issues/10568
> 
> \#### Description:
> 
> This PR solves the issue that after the API was enabled in UI the cache had to be cleared to actually make the API routes working. It's very annoying and every new Mautic user must search for the solution. We had a great discussion about this at @biozshock PR https://github.com/mautic/mautic/pull/11399 where you can read more details about reasoning for this change rather than the original change.
> 
> And I'd like to avoid merging \[this alert\](https://github.com/mautic/mautic/pull/11410) when we can solve the problem for good.
> 
> I measured the performance of having the API routes in the cache file or not but after \[the optimization Symfony released in version 4.1\](https://symfony.com/blog/new-in-symfony-4-1-fastest-php-router) I could not measure any difference. Here's the screenshot of the test with explanation what each of the requests mean. The response time was pretty much in the same range.
> 
> !\[Screen Shot 2022-08-30 at 10 06 01\](https://user-images.githubusercontent.com/1235442/187438431-eccb471a-8059-4744-b83a-e15bc17ddc0d.png)
> 
> 
> \#### Steps to test this PR:
> 
> \<!--
> This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
> \--\>
> 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester))
> 2. Enable the API and Basic Auth
> 3. Use your favorite API tester like https://www.postman.com to access some API endpoint. For example \`GET https://your-mautic/api/contacts\`.
> 
> Before the change you get an error that the route does not exist. You'd have to clear the cache to make it work. After the change this works without the need to clear the cache.
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>