Jump to content

Search the Community

Showing results for tags 'api'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Welcome
    • General
    • Feature Requests
    • Content Requests
    • Ideas Exchange
  • Products
    • Sage Business Cloud Accounting
    • Sage X3
  • Services
    • Banking Service
  • SAGE X3 Developers's Topics

Categories

  • What's New?
  • Innovate and Co-create
  • Scale and Grow
  • Supporting You

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Job Title

Found 7 results

  1. Hello everyone I wanna tell you a problem that get show when i´m doing a request in Postman to the Auth to get the TOKEN, however the next error appear These are the data i sent
  2. The new Reduced Rate 2 tax code has been introduced recently but now using a GUID instead of the string value (e.g. GB_EXEMPT) as per previous VAT codes. This breaks our integration as some Tax Codes use string code naming convention and now the new one uses GUID (As per screenshot). This must be a mistake, right?! Can you please update so the new VAT rate uses a Code following the original naming convention? Or, move all to GUIDs so the construct is uniform and we can code against it effectively? Unless this is fixed we will have to code for this glaring inconistency.
  3. Hi, We are on X3 V12 90.24.54. I am updating some sales orders via C# using web services. What I have noticed is that the sales line details API is updating incorrect line details, even after explicitly setting product code + line numbers. It seem that it is updating line detail based on the order received rather than observing the product code and line number. An example is I have a sales order with four line details (1000 -> 4000). I only want to update line 4000. My XML payload to the webservice is: <?xml version="1.0" encoding="UTF-16"?> -<PARAM xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> -<GRP ID="SOH0_1"> <FLD NAME="BPCORD">ABC001</FLD> <FLD NAME="SALFCY">UATSITE</FLD> </GRP> -<TAB ID="SOH4_1" SIZE="1"> -<LIN NUM="1"> <FLD NAME="ITMREF">HNP00019</FLD> <FLD NAME="NUMLIG">4000</FLD> <FLD NAME="SOPLIN">4000</FLD> <FLD NAME="QTY">12</FLD> <FLD NAME="ITMDES">This is a closed line really</FLD> </LIN> </TAB> </PARAM> I'm calling the webservice "SOH" endpoint, using the Modify method. The call is working correctly and updating the line detail, unfortunately, its the wrong line detail. I've tried omitting the SOPLIN field, etc. If I omit the NUMLIG field, then a new line detail is inserted (as expected). Any ideas?
  4. We have released a new update(#50) to our Banking Service Provider documentation. Please find what we have been working on within the following change log: Content improvements to setup, integrate and go live & support sections. Created new format for easier navigation; Explore Setup Integrate Go live & support Added explore section to easily access API specification, public postman collections and search by use case. Amended the getting started overview to fit this format change and allow for easier navigation. Updated contact us sections to reference our new banking service forum. Added supported Sage products and regions page. Updated navigation menu to fit format changes. Updated our provider walkthrough guides; Onboarding Re-Authorisation Posting Statements Multi Account Link Disconnection User experience added supporting graphical Imagery and content amendments. Added new field 'currency' to the provider API specification. Updated provider API specification with correct property descriptions for the PATCH /authorisations endpoint. Updated flow diagrams to contain retrieval of Sage ID token. Onboarding Re-Authorisation Posting Statements Corrected the Multi account link walkthrough, changing 'bankaccountids' query parameter to be 'externalId'. Updated the Multi account link walkthrough with descriptions of each field returned. Updates to the connector API specification; Correct property descriptions for the GET /availableAccounts endpoint. Amended 'bankaccountids' query parameter to be 'externalId'. Updates to our public banking services postman collections. If you have any feedback on these changes, please let us know below. 👇
  5. Hi All, Has anyone had any success connecting Postman to the Sage GraphQL sandbox environment? I've followed all the instructions here https://developer.sage.com/api/x3/graphql/quick-start-guide/ but no joy. Postman just pops up the OAuth window with the text "{"message":""}" in it. Its soooooo frustrating. Many Thanks.
  6. Hi, I'm currently building an application for a Client and receiving an Authentication error when attempting to request an access token. Tried both below authenticating via browser. Both in which I was advised to raise a support ticket Have registered the call back url for the application. Just wondering what the issue might be?? Any help would be appreciated. Regards, James
  7. Hi, In Sage One API, I would like to know if it is possible to get an Access Token without the input of the user / redirect_uri. From my understanding we must call the https://www.sageone.com/oauth2/auth route that will prompt the user to enter the login infos manually and then redirect the user to a redirect_uri callback with a code. And then we will be able to call https://oauth.na.sageone.com/token with the provided code to get the Access Token. What we want is the authentication step in the API to be transparent to the user. Thank you!
×
×
  • Create New...