Troubleshooting: MCP & API Access

🔌 Search Atlas API: Audit Data Endpoint Reference

🔧 Troubleshooting Cloudflare Token Paste Errors in Search Atlas

This article helps you resolve the error that appears when you paste a Cloudflare API token into Search Atlas. The error is almost always caused by one of a few specific token configuration issues — this guide walks you through each one so you can identify and fix the exact cause. 🔍 Common Causes - Incorrect token permissions: The token was created without the required permissions for Search Atlas to connect. - Token scope too narrow: The token is scoped to a specific zone (domain) but Search Atlas requires access to all zones, or vice versa. - Extra whitespace: Copying the token from Cloudflare sometimes includes a leading or trailing space, which causes the validation to fail silently. - Token was created as a Global API Key instead of an API Token: Search Atlas requires an API Token, not the Global API Key. - Token has been revoked or expired: A previously working token may have been deleted or expired in Cloudflare. 🛠️ Step-by-Step 1. Log in to your Cloudflare dashboard at dash.cloudflare.com and go to My Profile → API Tokens. 2. Verify you are using an API Token, not the Global API Key. The Global API Key will not work. If you used the Global API Key, you must create a new API Token instead. 3. Check the token's permissions. The token must include at minimum: Zone → DNS → Edit and Zone → Zone → Read. Read-only DNS access is not enough because OTTO writes DNS settings (it enables DNS proxy on DNS-only records). If these permissions are missing, click Edit on the token, add the missing permissions, and save. 4. Check the token's Zone Resources scope. Set it to All zones unless Search Atlas documentation specifies a single-zone scope. Mismatched scope is a frequent cause of this error. 5. Regenerate the token if you are unsure of its current state. In Cloudflare, click Roll (or delete and recreate it) to get a fresh token value. 6. Copy the new token carefully. Click the copy icon in Cloudflare rather than selecting the text manually. This reduces the risk of copying extra whitespace characters. 7. Paste the token into Search Atlas by opening your project settings and navigating to the Cloudflare integration field. Before saving, click inside the field and press Ctrl+A (or Cmd+A on Mac) to select all, then paste — this replaces any previous value fully rather than appending. 8. Save the token and wait for the connection validation to complete. ✅ How to Confirm It Worked After saving, Search Atlas will attempt to validate the token immediately. You will know the connection succeeded when: - The error message disappears and is replaced by a green success indicator or a confirmation message such as "Token connected" or "Cloudflare connected successfully." - Your Cloudflare zones or domain data become visible within the integration area — if zones were not populating before, they should now appear in a dropdown or list. - No red error banner is shown after saving. If the red error persists even after following all steps, the token value itself is the issue — return to Cloudflare and create a brand-new token from scratch rather than reusing the same one. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Search Atlas REST API Authentication and Error Fixes

Overview The Search Atlas REST API requires proper authentication before making API calls. Understanding how to obtain and use the correct credentials is essential to successfully integrating with the API. This article covers how to authenticate with the Search Atlas API and how to resolve common API errors related to credential configuration. Part 1 — Authenticating with the Search Atlas REST API The Search Atlas REST API uses a token-based authentication system. To make authenticated API requests, you must first obtain an access token using your Search Atlas account credentials. What credentials are required? - username — your Search Atlas account email address (the same one you use to log in to app.searchatlas.com) - password — your Search Atlas account password These are the same credentials you use to log in to the main platform. Once you have obtained your access token, include it in the headers of subsequent API requests as a Bearer token. Important notes: - Access tokens are time-limited. If you receive an authentication error mid-session, re-request a fresh token and retry your request. - Make sure you are using your Search Atlas login credentials, not a separate API key, when requesting an access token from the token endpoint. - Avoid hardcoding credentials directly in shared scripts. Use a secure credential storage method appropriate for your integration environment. Part 2 — Fixing Common API Authentication Errors If you are receiving authentication or configuration errors when calling the Search Atlas API, the most common causes are: 1. Wrong credential type — Using the wrong value (for example, passing a login password where an API key is expected, or vice versa). Confirm which credential type each endpoint requires before making calls. 2. Incorrect or malformed credential — The credential was copied with extra whitespace, a missing character, or from an outdated or revoked source. Copy your credentials carefully from your Search Atlas account settings. 3. Credential not yet generated — If you have not yet created an API key or token in your account, the relevant endpoint will reject your request. Check your account settings to confirm your credentials exist and are active. 4. Incorrect endpoint URL — Requests sent to a wrong or mistyped endpoint path will return errors. Double-check the endpoint URLs against the official Search Atlas API documentation. If you are unsure which credentials or endpoint configuration apply to your specific use case, gather the following before escalating: the endpoint URL you are calling, the exact error message or response code you are receiving, and the credential type you are passing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ GHL API Keys Page Branding Fix

A branding inconsistency in the API Keys page has been resolved for GoHighLevel (GHL) users. The SearchAtlas name was incorrectly appearing in description text on that page, and it has now been corrected to reflect the proper white-label branding. ✨ What's New The API Keys page description text in GHL environments was displaying SearchAtlas branding instead of the expected white-label branding. This fix ensures that the platform identity remains consistent and fully white-labeled throughout the GHL experience, including the API Keys section. 📋 What to Expect GHL users will no longer see any SearchAtlas branding references within the API Keys page description text. All other areas of the platform that rely on white-label branding are unaffected by this change. No action is required on your part — the update is applied automatically. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Cloudflare Worker API Token Validation Failures

Overview API token validation errors in the SearchAtlas Cloudflare Worker typically trace back to one of two root causes: the Worker script was not deployed correctly, or the API token is missing the required permissions. This article explains what to check and what information to have ready so our team can resolve the issue quickly. Step 1: Confirm You Have the Correct Worker Script Before troubleshooting token validation, confirm you are using the official SearchAtlas Worker script — not a generic Cloudflare template or an outdated version from a previous installation. - Log in to your SearchAtlas account and locate the Cloudflare Worker integration section to retrieve the current Worker script. If you are unsure where to find this in your account, our support team can point you to the exact location. - Do not use a script obtained from a third-party source or one that predates your current SearchAtlas account, as a mismatched script is a common reason token validation fails. Step 2: Deploy the Script in Cloudflare Once you have the correct SearchAtlas Worker script, deploy it through your Cloudflare dashboard. Replace any existing Worker code with the latest SearchAtlas script in full, then save and redeploy. Running an outdated script version can cause token validation to fail even if your token permissions are otherwise correct. After deploying, note the Worker's URL — you will need it when configuring the integration in SearchAtlas. Step 3: Review Your Cloudflare API Token Permissions Cloudflare API tokens are permission-scoped. A token that lacks the required permissions will fail SearchAtlas validation. When creating or reviewing your token in the Cloudflare dashboard, ensure it includes the permissions necessary for Cloudflare Worker script deployment and API token validation as required by the SearchAtlas integration. If you are unsure which permissions are needed, or if the token continues to fail validation after reviewing your setup, our support team can assist you directly. What to Have Ready When Contacting Support If you are unable to resolve the validation failure on your own, please have the following information ready before reaching out: - Your SearchAtlas project name - The exact error message you are seeing during token validation - A timestamp of when the error first occurred - A brief description of any changes made to your Worker script or API token before the issue began If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Cloudflare API Token Permissions for Clearview

🌐 Overview Connecting Clearview to your Cloudflare account requires a Cloudflare API token with specific permissions. A common issue customers encounter is searching for a Workers Routes permission that no longer exists in the current Cloudflare dashboard. This article explains exactly which permissions to select and how to create the token correctly using the updated Cloudflare UI. ⚠️ Common Mistake: Workers Routes Permission Older versions of the Clearview integration guide referenced a Workers Routes permission inside Cloudflare's token creation screen. Cloudflare has since redesigned their token creation interface, and this permission label no longer appears. If you have been searching for it, that is why the setup has been failing. You do not need a Workers Routes permission — follow the steps below to configure the correct permissions. ✅ Required API Token Permissions When creating your Cloudflare API token for the Clearview integration, you must include the following permissions: - Zone — DNS — Edit: Allows Clearview to read and update DNS records on your domain. - Zone — Zone — Read: Allows Clearview to identify and access your Cloudflare zone (domain). These two permissions are sufficient for the integration to function. Do not add unnecessary permissions, as this can cause authorisation errors. 🛠️ How to Create the API Token 1. Log in to your Cloudflare dashboard at dash.cloudflare.com. 2. Click your profile icon in the top-right corner and select My Profile. 3. Navigate to the API Tokens tab on the left sidebar. 4. Click Create Token. 5. Scroll down and select Create Custom Token by clicking Get started. 6. Give your token a recognisable name, such as Clearview Integration. 7. Under Permissions, add the following two permission rows: - Row 1: Select Zone — DNS — Edit - Row 2: Click Add more, then select Zone — Zone — Read 8. Under Zone Resources, set the scope to Include — Specific zone and select the domain you are connecting to Clearview. 9. Click Continue to summary, review the permissions, then click Create Token. 10. Copy the token immediately — Cloudflare will only show it once. 🔗 How to Enter the Token in Search Atlas 1. Open the Search Atlas platform and navigate to the Clearview integration settings. 2. Paste your Cloudflare API token into the designated field. 3. Click Connect or Save to complete the integration. 4. Wait a few moments for the connection to verify. A green confirmation indicator means the integration is active. 🚨 Troubleshooting: Authorisation Failed (cf_10000) If you see an error message referencing Cloudflare API Authorization failed or error code cf_10000, this usually means one of the following: - The token was created with missing or incorrect permissions — recreate it using the steps above. - The token was scoped to the wrong zone — ensure the correct domain is selected under Zone Resources. - The token was not copied in full — return to Cloudflare, revoke the old token, and generate a new one. After fixing the token, return to the Clearview integration settings in Search Atlas, remove the old token, paste the new one, and reconnect. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix API 404 Errors Fetching Published Content

🔍 Overview If you are calling the Search Atlas API to retrieve published content and receiving a 404 error, you are not alone. This error can appear even when your published articles are clearly visible inside the Search Atlas platform. This article explains what to have ready when escalating this issue to our support team. ⚙️ What This Error Means A 404 response when retrieving published content via the Search Atlas API indicates that the server could not locate the requested resource at the time of the call. Because the root cause requires investigation on the backend, our support team will need to look into your specific account and request details to identify what went wrong. 🚀 What to Do This issue requires backend investigation by our support team. To help us resolve it as quickly as possible, please have the following information ready before reaching out: - The exact API endpoint URL you are calling, copied directly from your integration or logs. - The full error response you are receiving, including any response body or headers. - The name of the workspace or project where the published content is located. - The timestamp of when the 404 error occurred (date and time, including timezone). - Confirmation of the content status — whether the affected content is confirmed as fully published inside the platform at the time of the error. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix Twitter/X OAuth Integration Login Loop

🔍 Overview Some users experience a login loop when attempting to connect their Twitter/X account in Search Atlas. Instead of completing the connection, the platform repeatedly redirects to a sign-in page even when you are already logged in to Twitter/X. This issue requires investigation and resolution by our support team directly on your account. ⚠️ What This Looks Like - You click the option to connect your Twitter/X account. - You are redirected to a Twitter/X sign-in or authorization page. - After signing in (or if you are already signed in), the page loops back and requests sign-in again. - The account never successfully links and you cannot proceed. ✅ Steps to Resolve 1. Contact our support team and describe the loop you are experiencing. Because this issue requires back-end investigation on your specific account, reach out to our support team so they can examine the OAuth connection directly and get your Twitter/X account linked. To contact support, email us or use the messaging option available on our website. 2. Provide your account details when you reach out. Share the email address associated with your Search Atlas account and confirm which Twitter/X account you are trying to connect. This allows the team to locate your account and investigate the OAuth issue promptly. 3. Our team will investigate and resolve the OAuth connection on your behalf. Once the team has reviewed the back-end state of your account's Twitter/X integration, they will apply the necessary fix and confirm when your account has been successfully linked. 💡 While You Wait - Make sure you are fully logged in to your Twitter/X account in your browser, as an active session may assist the team's investigation. - Do not attempt to disconnect or reconnect the account repeatedly, as this may complicate the back-end state our team needs to review. 🆘 Still Experiencing the Loop? If your Twitter/X connection loop is still occurring after contacting us, please reply to your existing support conversation so we can continue investigating. You can also reach our support team by emailing us or using the messaging option on our website.