Try out the Record Matching API using the Swagger UI

The goal of this tutorial is to guide you through the Record Matching REST API using it's dedicated Swagger User Interface. Swagger UI is a great tool that documents and allows you to test REST APIs. This guide shows you how to use it for trying out the Record Matching API

Instructions

1. Upload records as a csv file

• Click on the 'Try it Out' button to enable the input parameter fields
• Paste your access token (API key) into the access-token field (If you do not have a access token, click here to view instructions to generate one)
• Upload your input data file, at appropriate
• Click on 'Execute'

• At this instance, the Swagger UI sends the request to the PermID server, await for the response and displays it

2. Upload records as plain text

• Click on the 'Try it Out' button to enable the input parameter fields
• Paste your access token (API key) into the access-token field (If you do not have a access token, click here to view instructions to generate one)
• Enter text in the standard format in the Text field. The format is shown below: 

                LocalID,Standard Identifier,Name,Country,Street,City,PostalCode,State,Website

                1,RIC:AAPL.O|Ticker:AAPL,Apple,US,"Apple Campus, 1 Infinite Loop",Cupertino,95014,California,

• Click on 'Execute'

• At this instance, the Swagger UI sends the request to the PermID server, await for the response and displays it

Among other information, the API response includes a Response Code and a Response Body

• Response Code:  The Response Code gives you a status on the request you sent. If everything went fine the returned code should be "200", meaning the request has been handled successfully by the server
• Response Body: The Response Body contains the actual Matching results . For each entity sent for matching, the response contains at least 1 match record. If the input record was successfully matched, there are one or more matching PermID entities in the response, depending on the x-openmatch-numberOfMatchesPerRecord value supplied in the request, and the number of matches found. A sample response body is shown below:

References

To learn more and for a detailed description of the API response, please refer the Record Matching API

We also recommend you to follow the Record Matching Tutorials that explains how to leverage the API in Java example applications

Questions?

If you have any querstions regarding the use of  Entity Search API or any support questions in general, please use the Q&A section of the Developer Community and raise them there.