Now that we have covered some of the mechanics of calling the APIs, then what happens? Well, depending on the API you call, you will get back one or more ‘records’ (assuming your search found something that is). The format of the record that you get back is actually controlled by a parameter in the request called ‘ResourceType’. Common to the /people, /companies and /match APIs, there are 3 record types: Core, Basic, and Enhanced. The people API also includes 2 additional types: TargetReady, and LifeStyle.
The 3 most common types are Core, Basic, and Enhanced. 
The most basic record is the ‘Core’ record and it looks like this:
https://api.infoconnect.com/v1/companies/719342925?resourceType=core

Result:

{
        "ETag": "b8cc3f99",
        "Id": "719342925",
        "Links": [
            {
                "Href": "/v1/companies/719342925",
                "Rel": "self"
            },
            {
                "Href": "/v1/companies/452186299",
                "Rel": "parent"
            }
        ],
        "ParentCompany": "452186299"
}
Both ETag and Id are internal record ids that uniquely identify this particular record. The 'Id' field is especially useful because you can use it in a call to the get API for companies or people to retrieve this particular record again. The same goes for ‘ParentCompany’ if this company has one.
In fact, you can see in the ‘Links’ array, we return these exact URIs for both this record and the parent company record (if there is one).
So that is the 'Core' record. It contains just the most basic identifier for the data. The next type of format is the ‘Basic’ record and builds on the 'Core' record to include more information. Below is an example of what this looks like for the same company:
https://api.infoconnect.com/v1/companies/719342925?resourceType=basic

Result:

{
    "ETag": "4e9b0263",
    "Id": "719342925",
    "Links": [
        {
            "Href": "/v1/companies/719342925",
            "Rel": "self"
        },
        {
            "Href": "/v1/companies/452186299",
            "Rel": "parent"
        }
    ],
     "Address": "777 Brockton Ave", "AddressParsed": { "Name": "Brockton", "Number": "777", "Suffix": "Ave" }, "City": "Abington", ""CompanyName": "SUBWAY", "FirstName": "J", "LastName": "Leone", "Location": { "Latitude": 42.096019, "Longitude": -70.967567 }, "Phone": "7814212014", "PostalCode": "02351", "StateProvince": "MA",
    "ParentCompany": "452186299"
}
The next step up from Basic is the ‘Enhanced’ record. This record, again, builds on the Core and Basic and includes even more information.
https://api.infoconnect.com/v1/companies/719342925?resourceType=enhanced

Result:

{
    "ETag": "c8ce34a6",
    "Id": "719342925",
    "Links": [
        {
            "Href": "/v1/companies/719342925",
            "Rel": "self"
        },
        {
            "Href": "/v1/companies/452186299",
            "Rel": "parent"
        }
    ],
    "Address": "777 Brockton Ave",
    "AddressParsed": {
        "Name": "Brockton",
        "Number": "777",
        "Suffix": "Ave"
    },
    "City": "Abington",
    "CompanyName": "SUBWAY",
    "FirstName": "J",
    "LastName": "Leone",
    "Location": {
        "Latitude": 42.096019,
        "Longitude": -70.967567
    },
    "Phone": "7814212014",
    "PostalCode": "02351",
    "StateProvince": "MA",
     "BusinessType": "Restaurants", "County": "Plymouth", "CreditRatingScore": "B+", "Franchise": "Subway", "Gender": "Male", "LocationEmployeesSizeActual": 7, "LocationEmployeesSizeRange": "5-9", "LocationSalesVolumeActual": 406000, "LocationSalesVolumeRange": "Less Than $500,000", "NaicsList": [ { "Code": "72251301", "Description": "Limited-Service Restaurants" }, { "Code": "72251117", "Description": "Full-Service Restaurants" }, { "Code": "72251302", "Description": "Limited-Service Restaurants" }, { "Code": "72251303", "Description": "Limited-Service Restaurants" } ], 
    "ParentCompany": "452186299",
     "PrimaryNaics": "72251117", "PrimarySic": "581208", "SicList": [ { "Code": "581206", "Description": "Foods-Carry Out", "YearFirstAppeared": "2009" }, { "Code": "581208", "Description": "Restaurants", "YearFirstAppeared": "2009" }, { "Code": "581209", "Description": "Delicatessens", "YearFirstAppeared": "2009" }, { "Code": "581219", "Description": "Sandwiches", "YearFirstAppeared": "2009" } ], "Title": "Owner", "UriList": [ { "Uri": "subway.com" } ], "ZipPlus4": "02351-2111"
}
So far all these examples have applied to companies, but people also have the same kinds of records, each with more and more information returned with them. Check out the people api pages for all the details on those!
One final thing before we finish is that while these types are basically fixed in what data they will return, the APIs also support what is essentially a custom record. Using the 'Fields' parameter in a POST request and omitting the ResourceType paramter you can get only the data back that you want! So, for example, if you only want the company name, geo location, and phone number you could make a POST request like this:
POST https://api.infoconnect.com/v1/companies/search?apikey=
Body:
{
  "Id":["719342925"],
  "Fields":["CompanyName","Location","Phone"]
}
The result will be a ‘Core’ record along with the fields you requested.
{
	"ETag": "7148eab3",
	"Id": "719342925",
	"Links": [
	    {
	        "Href": "/v1/companies/719342925",
	        "Rel": "self"
	    },
	    {
	        "Href": "/v1/companies/452186299",
	        "Rel": "parent"
	    }
	],
	 "CompanyName": "SUBWAY", "Location": { "Latitude": 42.096019, "Longitude": -70.967567 }, "Phone": "7814212014", 
	"ParentCompany": "452186299"
}
The API documentation contains a list of all the available fields for people and company records in the “Custom Output” section of the doc for each API.