Jump to content

Steel, Mark

Moderators
  • Posts

    464
  • Joined

  • Last visited

  • Days Won

    35

Steel, Mark last won the day on February 13

Steel, Mark had the most liked content!

Reputation

45 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Carlos, Thank you for your post. Sage 300 isn't a product supported on the community at present. If you don't receive a response you can contact the Sage 300 Developer Support team at [email protected]. Thanks Mark
  2. Hi Carlos, Sage 300 isn't a supported product in the community at present. You can direct your queries to the Sage 300 Developer Support team at [email protected] for help with this issue. Thanks Mark
  3. Hi Donna, Sage 300 isn't a supported product in the community at present. You can direct your queries to the Sage 300 Developer Support team at [email protected] for help with this issue. Thanks Mark
  4. Hi Caludio, Thank you for your post. Alternatively to requesting attributes=all you can use the ID of the data record to obtain the full response. https://api.accounting.sage.com/3.1/ledger_accounts/e438573afaca11e7aa730a57719b2edb Thanks Mark https://developer.sage.com/accounting/reference/accounting-setup/#tag/Ledger-Accounts/operation/getLedgerAccountsKey
  5. Hi Paul, Thank you for your post. The Key is the contact ID in this instance. The search facility is to the right in the top banner. Thanks Mark
  6. Thanks Andrew, You'll need to pass Accept:application/json in the header also. There's a useful POSTMAN env which has a small collection you can use as a starting point to build out the collection further.
  7. Hi Shivam, Thank you for your post. The API gateway times out after 28 seconds of waiting for a response from the backend. If you're creating artefacts, Estimate's in this instance with a large number of line items it may be that at times the backend is unable to respond in 28 sec's. If the payload is all good the artefact will be created. You'll need to think about implementing idempotency in your requests if large numbers of item lines is likely to be the norm. https://developer.sage.com/accounting/guides/concepts/idempotency/. I've also referenced the below threads in the developer community from people having similar issues when posting sales_invoices. https://developer-community.sage.com/topic/775-time-out-on-invoice-creation/#comment-2033 https://developer-community.sage.com/topic/637-sales_invoices-timeouterror-the-backend-has-not-responded-within-28s-while-proxying-this-request/#comment-1765 Thanks Mark
  8. Hi Andrew, Thanks for your post. What is the request you are making and what headers are you passing in the request? Thanks Mark
  9. Hi Joe, I'm not sure why you referenced https://capcutproapk.org/? The API reference for https://developer.sage.com/accounting/reference/products-services/#tag/Products/operation/postProducts provides the ability to expand the sales_prices array which references the product_sales_price_type_id as per the example json body above. It doesn't highlight it as a required field however so we do need to update that aspect of the swagger/open API spec. https://developer.sage.com/accounting/reference/products-services/#tag/Product-Sales-Price-Types - Details how to obtain and create product_sales_prices. Thanks Mark
  10. Hi Rishiom, The fix has now been deployed and the problem client_id's are now working. Thanks for your patience. Mark
  11. Hi Daniela, Sage Business Cloud Accounting exposes public API's to provide integration ability to third party software solutions. https://developer.sage.com/accounting/reference/. Looking through our integrators on Sage Marketplace there is one product stating it is integrating with Prestashop and Sage Business Cloud Accountinghttps://uk-marketplace.sage.com/en-GB/home. Wether this specific integration provides the functionality you are looking for would be something you would need to determine. Thanks Mark
  12. Hi Rishiom, The deployment of the fix will happen tomorrow afternoon(07/02/2024) GMT Thanks Mark
  13. Thanks Alexandre, This is the bug section for our API's used by our integrators. Thanks Mark
  14. Hi Rishiom, We are aware of an issue with generated client_id guid's which are failing to pass a regex in our auth service. It sounds as if this could be the issue for yourself. We're hoping to push a fix live today 06/02/2024 to resolve the issue. If you DM me with the client_id you're using i'll be able to check if this is the issue. Thanks Mark
  15. Hi Ray, Thank you for your post. You've posted in the General lobby without mention of the Sage product you are integrating with. If you can provide the name of the product and information relating to the error we'll be able to help/guide you better. Thanks Mark
×
×
  • Create New...