Using RecordSeek with FamilySearch

J. Britt Franklin

We have tried using RecordSeek with Chrome and Edge but when we try to create a record to update something in FamilySearch we get an authentication error and the process halts. Is there some kind of prohibition about using RecordSeek to update records in FamilySearch?

Thanks!

MandyShaw1

@J. Britt Franklin this Community can't help with 3rd party products, you will need to contact RecordSeek support, sorry.

Áine.ní.Donnghaile

The creator of RecordSeek does not always keep his security up to date, causing the product to fail. As Mandy says, you'll need to contact RecordSeek.

DavidNCraig

@J. Britt Franklin

I experienced the same problem yesterday on Firefox. Clear your cache, restart your computer and FS and Recordseek will handshake and renew with each other. I don't believe Recordseek is currently working on Chrome. Don't know current state of Recordseek on Edge.

DavidNCraig

I am now experiencing the same problem. Something has changed at FamilySearch. Very disappointing.

From a Google Search-

RecordSeek may experience issues with FamilySearch

due to changes in FamilySearch’s API, updated usage agreements, or technical changes in how FamilySearch handles record permissions and security. As a third-party tool, RecordSeek relies on

FamilySearch's infrastructure

remaining consistent.

Áine.ní.Donnghaile

As has been said before, the responsibility lies with the third-party product. If something changes at FamilySearch, RecordSeek has to adapt, and users need to contact RecordSeek.

MandyShaw1

RecordSeek is not listed on the Solutions Gallery so probably does not have current formal agreement/support to use the FamilySearch APIs to do its source attaches.

Otherwise it will presumably be making use of web page content direct, invisibly to FS, and will therefore be dependent on the structure of that content not changing (something which obviously happens regularly as FS enhances the site, fixes bugs, personalises content by geographical region/LDS or not/Lab enrolment, etc.) This sort of activity is always liable either to fail or, worst case, to update FS data in unexpected ways (data corruption).

Either way this is not a FS problem and is a good example of why tools that change other sites' data without using supported APIs in a fully approved manner are a Bad Idea. (See also BYU RLL.)

Amy Archibald

RecordSeek hasn't been updated since before the pandemic. You can try to reach out to the creator through this website. https://recordseek.com/ or this website: https://dovy.io/

MandyShaw1

https://community.familysearch.org/en/discussion/comment/625563#Comment_625563

The developer posted on Facebook in 2019 that 'RecordSeek is now using the new FamilySearch APIs'. If the code has not been updated since, this API usage is not likely to still be working correctly in 2026, given that the APIs' authentication methods have been tightened up very considerably since then (not to mention that API usage is now supposed to be tightly controlled via a formal approval process). Since that 2019 post the only Facebook activity is from concerned users. There are no tweets post 2018 either. I would therefore honestly suggest not wasting time on this tool.

cody85749

Yes — this is very likely a limitation, not just your browser issue.

There’s no official “ban” message shown, but in practice:

• FamilySearch does NOT support RecordSeek as an integrated tool
• RecordSeek is a third-party tool, so any authentication or API changes on FamilySearch can break it
• FamilySearch uses OAuth-based authentication with access tokens for apps
  → If RecordSeek isn’t updated to match that flow, you’ll get authentication errors

What’s likely happening

• RecordSeek is trying to write/update data (create records)
• FamilySearch requires proper authorized API access
• If the token/auth flow fails → process stops (exactly what you’re seeing)

Key point

👉 RecordSeek may still work for reading/searching, but
👉 Updating or attaching records is unreliable or blocked due to authentication + lack of official support

What you can do

• Use FamilySearch’s built-in tools to add/edit records (most reliable)
• Try:
  • Logging out/in again
  • Clearing cookies/cache
  • Reinstalling RecordSeek
    (basic fixes sometimes help, but not guaranteed)
• If needed, contact RecordSeek developer (not FamilySearch)

Bottom line

This isn’t just your setup — it’s a known compatibility gap between RecordSeek and FamilySearch, especially for actions that require authentication (like updating records).