Access token / app mismatch" on PATCH/PUT requests

Get Help
1

Hi everyone,

I’m hitting a persistent issue with the Adalo Collections API and my “App API Key” (from Settings > Integrations).

Problem My Cloud Function successfully obtains data (e.g., from Stripe) but fails to update Adalo collection records using PATCH/PUT requests. The Adalo API consistently returns: { "error": "Access token / app mismatch" } or Error: Failed to update Adalo: Unauthorized.

What I’ve done/checked:

-API Key:Regenerated the App API Key multiple times.
-App/Collection IDs:Confirmed ADALO_APP_ID and ADALO_COLLECTION_ID are correct and being sent.
-API Names:Verified exact API Names for all fields (Stripe Account ID, Charges Enabled, Payouts Enabled, etc.).
-Request Type: Occurs on both PATCH/PUT. Even simple GET requests to the same collection (to verify records) return Unauthorized.
-Cloud Function: Logs confirm the correct API key, App ID, and payload are being sent. The function itself is working (e.g., exchanging tokens with Stripe).
-Record Existence: Manually ensured the target Adalo record exists and is correctly linked (e.g., to the user).

My Question:

Does the “App API Key” (obtained from Settings > Integrations) inherently grant write (PATCH/PUT) access to collections? Or are there specific permissions, roles, or a different type of API key required for successful write operations via the Collections API?

Any insights or similar experiences would be greatly appreciated! Thanks in advance for your help.

2

Hi @jarodadam, I’m experiencing a very similar issue.

In my case, I get a 401 Unauthorized error when trying to update a many-to-many relationship using the standard Toggle component. The collections and relationship are correctly configured, but the write fails. I also tested this on a brand new collection and the issue persists.

Did you open a support ticket with Adalo about this? If so, I’d really appreciate if you could share any insights you receive.

Thanks!

3

Hi @jarodadam,

Adalo Collections API key is universal (unfortunately) and grants access to ALL collections with ALL permissions.

Just in case: are you on Team or other plan, which allows usage of Collections API?
If yes: did you try to send a request from Postman or using curl?

Best,
Victor.

4

Hey Kamil, honestly I’ve been unable to submit a support ticket on my end and have reached out via email and contacted Adalo team members through the forum here, along with email and have yet to hear back.

1 Like
5

@jarodadam this issue is typically related to an issue with the App/API Key or plan access so it would be unrelated to the issue Kamil is seeing. If you’re on the Team or Business plan and are still experiencing the error, it’s likely something crossed in the API setup. This is common when you have multiple apps sharing a database and something isn’t matching in the authentication.

We typically suggest testing in Postman to see if you can reproduce the issue and if so, send the API setup and App URL to the team so we can take a look.

I don’t see a ticket from you or any DM on my end but if you share that info in a Support Ticket we will be happy to take a look. Shoot me a DM once it’s completed, I will verify have received it and will troubleshoot it further.

-Jessi

7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.