Skip to main content
GET /autocomplete is being replaced by a new Autocomplete API and stops working on Friday, September 25, 2026. This is a breaking change: the URL, the request parameters and the response body all change. The replacement is a dedicated typeahead service rather than a single lookup call. Your backend mints a short-lived session, the browser queries it on each keystroke, and picking a suggestion hands you a token you feed straight into a search — so your API key never reaches the client and the search runs against exactly the business the user chose.

​
What changes in the URL and the request

One call becomes two. Your backend calls POST /autocomplete/sessions with your existing API key to mint a short-lived session, and the browser then calls GET /autocomplete/businesses on each keystroke, passing that session in an X-Autocomplete-Session header. Rather than repeat it all here, sdk.baselayer.com documents the full request flow.

​
What changes in the response

Each suggestion now describes a canonical business rather than a single registration, and carries its officers, registered agents, addresses and liens, which you can also filter on. The response now contains a suggestions[].token, bound to your organization, valid for 15 minutes, and redeemable only as business_token on POST /searches. Pass it there to run the search against exactly that business and complete your KYB.

​
An SDK to speed up the integration

You do not have to wire the session flow up by hand. We publish a JavaScript/TypeScript SDK that mints the session, refreshes it before it expires, re-mints and retries when one lapses or a rate limit is hit, and gives you a ready-made typeahead component — see sdk.baselayer.com. For most integrations it is the fastest path off the old route, and it keeps you on the right side of the session rules without you having to track them. Contact your Baselayer representative if you are interested in a demo.