Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.attio.com/llms.txt

Use this file to discover all available pages before exploring further.

Before submitting your app for review, ensure your app listing meets the following requirements. Apps that don’t meet these requirements will be rejected.

​
Developer account

  • Account name MUST NOT contain “Attio” or impersonate any other company.
  • Account name MUST NOT include “dev”, “test”, or other non-public-facing terms.
  • Account name MUST be appropriately capitalized.
  • Account name MUST be suitable for the public App Store.
  • Account MUST have a logo. See logo requirements for specifications.

​
App name and slug

  • App name MUST NOT contain “Attio”.
  • Non-official apps MUST NOT imply they are the official integration for a service (e.g. only Meta or Attio may name an app “WhatsApp”).
  • Official apps MUST match the service’s exact name and capitalization.
  • Unofficial or utility apps MUST use title case (e.g. “Stripe Syncer” not “Stripe syncer”).
  • App name SHOULD be consistent with the developer account name.

​
Tagline

  • Taglines MUST use sentence case.
  • Taglines MUST clearly describe what the app or service does.

​
Category

  • Categories MUST be correctly selected for the app’s function.

​
Text content

Your listing includes three text sections: Overview, How It Works, and Configure. Each MUST be between 100 and 3,000 characters. All text content MUST be high quality, well-written, and free of typos. Additionally:
  • All text content MUST be written in English.
  • Headers MUST use the correct hierarchy and MUST NOT end with a colon.
  • Content MUST use the following capitalization for the following Attio concepts: “records”, “objects”, “lists”, “people”.
  • Overview MUST provide a clear description of the app and/or external service.
  • How it works MUST explain the app’s key features and functionality.
  • Configure MUST clearly explain the setup steps for the user.

​
Submission video

  • Initial app submissions MUST include a video walkthrough of the app’s functionality.
  • The video MUST be a screen recording which walks through all app functionality, including installation, authentication/configuration, and core app features.
  • The video MUST walk through the Attio integration specifically and MUST NOT be a generic demo or marketing video.
  • All links MUST use HTTPS.
  • All links MUST return a 200 status code when visited.

​
Website URL

  • Website URL MUST point to your company or product homepage.

​
Documentation URL

  • Documentation URL SHOULD point to a precise documentation page for the Attio app. If a specific page is not available, we will accept the closest suitable page.

​
Contact email

  • The contact email MUST be a valid email address.

​
Terms of service

  • The terms of service URL MUST link to a terms of service page.

​
OAuth entry point URL

  • The OAuth entry point URL MUST be a valid URL that returns a 200 status code when visited.
  • OAuth entry point URL (if applicable) MUST take the user to the closest entry point into the authentication flow with Attio.
  • The OAuth entry point URL MUST handle all authentication errors appropriately.

​
Terms and data

  • Your app MUST be compliant with all items stated in its own terms and privacy policy.
  • Your app MUST NOT breach the terms of any other relevant services (e.g. if connecting to Stripe, your app must not breach Stripe’s terms of service).

​
Scopes

  • Your app MUST request the minimum set of required scopes.
  • The usage of scopes MUST be justified.