Illustrative prompts showing how to use the Youtrust Developer MCP across the integration lifecycle. Adapt them to your environment, credentials, and API access.

Build your integration

These prompts cover the core of what the MCP is for: understanding the API, writing the code, and getting it right.

Plan an integration

I'm building a customer onboarding flow that needs a legally binding signature. Based on the Youtrust API, propose the recommended integration flow, identify the endpoints I need, and explain which steps should happen synchronously versus through webhooks. Start with the sandbox approach.

The MCP searches the documentation, maps your business requirement to the relevant API resources, and proposes an implementation plan before any code is written.

Find the right endpoint and generate code

How do I create a signature request with multiple signers using the Youtrust API? Show me a minimal example in Python, explain the required fields, and point out where I need to add my document and signer information.

The MCP finds the relevant documentation, explains the request structure, and generates code grounded in the current API contract.

Build from a Template

Find the Youtrust template for our standard employment agreement, show me the fields and signer roles it expects, and explain how I can create a signature request from it in the sandbox without sending anything to a real signer.

The MCP searches your Templates and the documentation, clarifies the required inputs, and helps you build a repeatable workflow before moving to production.

Debug an integration

My request to create a signature request returns a 400 error. Here is the request payload and response: [paste payload and response]. Check the payload against the Youtrust API documentation, identify the likely issue, and provide a corrected version. Do not execute the request.

The MCP compares your implementation with the API contract, explains the error in practical terms, and suggests a fix without making an API call.

Implement webhooks

Show me how to handle Youtrust webhook events for a signature request becoming completed or declined. Generate a Node.js example that validates the event, handles retries safely, and updates my database idempotently.

The MCP guides you through asynchronous patterns, event handling, and reliable implementation practices, rather than treating the API as a collection of isolated endpoints.

Check your integration while you build

These prompts read and act on your own data. They are useful to confirm your integration behaves as expected while you develop it.

Check status and follow up

In sandbox, find the signature requests created in the last 14 days that are still pending. Group them by status and tell me which ones have been waiting for more than five days.

The MCP searches and filters your Signature Requests and summarises the current state.

Send a reminder with confirmation

For the pending signature request [ID], confirm the document name, recipients, current status, and last reminder date. If it is eligible for a reminder, explain what will happen and ask for my confirmation before sending it.

The MCP retrieves the context, checks whether the action is appropriate, and asks for a human confirmation before a consequential write action.

Retrieve the completed document

Find the completed signature request for [reference]. Check whether all signers have completed it, then explain how to download the final signed document and audit information. Do not download anything until I confirm.

The MCP finds the request, checks its state, explains the retrieval steps, and preserves your control over document access.

Prompt design principles

Principle	Why it matters
Give business context	The more context you give, the better the agent selects the right workflow and Resource.
Ask for a plan before execution	When an action can create, send, remind, or download something, ask for the explanation first.
Include identifiers and constraints	IDs, dates, statuses, and limits let the agent target the right records.
Keep a human in the loop	Use the MCP freely for read-only discovery, but confirm every consequential write actions especcialy in production.
Search in short queries	Documentation search matches keywords literally. Several short questions beat one long one.