# Figma API updates broke the Figma social connection in Auth0

**URL:** <https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121>\
**Category:** Get Help\
**Tags:** other-built-in-social-connections, connections\
**Created:** [October 13, 2025, 11:14am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121 "2025-10-13T11:14:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dev73](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dev73/32/70868_2.png) [@dev73](https://community.auth0.com/u/dev73)\
**Post date:** [October 13, 2025, 11:14am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121/1 "2025-10-13T11:14:05Z")

</div>

Due to updates in the Figma authentication flow, the current Figma social connection in Auth0 seems broken.

Due to changes in Figma’s API, the files:read scope is not available anymore for new OAuth apps in Figma. Since the current Figma connection in Auth0 defaults to this permission, the following error is raised during a login:

{“error”:true,“status”:400,“message”:“Invalid scopes for app”,“i18n”:null}

Will the Figma social connection be updated in Auth0 to support the new scopes?

Additionally, is there a way to manage the scopes for the current Figma social connection in Auth0, so we can fix our current broken state?

Thanks!

---

<div class="post-metadata">

**Author:** ![teodor.andrei](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/teodor.andrei/32/75320_2.png) [@teodor.andrei](https://community.auth0.com/u/teodor.andrei)\
**Post date:** [October 14, 2025, 9:23am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121/3 "2025-10-14T09:23:34Z")

</div>

Hi @dev73 and welcome to the Auth0 Community!

I will investigate this issue and get back to you as soon as possible.

In the meantime, as a workaround, you can set up a custom OAuth 2.0 connection to Figma, by following this guide: [Connect Apps to Generic OAuth2 Authorization Servers](https://auth0.com/docs/authenticate/identity-providers/social-identity-providers/oauth2)  
This way you’ll have control over all integration parameters.

Kind regards,  
Teodor.

---

<div class="post-metadata">

**Author:** ![dev73](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dev73/32/70868_2.png) [@dev73](https://community.auth0.com/u/dev73)\
**Post date:** [October 14, 2025, 10:18am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121/5 "2025-10-14T10:18:35Z")

</div>

Thanks Teodor!

In the meantime we found a solution by updating the default scope of the Figma Social connection through the management API.

Replacing the default **file\_read** scope with valid ones seems to resolve the issue.

---

<div class="post-metadata">

**Author:** ![teodor.andrei](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/teodor.andrei/32/75320_2.png) [@teodor.andrei](https://community.auth0.com/u/teodor.andrei)\
**Post date:** [October 14, 2025, 10:50am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121/6 "2025-10-14T10:50:46Z")

</div>

Hi @dev73 !

That’s good to hear! Is there anything else I can help you with regarding this topic?

Kind regards,  
Teodor.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [October 28, 2025, 10:51am UTC](https://community.auth0.com/t/figma-api-updates-broke-the-figma-social-connection-in-auth0/193121/7 "2025-10-28T10:51:23Z")

</div>

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