How to retrieve send mail configuration in Zoho

Retrieving your send mail configuration in Zoho CRM is straightforward via a single settings API endpoint that returns the outgoing mail setup for your organisation.

Why this matters

When you need to audit, troubleshoot, or programmatically inspect how outgoing emails are configured in Zoho CRM, you need a reliable way to pull that data without navigating through multiple UI screens. This is especially useful for consultants onboarding a new client, developers building integrations, or admins verifying that the correct sending identity is in place. Understanding the API call also lets you automate configuration checks as part of a broader health-check workflow.

Step-by-step

Step 1. Ensure your Zoho CRM connection is authenticated and your access token is valid. The OAuth flow requires a connected session before any settings endpoint can be reached — if the connection is missing or expired, the API will reject the request. ^[3]

Step 2. Confirm that your OAuth scopes include the necessary CRM organisation-level permissions. The scope set used for Zoho CRM should cover ZohoCRM.org.ALL (or at minimum read access to org settings) so that settings endpoints are accessible to your token. ^[7]

Step 3. Issue a GET request to the /settings/sendmailconfig endpoint. This is the dedicated operation — labelled getsendmail_config — under the Mail & Social settings category of the Zoho CRM API. ^[5]

GET /settings/send_mail_config

In Python, using the CRM client wrapper, the call looks like this: ^[5]

def get_send_mail_config(self):
    return self.c.request("GET", "/settings/send_mail_config")

Step 4. Parse the response object returned by the endpoint. The result will contain your organisation's outgoing mail settings. Store or log this data as needed for your audit or integration logic. ^[5]

Step 5. If you are working within a multi-app environment (CRM + Desk), make sure you are targeting the CRM API client specifically — not the Desk client — since /settings/sendmailconfig is a CRM-scoped endpoint. The app_type parameter in the connection layer controls which API client is instantiated. ^[1]

---

> Note: Beam Help is independent expert support for Zoho — we are not official Zoho support. For billing or account-level issues, contact Zoho directly.

---

Common pitfalls

• No active connection. If the zoho_connections record for the current user is missing or the token has expired, the API layer will surface an error such as *"Zoho is not connected for this app. Please reconnect."* Always verify the connection status before calling settings endpoints. ^[1]
• Wrong data centre. The OAuth token and API domain are tied to the data centre (com, eu, in, etc.) recorded at token exchange time. Sending a request to the wrong regional domain will result in an authentication failure. Check the api_domain value returned during the OAuth code exchange. ^[3]
• Insufficient scopes. If ZohoCRM.org.ALL was not included when the OAuth consent was granted, the settings endpoint will return a permissions error. You may need to revoke the existing token and re-authorise with the correct scope list. ^[7]

What to check

• Token validity: Confirm the access token has not expired and that a valid refresh token is available to obtain a new one if needed. ^[3]
• Scope coverage: Verify that ZohoCRM.org.ALL is present in the scopes granted during OAuth authorisation. ^[7]
• Correct API client: Make sure the request is routed through the CRM API client (not Desk), and that the app_type is set to "crm" in your connection configuration. ^[1]