Navigator API vs eSignature API

Hello there and welcome to the Docusign Community! Thanks for asking a very good question.

First, let me clarify that Navigator API is not a replacement for the eSignature API. Most work with envelopes still requires the use of the eSignature API.

At this time (Jan 2025) we only have two endpoints publicly available in the Navigator API, but we do anticipate adding more later in the year. 

Navigator and Navigator API are new products that provide AI-supported technologies to extract information from agreements (often agreements are stored in an envelope). However, these technologies do not replace eSignature and the eSignature API, they complement and enhance the eSignature product by Docusign.

As for creating accounts, you’re correct, that requires the Admin API and you should look at our two articles (And code examples) about how to clone and how to create an account.

Hope this helps, feel free to ask additional questions.

​@Inbar.Gazit does it mean i need to purchase different plan later? for navigator api and esignature api? 
my app is in rare care where we act as social hubs and user linking to multiple social accounts. we just wwant to be the bridge/middleware to connect people easily from different social platforms.

So we create market for docusign, and potentially bring thousand of customer as we will connect them and need some agreements later and I just want to throw all the PLAN to the users. since basically if they create envelope in our app, they also able to see their agreements/envelopes within docusign app or any app that integrated with docusign. so yeah user need to purchase docusign PLAN and not us. although our app still indeed need to purchase some plan, since we are still using docusign API for specific case directly to customer but this case make me confuse to integrate it properly whether using admin api, navigator api, esignature api