![]() Learning to read the Sage Intacct DTD and XSD files will help you write valid XML more consistently.Īt a high level, the XML document establishes various credentials and provides the API function calls, as shown.įor an in-depth look at each of the elements in the XML request body, see the XML requests topic.īy default, the response from the gateway returns to the client in the same HTTP connection as the request, which is known as a synchronous response. ![]() Your XML requests must be constructed carefully in order to avoid an error response from the gateway. 3.0 is validated against the XSD file inside the v3.0 folder.2.1 is validated against the DTD files inside the v2.1 folder. SAGE INTACCT DOWNLOADSage Intacct currently does not support receiving JSON through Web Services.Īll schemas are available for download in the intacct_dtd repository on GitHub.Īs XML requests are passed through the Sage Intacct Web Services gateway, they are parsed and validated against either a DTD or XSD: Use POST requests only.Īll data should be sent encoded as XML with a Content-Type of application/xml. Note: HTTP GET requests are not supported and will be blocked at a future date. You use HTTP POST requests to communicate via a unique endpoint. Typically, this will be a Web Services user account, which does not include UI access (see Web Services users in the Sage Intacct product help). In addition, the administrator for the target company must:Įnable the Web Services subscription using Company > Admin > Subscriptions.Īuthorize your Web Services sender ID for the company.Ĭreate your user ID. Note: If you need a developer license, contact your account manager. A sender ID can be authorized for more than one company and can be tracked through an audit history report. You must have an active Sage Intacct Web Services developer license, which includes a Web Services sender ID and password. Note: For information about creating extensions that are inside the Sage Intacct UI, see the Platform Services documentation. Some of the material about working with XML APIs directly is not as relevant when working with the SDKs, but it’s still important to understand the underlying concepts. The rest of this topic highlights basic concepts of Web Services. ![]() Your application interacts with the system through the Web Services gateway using one of the Sage Intacct SDKs or using the underlying XML API framework directly. Once integrated, your application can create, update, read, or delete standard or custom objects in a Sage Intacct company (or tenant). With Web Services, you can leverage the cloud storage and advanced business logic of the Sage Intacct SaaS framework while providing your own customer-facing web application.įor example, you might integrate a web store front or other business with automated billing into the Sage Intacct ecosystem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |