How do I test Pre.Fill and Auto.Complete, and how are they billed?

Last updated: October 9, 2026

Testing.

  • Pre.Fill in sandbox returns a fixed sample response regardless of the name you submit, so you can build against the response shape without hitting real records. Use production to see real results for a specific person.

  • Auto.Complete works in sandbox from October 8, 2026: open a session with your sandbox API key and the typeahead behaves exactly as it does in production. Sandbox suggestions come only from Baselayer's sandbox test businesses (listed in the Integration Test Cases spreadsheet), not from live registrations, so type the name of a test business to see suggestions.

  • A business_token only works in the environment it came from: a token picked in sandbox can be used on a sandbox business search, and a production token only in production.

  • In the console, the business typeahead is also available when a sandbox application is selected.

  • The live demo at sdk.baselayer.com shows the experience before you integrate. More on sandbox: Sandbox vs. Production.

Billing.

  • Pre.Fill is billed per request, regardless of how many registrations are returned. It is available on contracted plans and not on self-serve plans; if you get an access error, contact your account team to have it enabled.

  • Auto.Complete is billed per session, which can include multiple actions from the user. It is enabled per organization; contact your account team to turn it on.

  • Sandbox Auto.Complete sessions are not billed and do not count toward your organization's usage limits.

  • The business search you run on the confirmed entity is billed as usual.

Both respond in real time, so they can sit directly in an applicant-facing form without a loading state beyond the usual typeahead delay.