What Is Included with Quip Developer Support

What Is Covered by Quip Developer Support

Quip Developer Support is available to customers with an active Quip Enterprise or Quip Advanced subscription and covers the following areas:

• Quip Admin API: Assistance with authentication, endpoint behavior, event log retrieval, and bulk export operations
• Quip Automation API: Help with creating, editing, and managing documents and spreadsheets programmatically using API calls
• Quip Live Apps API: Support for developers building custom Live App components embedded in Quip documents
• Salesforce Flow integration: Guidance on configuring Quip actions in Salesforce Flow Builder, including creating documents, editing sections, and adding documents to folders
• API key management: Assistance with creating, scoping, and troubleshooting API keys in the Quip Admin Console

Example: A Salesforce developer building a Flow that automatically generates a Quip deal plan when an Opportunity reaches Stage 3 can open a Developer Support case to get help configuring the Create Document and Add Document to Folder Flow actions.

What Is Not Covered

The following are outside the scope of Quip Developer Support:

• Custom application development beyond Quip's supported API surface
• Third-party integrations not built on the Quip API
• Salesforce Platform issues unrelated to Quip API calls or Flow actions
• Live Apps that have been retired (custom Live Apps retired in 2023)
• Debugging customer-written code beyond identifying API usage errors

How to Open a Developer Support Case

To get the fastest resolution, include the following in your support case:

• The API endpoint you are calling and the exact request payload (with sensitive data redacted)
• The full error response or unexpected behavior you are observing
• The Quip site URL and the article or document ID involved, if applicable
• The Salesforce Flow name and version, if the issue involves a Flow action

API Documentation Resources

Before opening a case, review the Quip developer documentation for the API you are using. Many common integration questions are addressed in the reference documentation.