# Documents & Contracts: Public APIs > Learn how to use Documents & Contracts Public APIs in GHL Customer Care to list documents, send existing files, retrieve templates, and automate document workflows. - Source: https://docs.ghlcustomercare.com/docs/documents-and-contracts/documents-and-contracts-2/documents-contracts-public-apis-155000007531 - Section: Documents & Contracts / Documents and Contracts - Reading time: 6 min - Images: 3, each explained below --- Automate document workflows in GHL Customer Care with Documents & Contracts Public APIs. These APIs let developers list documents, send existing documents to contacts, retrieve templates, and generate documents from templates without manual work. This makes it easier to sync records, trigger document delivery from external systems, and streamline contract-related processes inside GHL Customer Care. The feature is part of the broader Documents & Contracts experience in GHL Customer Care and is designed for programmatic use. --- **TABLE OF CONTENTS** - [What is Documents & Contracts: Public APIs?](#what-is-documents-and-contracts-public-apis) - [Key Benefits of Documents & Contracts: Public APIs](#key-benefits-of-documents-and-contracts-public-apis) - [List Documents](#list-documents) - [Send Document](#send-document) - [List Templates](#list-templates) - [Send Template](#send-template) - [How To Setup Documents & Contracts Public APIs](#how-to-setup-documents-and-contracts-public-apis) - [Frequently Asked Questions](#frequently-asked-questions)[](#related-articles) - [Related Articles](#related-articles) --- ## **What is Documents & Contracts: Public APIs?** Documents & Contracts Public APIs give developers a way to work with document assets in GHL Customer Care through API requests instead of manual actions in the app. They are useful when you need to connect GHL Customer Care with external systems, automate sending from your own workflows, or dynamically create documents from saved templates. These APIs are scoped to the relevant GHL Customer Care location and are best used when your process requires developer-led automation rather than a no-code workflow alone. Documents & Contracts Public APIs currently support core document workflow actions such as: - Listing documents in a location - Sending an existing document to one or more contacts - Listing templates in a location - Creating and sending a document from a template in a single request --- ## **Key Benefits of Documents & Contracts: Public APIs ** Documents & Contracts Public APIs help teams reduce manual effort and connect document operations to the rest of their tech stack. They are especially valuable for businesses that want tighter control over when documents are generated, sent, and followed up on. - **Automate document delivery**: Send documents from external tools, custom apps, or internal systems without manually opening GHL Customer Care. - **Use saved templates efficiently**: Generate new documents from existing templates in one API call to speed up repeatable processes. - **Keep document data in sync**: Retrieve document and template lists for reporting, system syncing, or operational visibility. - **Support scalable workflows**: Connect API-based sends with downstream workflow triggers for reminders, follow-ups, and status-based automation. - **Reduce manual errors**: Standardize how templates are selected and sent across teams, systems, or client-facing processes. --- ## **List Documents** Listing documents helps you retrieve available document records within a specific GHL Customer Care location. This is useful for integrations that need to sync document inventories, display available items in another system, or verify which assets already exist before triggering additional actions. You can use the **List Documents** endpoint to: - Retrieve documents available in a location - Support syncing between GHL Customer Care and an external system - Build internal tools that reference existing document records - Reduce duplicate creation by checking what already exists first ![List Documents (image 1 of 3)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155068515262/original/W6-WmKB31secM6433B3-w6qeRauKgJ4Y5A.png) **List Documents (image 1 of 3)** This screenshot appears in the "List Documents" section of "Documents & Contracts: Public APIs". The text alongside this image reads: Retrieve documents available in a location Support syncing between GHL Customer Care and an external system Build internal tools that reference existing document records Reduce duplicate creation by checking what already exists first. This part of the guide covers 1 field, listed below. Immediately after, the guide continues: Sending an existing document by API is helpful when a document has already been prepared in GHL Customer Care and only needs to be delivered to the right contact at the right time. This supports custom business logic, external application…. - What this covers: Retrieve documents available in a location Support syncing between GHL Customer Care and an external system Build internal tools that reference existing document records Reduce duplicate creation by checking what already exists first - Fields: Retrieve documents available in a location - Controls: List Documents - Next: Sending an existing document by API is helpful when a document has already been prepared in GHL Customer Care and only needs to be delivered to the right contact at the right time. This supports custom business logic, external application triggers, and developer-driven automation beyond standard workflow actions. Full procedure: 1. Retrieve documents available in a location 2. Support syncing between GHL Customer Care and an external system 3. Build internal tools that reference existing document records 4. Reduce duplicate creation by checking what already exists first --- ## **Send Document** Sending an existing document by API is helpful when a document has already been prepared in GHL Customer Care and only needs to be delivered to the right contact at the right time. This supports custom business logic, external application triggers, and developer-driven automation beyond standard workflow actions. You can use the **Send Document** endpoint to: - Send a prebuilt document to a contact - Trigger document delivery from an external form, portal, or app - Standardize document sends across custom workflows - Reduce manual handoff steps for sales or onboarding teams Keep in mind: - The document must already exist in GHL Customer Care before it can be sent - Recipient behavior should follow the capabilities defined in the official API documentation - API-driven sends can be paired with workflow-based follow-up automation after the document is sent or signed ![Send Document (image 2 of 3)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155068515535/original/9f9zIAfoaHjASv4pPYD1boGb9vDMDMkYSg.png) **Send Document (image 2 of 3)** This screenshot appears in the "Send Document" section of "Documents & Contracts: Public APIs". The text alongside this image reads: The document must already exist in GHL Customer Care before it can be sent Recipient behavior should follow the capabilities defined in the official API documentation API-driven sends can be paired with workflow-based follow-up automation after the document is sent or signed. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Listing templates helps developers retrieve reusable document blueprints that are available in a GHL Customer Care location. This is especially helpful when your external system needs to let users choose from approved templates without…. - What this covers: The document must already exist in GHL Customer Care before it can be sent Recipient behavior should follow the capabilities defined in the official API documentation API-driven sends can be paired with workflow-based follow-up automation after the document is sent or signed - Fields: Send a prebuilt document to a contact, Standardize document sends across custom workflows, Reduce manual handoff steps for sales or onboarding teams - Controls: Send Document - Next: Listing templates helps developers retrieve reusable document blueprints that are available in a GHL Customer Care location. This is especially helpful when your external system needs to let users choose from approved templates without rebuilding the same content each time. Full procedure: 1. Send a prebuilt document to a contact 2. Trigger document delivery from an external form, portal, or app 3. Standardize document sends across custom workflows 4. Reduce manual handoff steps for sales or onboarding teams --- ## **List Templates** Listing templates helps developers retrieve reusable document blueprints that are available in a GHL Customer Care location. This is especially helpful when your external system needs to let users choose from approved templates without rebuilding the same content each time. You can use the **List Templates** endpoint to: - Fetch template records available in a location - Populate a template picker in an external app or internal tool - Verify template availability before generating a document - Standardize repeatable document creation across teams ![List Templates (image 3 of 3)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155068515858/original/L4tOJaf_IWH4w_cV5ctEF2Y17fHqPPlwLQ.png) **List Templates (image 3 of 3)** This screenshot appears in the "List Templates" section of "Documents & Contracts: Public APIs". The text alongside this image reads: Fetch template records available in a location Populate a template picker in an external app or internal tool Verify template availability before generating a document Standardize repeatable document creation across teams. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Sending a template lets you create and send a document from a saved template in one API call. This is one of the most useful options for automating proposals, agreements, and other repeatable document types because it combines document…. - What this covers: Fetch template records available in a location Populate a template picker in an external app or internal tool Verify template availability before generating a document Standardize repeatable document creation across teams - Fields: Fetch template records available in a location, Verify template availability before generating a document, Standardize repeatable document creation across teams - Controls: List Templates - Next: Sending a template lets you create and send a document from a saved template in one API call. This is one of the most useful options for automating proposals, agreements, and other repeatable document types because it combines document generation and delivery into a single action. Full procedure: 1. Fetch template records available in a location 2. Populate a template picker in an external app or internal tool 3. Verify template availability before generating a document 4. Standardize repeatable document creation across teams --- ## **Send Template** Sending a template lets you create and send a document from a saved template in one API call. This is one of the most useful options for automating proposals, agreements, and other repeatable document types because it combines document generation and delivery into a single action. You can use the **Send Template** endpoint to: - Generate a new document from a template - Send the generated document immediately - Automate repeatable contract or proposal workflows - Support personalized document delivery from external triggers or systems This option is often best when: - You already use standardized templates in GHL Customer Care - You need a fresh document created for each contact - Your process starts outside GHL Customer Care but should still use GHL Customer Care’s document infrastructure **Suggested screenshot:** Template selection or template editor view in GHL Customer Care, showing the reusable structure the API can generate from. --- ## **How To Setup Documents & Contracts Public APIs** A proper setup ensures your integration can authenticate securely, use the right GHL Customer Care location, and call the correct API endpoints. Before building, make sure you understand whether your use case is better served by a Private Integration or a broader developer implementation supported through the GHL Customer Care API platform. 1. Confirm that Documents & Contracts is part of your workflow and that the needed documents or templates already exist in the correct GHL Customer Care location. 2. Review the current **GHL Customer Care API Documentation** to confirm endpoint behavior, authentication requirements, and request details. GHL Customer Care’s official API documentation is now hosted through the Developer Marketplace documentation path. 3. Decide on the correct authentication method for your integration. Private Integrations are intended for secure internal connections, while Marketplace-style developer flows may use OAuth-based access. 4. Make sure your API requests are targeting the correct GHL Customer Care location context so that documents and templates are retrieved from the intended account area. 5. Test your request flow for the specific action you need: - List Documents - Send Document - List Templates - Send Template 6. If you want actions after a send, connect your process to workflow automations that respond to document events such as sent, viewed, signed, or completed. --- ## **Frequently Asked Questions** **Q: Are Documents & Contracts Public APIs meant for developers?** Yes. The feature is designed for programmatic use, especially for teams building integrations, automations, or custom applications around GHL Customer Care document workflows. **Q: What is the difference between Send Document and Send Template?** **Send Document** sends an existing document that is already in GHL Customer Care. **Send Template** creates a new document from a template and sends it in the same request. **Q: Can I use these APIs instead of workflows?** Yes, when your process starts outside GHL Customer Care or needs custom logic. Workflows are often better for no-code automation inside GHL Customer Care, while APIs are better for developer-led integrations. **Q: Do these APIs work with templates already created in GHL Customer Care?** Yes. The template-related endpoints are designed to retrieve templates in a location and create documents from them programmatically. **Q: Can I automate follow-ups after a document is sent?** Yes. You can pair API-based sends with Documents & Contracts workflow triggers to automate reminders, internal notifications, or downstream actions based on document status. **Q: Do I need Private Integrations to use these APIs?** Not always. Private Integrations are one option for secure internal use cases, but GHL Customer Care also supports broader developer access patterns through its current API platform and Marketplace documentation. **Q: What does “location” mean for these endpoints?** These endpoints operate within the relevant GHL Customer Care location context, so documents and templates returned by the API are tied to that location’s data. **Q: Can I manage every document action through these public APIs?** The feature article specifically documents listing and sending actions for documents and templates. For the most current endpoint coverage, always confirm the official API documentation. --- ### **Related Articles** - [GHL Customer Care API Documentation](https://docs.ghlcustomercare.com/docs/developer-resources/developer-resources-2/ghl-customer-care-api-documentation)  - [Documents & Con    tracts in GHL Customer Care – Setup and Guide](https://docs.ghlcustomercare.com/docs/documents-and-contracts/documents-and-contracts-2/how-to-use-documents-contracts)  - [Send Contracts & Proposals Using Workflows in GHL Customer Care](https://docs.ghlcustomercare.com/docs/documents-and-contracts/documents-and-contracts-2/how-to-create-and-send-document-or-contract-templates-automatically-in-a-workflo)  - [Workflow Trigger - Documents & Contracts](https://docs.ghlcustomercare.com/docs/documents-and-contracts/documents-and-contracts-2/workflow-trigger-documents-contracts)  - [Workflow Action - Send Documents & Contracts](https://docs.ghlcustomercare.com/docs/workflows/documents-and-contracts-3/workflow-action-send-documents-contracts)  - [Private Integrations: Everything you need to know](https://docs.ghlcustomercare.com/docs/integrations/private-integrations/private-integrations-everything-you-need-to-know) --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com