Hey! Trying to set up BotID between multiple project, both hosted on Vercel.
There’s a nextjs app router project and a POST /v1/contact endpoint and setting up BotID here works great.
But the other project is an older frontend only Gatsby site, which uses the same endpoint, but always fails with isBot: true. Tried to debug with all the AI in the world, so I’m pretty confident that the setup is correct. Here are the details:
Gatsby site has the necessary rewrites and headers in vercel.json, then in gatsby-browser.js I have this script:
import { initBotId } from 'botid/client/core'
export const onInitialClientRender = () => {
initBotId({
protect: [
{
path: '/v1/contact',
method: 'POST',
},
],
})
}
It seems to work fine, I see the request for the botid js file and the x-is-human header gets attached. Logging out the x-is-human, x-path and x-method - they all seem correct.
On the server side I have withBotId in the next config and this code in the handler:
const verification = await checkBotId({
advancedOptions: {
extraAllowedHosts: ["olddomain.com", "www.olddomain.com"],
},
});
And again, submitting to this exact endpoint from next frontend works.
Tried to change extraAllowedHosts to add / remove the www version, add / remove https version, every combination, but nothing seems to work. And there’s no reason or explanation what might be wrong. Here’s the verification logged out:
verification: {
isHuman: false,
isBot: true,
isVerifiedBot: false,
verifiedBotName: undefined,
verifiedBotCategory: undefined,
bypassed: false,
classificationReason: undefined
}
Any idea what might be wrong?
