How can I get a list of valid SDATA endpoints?

Question

Hello

So my client is using Sage Accounts 50 v27. Sdata is enabled and lists in settings the URL http://<server name>:<port>/sdata/accounts50/GCRM/{<some sort of UID>} I tried to use curl from a different machine on the network to obtain a list of projects. However all URLs I found in the sage documentation return error, ApplicationNotFound, Unable to locate a handler to process the request '<URL part after /sdata/>' The only URL I found in the documentation at http://sage.github.io/SData-2.0/pages/core/1403/ that actually returns something is http://<server name>:<port>/sdata/$system/registry/-/endpoints which is supposedly a list of accessible endpoints, but there are only 2 /accounts50 and /accounts50/GCRM and accessing with CURL returns a different error: ResourceKindNotFound, Unable to locate the specified object 'accounts50'

Please note that with curl I am sending the Basic Authorization header with my sage user account, thought without it, I get the same errors.

So, how can I access the API to return something useful?

Your help is greatly appreciated.

Darron Cockram · Accepted Answer

Lucian Pricop said: However all URLs I found in the sage documentation return error, ApplicationNotFound That error would happen if the accounts50 provider were not registered or not enabled on the PC. Querying the $system/registry/-/endpoints URL is the right thing to do to determine if a provider is available and registered, but even if it is none of the URLs returned are directly 'browsable'. Rather they are stems of what would be a valid URL. You would need to include further detail on the URL to actually retrieve any information. This page shows an example https://sage.github.io/SData-2.0/pages/core/0201/ but if you are sending a request of the form http://:/sdata/accounts50/GCRM/{} the key thing you are missing is the resource kind which would go after the UUID (which is actually the unique identifier of a dataset). The specific resources that can be requested are 'self documented' via a $schema request so you can simply issue a request to http://:/sdata/accounts50/GCRM/{} /$schema to see what is available. Note that the dataset Id provided in that URL must be a valid one for an existing and available dataset for the request to complete successfully. Lucian Pricop said: there are only 2 /accounts50 and /accounts50/GCRM and accessing with CURL returns a different error: ResourceKindNotFound, Unable to locate the specified object 'accounts50' So what that is saying is that the accounts50 application is registered and that it supports the GCRM contract, so the Sdata adpater is available and can deal with requests adhering to that schema. However if there are only those 2 entries it means there are no datasets registered, or that any that were are currently unavailable/inaccessible. Specifically the error means Sdata could not find the appropriate resource kind to be requested (supported resource kinds can be discovered via the $schema request as noted above). A couple of things to look at here. First of all if you open the Accounts application on the same PC you are issuing the requests to do you have any available datasets to open (not including demo data or practice data), and are you able to open and access that data in the Accounts application? If you can then the 2nd thing to look at is where is the data located i.e. is it on a local drive or a remote path (UNC or mapped drive)? 'Local' being local to the PC that is running the Sdata service you are trying to query. If the data is on a remote path then Sdata will not be able to access this by default so you would need to either reconfigure things to allow the service to access data on the network, or move the data to be local. It may be best to start simple and create a new test dataset (company) in Accounts ensuring you use a path to a local drive (the default path should be fine normally) and then query the endpoints URL again via localhost i.e. http://localhost:5495/sdata/$system/registry/-/endpoints . If things are working correctly you should see an additional entry in the response that will be the dataset and include the dataset Id. Armed with the dataset Id you can then issue a schema request http://localhost:5495/sdata/ accounts50/GCRM/{}/$schema and that will tell you all of the available resource kinds and what operations they support. With this information you could issue a simple request to actually return some data e.g. localhost:5495/.../{}/taxCodes Lucian Pricop said: I am sending the Basic Authorization header with my sage user account, thought without it, I get the same errors. You will need to provide authentication for a valid URL to be processed, but the errors you are getting are happening before any authentication occurs which is why it currently makes no difference. The above errors are all endpoint routing issues where the Sdata service is unable to determine an appropriate handler for the request. Authentication will only kick in once a valid handler has been determined and the request is passed on to it. Also worth noting that authentication is applied within the context of the dataset you are connecting to so the the account details you need to send are the username/password for the dataset you are connecting to. Hope that helps.

Sage 50 Accounts

How can I get a list of valid SDATA endpoints?

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING