Discover SharePoint 2013 webservices - sharepoint-2013

I'm struggling to access to some data hosted on a website.
I know this website was developed using Sharepoint 2013 (by someone else, and I don't have any contact with them).
I have the right credentials to the site, and via browser I can navigate and obtain the data I need (some electric measurements).
I need a way to obtain the data using a webservice.
Is there a way to discover all the webservices implemented on the site? And to gain access to those data?
I browsed the lists on _api/Web/Lists but due to my lack of knowledge I didn't find anything useful.
Thank you all!

Best way to start you discovery of default SharePoint web services is from here
There are at least 3 default services that you could use to get more information from different lists and webs:
/_api/site
/_api/web
/_api/web/lists/getbytitle('listname')/items
Unfortunately I don't think there is a way to discover all web services there are on your particular site

Related

Connect to CRM with only webservies

Can someone please point me to the direction where there is a example on how to connect and retrieve data from Microsoft Dynamic online 2011 with only the web services, such as Discovery and Organization, and not using any of the SDK that Microsoft provided. It would also be nice if I dont need to add System.ServiceModel.
I looked at the Soap example it still used Microsoft.Crm.Sdk.Samples.
The reason i am avoiding any SDK or namespace is I am trying to build a SQL CLR that can connect to CRM online and retrieve the data i needed for the reports. The reports are based on my local database and CRM data.
Thank you for all the help
Most data can be fetched (and relationships are well represented) via the oData/REST web services. You don't need any particular SDKs or custom code, just anything that can read data in XML or JSON format from a URI.
[Your Organization Root URL]/XRMServices/2011/OrganizationData.svc is where you'll find the fun stuff. Documentation is on MSDN at http://msdn.microsoft.com/en-us/library/gg334767.aspx

Accessing Sharepoint lists from a Standalone Application

I have a Standalone application, which needs to access a Sharepoint list. I bumped into a few articles, mentioning Web Service is the way to go about it.
But I am unable to find a step by step path to write a web service to fetch list from sharepoint. In addition to this, the application can take a WSDL file as an input.
Please let me know how to proceed about this scenario.
If you are using SharePoint 2007, then web services is the only way to do this. Here is a list of the different web services available.
If you are using SharePoint 2010 you can use the client object model.
You can simply use the SharePoint webservice Lists.asmx (both in SharePoint 2007 and 2010)
In your application, add a web reference 'http://(sharepoint-url)/_vti_bin/lists.asmx'
Once done, you can use the method GetList.
For more information, http://msdn.microsoft.com/en-us/library/lists.lists.getlist(v=office.12).aspx#Y82

Microsoft Dynamics CRM -- Do people build websites with it?

Forgive my ignorance, but do people build websites with Microsoft Dynamics CRM?
I have a potential client who says that is the technology they will use for a new web project, for which I would be doing the HTML templating. I want to learn all I can as I am new to this particular system, but I can't seem to find anything related to web building and CRM. Is it more likely the client is using another piece of technology that they are neglecting to tell us about?
Any experience or insight about this process is greatly appreciated!
You can't build website using MSCRM, but you can build ASP.Net website using CRM content easily. The API provided by MSCRM is a set of web services, that can be queried in a website to populate pages content.
Also, you can directly query the Database if you want ReadOnly content, and only for read-only content, because it is not supported to update/create data using SQL connections.
Note that it's required to have the external connector license to use any data in the CRM, thru the API and even thru direct SQL queries.
I have built a website using .NET, utilising the CRM4 API and database. All the website did was to submit queries to CRM using the CRM web services and metadata web services, and get data back. This company was already using CRM for their back end, so it's much easier for the front end to use the same database as well since it's a simple one.
The alternative would be to create an intermediate connector between the 2 systems -- backend and front end, which is not as efficient (for our case anyway).

Will SharePoint 2010 support Web Service Access?

It's my understanding SharePoint 2010 has introduced a new JavaScript API, a brand new assembly for Silverlight clients, but does anybody know if there will be still support for good old Web Service Access?
By old services, I am referring to the old interface
http://msdn.microsoft.com/en-us/library/dd878586.aspx
Yes SharePoint 2010 still has web services. Review this MSDN section for more information.
Essentially the new API's are there to help client side code run interesting code without having to use the Web Services. If you have ever tried utilising a webservice from Javascript you can understand the pain the new API's are trying to prevent.
The Web services are still supported. However, the data-retrieval oriented Web services should be considered semi-deprecated. Going forward, you shoul use either the client object model or ADO.NET Data Services to get data from a client.
I've been trying to figure out how to administrate the whole thing with whatever APIs are available. The MSDN documentation seems like what I need, except I feel stupid and can't find where those APIs are on my server. There are no URLs to be seen in the documentation. Am I blind?

Using a Web Service to access data outside MOSS using AD for authentication

So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.