Product Updates
Documentation
Dashboard

Have something to share?

Tell us how we can make Pica more useful to you. We welcome your insights, suggestions, feedback, and integration requests to help us continually improve the platform.

AuthKit bug

Hi Pica Support Team, I'm integrating AuthKit into a Next.js App Router project and discovered a critical bug in the @picahq/authkit-token npm package (I am using the latest version). The AuthKitToken.create() method is not generating a token string. Instead, it is returning a paginated JSON response containing my workspace's available integrations, which silently breaks the frontend useAuthKit React component because it fails to receive a valid token string. I inspected the compiled source code of the SDK inside node_modules/@picahq/authkit-token/dist/src/apis/link.api.jsand found the root cause: The createEventLinkTokenApi function makes a POST request to /v1/authkit (which seems to be the endpoint to fetch configured workspace integrations) instead of an endpoint to mint a new token. It even paginates the response and returns an array called rows. javascript // From your node_modules/@picahq/authkit-token/dist/src/apis/link.api.js const fetchAuthkitPage = async (page, pageLimit) => { // BUG: This endpoint returns a list of configured apps, not a token const response = await axios_1.default.post(`${url}/v1/authkit?limit=${pageLimit}&page=${page}`, payload || {}, { headers }); return response.data; }; Workaround Used: We have bypassed the npm package entirely and are successfully generating tokens using a manual fetch to https://api.picaos.com/v1/authkit/tokens, which works perfectly and correctly returns the { token: "..." } payload. Could you please have the engineering team update the Node.js SDK to hit the correct token generation endpoint (/v1/authkit/tokens) instead of the workspace config endpoint? Thank you,

News Feed 18 days ago

2
🐛

Bug Reports

Support non-restricted Gmail scopes in AuthKit (readonly, send, modify)

I want to be able to configure AuthKit's Gmail connection to use non-restricted scopes (like gmail.readonly, gmail.send, and gmail.modify) instead of the restricted 'mail.google.com' scope. This is important because the restricted scope triggers Google's verification process immediately, which I want to avoid for applications that only need to read, respond, or flag mail as read. I'm requesting the extension of the Gmail authkit spec to optionally include these items if the overarching gmail spec is de-selected.

Tan Custard About 2 months ago

💡

Feature Requests

Intergration request - Ring Central

Hey Team. Connectors for VoIP systems, such as Ring Central would be great. Specifically to access historical call data (meta data and call recordings) for analysis purposes. A bonus would be ability to query current wait times, read phone line data (ie phone lines and who they’re assign to) and really huge win would be the ability to redirect calls via the integration (ie divert calls to specific numbers for certain conditions, ie after hours). Ring Central seems to be the main VoIP platform in the US, but AirCall and others would also be great to be able to connect to. Thank you.

eddie-caeluslabs About 2 months ago

🔗

Integrations