> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Your Internal Apps Starter Kit > Explore Docusign API capabilities and ISV Embed program features, create your proof of concept, and accelerate your ISV embed solution development. # Your Internal Apps Starter Kit ## Kit Contents ### Get Started Use the tools and resources in this kit to explore API features, learn how to call API endpoints for the functions you need, and get started building your own integrations. ### Contents #### [Postman Collections](/tools/postman) Explore the Docusign APIs by downloading the Postman collections. #### [Quickstart](/docs/esign-rest-api/quickstart) Download a personalized project in the programming language of your choice configured with your developer account settings. #### [API Reference and Explorer](/docs/esign-rest-api/reference/accounts/accounts/get) Browse the API Reference while logged in to your developer account and select “API Explorer” to try out your chosen endpoint. #### [Sample App](https://government.sampleapps.docusign.com) Try the MyGovernment sample app to explore common APIs, and download the source code to reuse in your apps. Follow these steps to launch your own Internal Application project. 1. **Sign up for a developer account** If you haven’t already got one, sign up for your FREE [developer account](https://www.docusign.com/developers/sandbox?postActivateUrl=https://developers.docusign.com/&_gl=1*1d3gman*_gcl_au*ODczOTUxNTUwLjE3MjcyOTgwNDc.). The developer account gives you full access to build and test your integrations in our developer environment. 2. **Read Platform 101 Overview documentation** To plan your integration, make sure you read the [Platform 101](/platform) documentation. Get familiarized with Docusign terminology by reading the [glossary](/platform/glossary) 3. **Get your API credentials for the developer environment** To make an API call, you will need to get your API credentials (clientID and secret) from the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page. 4. **Choose your authentication method** Based on your use case, choose from one of the four [authentication methods](/platform/auth): * Confidential Authorization Code Grant is generally used for user-present scenarios with a secure server running. * Public Authorization Code Grant, which uses Public Key Code Exchange (PKCE) to grant a token without needing to store a client secret. * JSON Web Token (JWT) Grant is generally used in system integrations where the user is not present. * Implicit Grant is generally used in single-page and mobile applications. A more secure alternative to Implicit Grant is Public Authorization Code Grant. 5. **Get your base URI and account information for making API calls** Use the [userInfo endpoint](/platform/auth/reference/user-info) to get the base URI and user account information your app needs in order to access Docusign APIs. The userInfo endpoint is accessed through the Docusign authentication service, which resides on a different subdomain than the core API service: * **** for the developer environment * **** for the live production system For the eSignature REST API, the base URI is: * **** for the developer environment * **https\://\{server}.docusign.net/restapi** for the production environment, where \{server} depends on the location in which your production account is administered. 6. **Make your first API call** Use one of the tools listed in this Get Started Kit to make your first API call. The most popular first API call is to [create an envelope](/docs/esign-rest-api/reference/envelopes/envelopes/create) from our eSignature API, which is used to request signatures. 7. **Explore these additional capabilities** Continue to build on your proof of concept by adding some important additional capabilities. Note: some of these capabilities may require purchase of specific plans for use in production. See [pricing](/docs/esign-rest-api/reference/envelopes/envelopes/create) or [contact sales](https://www.docusign.com/contact-sales). Popular capabilities: * [Create Template](/docs/esign-rest-api/how-to/create-template) * [Create Tabs](/docs/esign-rest-api/esign101/concepts/tabs) (data fields) * [Embedded Sending](/docs/esign-rest-api/how-to/embedded-sending) * [Embedded Signing](/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing) * [Envelope corrections](/docs/esign-rest-api/reference/envelopes/envelopeviews/createcorrect) * [Void Envelopes](/docs/esign-rest-api/reference/envelopes/envelopes/update) * [Event Notification aka Connect Webhooks](/docs/esign-rest-api/reference/connect) Advanced Docusign capabilities compatible with your API integration. (Check plans and pricing) * [SMS and WhatsApp delivery](/docs/esign-rest-api/esign101/concepts/sms-delivery) * [Web Forms](https://www.docusign.com/products/web-forms) * [ID Verification](https://www.docusign.com/blog/how-does-online-id-verification-work) * [Extension Apps](https://apps.docusign.com/app-center) * [Workflow Builder workflows](https://www.docusign.com/products/platform/workflow-builder) Check out our [How-to guides](/docs/esign-rest-api/how-to) for a comprehensive list of capabilities. 8. **Troubleshoot common errors** Diagnose and fix your most common development issues with our guide to [common error messages](/docs/esign-rest-api/esign101/error-codes/troubleshooting-common-errors). 9. **Get pricing** By default, the free developer account includes some enterprise features. Before you go live on production, make sure that you have also purchased a plan that includes features that you need in the production environment. Check [Choose the right developer plan](/choose-the-right-developer-plan) to see which best fits your business model. 10. **Submit for review** Once you have completed your API integration, you can submit your integration for review to go-live in production. Learn more about how to Go-live from our [documentation](/platform/go-live) and [Videos](https://www.youtube.com/watch?v=Fm7L91P-p5Q\&list=PLXpRTgmbu4ooU4l_mlYWvWtoSSkDHJKuo). 11. **Ask the community** If you run into issues, ask the [Docusign Developer Community](https://community.docusign.com/developer-59) or check [Docusign Community](https://stackoverflow.com/questions/tagged/docusignapi). You can also join the [API Office Hours](/developer-events) for a demo and live Q and A for additional information. 12. **Manage your API usage** Last but not the least, manage your integration using the [API Usage Center](/tools/api-usage-center). Has this Starter Kit been helpful? Let us know what you think! Take our quick [survey](https://docusign.co1.qualtrics.com/jfe/form/SV_0lDgnZEACCwuDBk)