> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-tailored-solution-integration/gumu-sage-intacct-checkbook-integration/pre-requisites/sage-intacct/sender-id-web-service-authorization.md). # Sender ID Web service authorization ***Why this is needed?***\ Sender ID is token used for web services call made by GUMU™ integrations, Sage Intacct provides this Sender ID to development partner to enable successful calling of web services from external application. This Sender ID needs to be authorized by the client in their Sage Intacct Company which will be used in integration. ***Important note***\ This is mandatory setting. ***How it is done?***\ Web services should be authorized in Sage Intacct for the integration to execute correctly, to achieve this follow the steps mentioned below 1. Click on link mentioned below\ 2. Login into Sage Intacct Company using Company ID, User ID, Password. ![](/files/-MLzwSlPqHHb4fsBIvBB) 3\. Add Web Service Authorizations for Sender id – **ajax**\ ***How it is done?***\ *Navigation path* - Company > Company Information > Security tab > Scroll down to Web Services authorizations section set the following fields\ Add Sender ID – **ajax**\ Status – **Active** 4\. Add web service authorization for Sender id – **GreytrixMPP.**\ This sender ID will be provided by Greytrix. User needs to provide access to this sender id in their company as it is important part of the security rights for the integration. ***How it is done?***\ *Navigation path* - Company > Company Information > Security tab > Scroll down to Web Services authorizations section set the following fields.\ Add Sender ID – **GreytrixMPP**\ Status – **Active** ![](/files/-MLzwSlQOE2BahVZPS67) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.greytrix.com/gumu-tailored-solution-integration/gumu-sage-intacct-checkbook-integration/pre-requisites/sage-intacct/sender-id-web-service-authorization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.