Our newly released Name Normalization endpoint takes semi-structured name data provided as a string and outputs the data in a structured format. We use US census data, coupled with proprietary algorithms, to parse the name string and determine which pieces belong in which categories. We also return the the likelihood that the data is structured correctly, based on the underlying census data.

As an example, if you submit the name string “Mr. Bartholomew (bart) Lorang” to the Name Normalizer JSON endpoint via the q parameter, it will return the following response:

You can find detailed instructions and more examples in our new FullContact API docs.

Getting started with the FullContact Name Normalization endpoint couldn’t be easier.

1. Sign-up for a Free API Key.
2. Submit a query to the Name Normalizer, passing the name string via the q parameter.
3. Receive structured name data in either JSON or XML.

Turn your messy, free form name data into structured name data using this powerful new endpoint. And if you don’t have one yet, sign-up for a free FullContact API key, try it out, and let us know what you think!

I just “pivoted.”

Four weeks ago, I had never heard of a “pivot” as it is used in startup life. Now, I head up business development at FullContact and I get subjected to the word “pivot” on a daily basis.

Suddenly, I am bombarded with quotations from Brad Feld and David Cohen. My colleagues tell me about FullContact’s numerous pivots. After two days on the job, I have realized something else: not only do I work for a startup, but my whole life has been one giant startup.

My pregnant wife is watching me write this right now and I can see the question in her eyes: “You are 33 fricking years old and a soon you will be a father. What do you mean your life is a start-up?” Honey (and readers) let me explain.

I find a lot of truth in Steve Blank’s description, “a startup is an organization formed to search for a repeatable and scalable business model,” and “a business model describes how your company creates, delivers and captures value.”

Isn’t that what we all want in life? To find a repeatable and scalable model to create, deliver, and capture value, regardless of how we define that value?

For a long time I had an idea for my startup. But instead of a business, that startup was me. I believed I could take my ability to influence people, my competitive drive, and my strategic thinking to be successful while making a difference. I just needed to find the right opportunity.

The first iteration of the start-up of me was when I transitioned from the Marine Corps to the civilian world as an operations manager for a manufacturer. I successfully turned around an operation that had never operated profitably into one that was as profitable as the other segments in the company.

Great start, right? But I didn’t feel that I was working at my full potential or that I was on the path to do so. My impact was limited to the my team. It was not scaleable and I didn’t think it was repeatable. I was in an industry that was incredibly hard hit by the recession and I could only improve efficiency so much. Finally, I wasn’t taking full advantage of my strengths. I could do more.

This led to my first pivot, though I did not put it in those terms at the time. An opportunity arose with the same company to leverage what I had learned about the product and all of my strengths as the Vice President of Commercial Sales.

Again, I saw initial progress towards my goal and believed I was on the right track. But as time went on it became clear that this path was not going to lead me to where I wanted to go either. While it was sustainable, it was not scalable. I reported directly to the CEO, he wasn’t going to go anywhere, and the company was not going to grow anywhere near the rate it had previously.

As fate would have it, that is when FullContact came into the picture.

So I pivoted.

I took lessons learned, strengths gained, and failures experienced to go after an opportunity that presented itself and was aligned with all of those elements.
Just like a smart start-up.

It is a lesson I think everyone can apply to his or her life. Do not hesitate to pivot. Keep your desired end state in mind and when you hit surfaces find the gaps (we’ll talk about that later), even if it means you have to make a major course correction. Make sure you are sustainable, scalable, and creating value. Your life is a start-up and as I hear the new boss say all the time, “Do More Faster.”

FullContact provides a wealth of contact information about your users, but up until now the only way to query for that information was to pass our Person Lookup API an email address. This is great when you have an email address for every one of your users, but what if you don’t? Today we’re proud to announce the release of Twitter name lookup for the FullContact API, enabling developers to query for contact information using a Twitter name.

Performing a Twitter Lookup

If you’re already using the FullContact API, performing a Twitter lookup is as easy as passing the Twitter name you’re querying to our V2 Person endpoint using the twitter parameter. If you’re not yet a user, head on over to our API Signup Page to get your free API key (This includes 3000 queries to our V2 person endpoint, a $100 value). Once you have your key, you can test the API directly in your browser using the following URL (replace the “xxxx” value for the apiKey parameter with your API key).

This request will return enhanced social contact information for the Twitter name @lorangb. When querying by Twitter name, make sure to only include the alpha-numeric portion of the name (everything after the @ symbol). It’s also possible to pass the Twitter name via the X-TWITTER property of a vCard request.

Response Data

The response will be returned in the same format as the standard email lookup. You can change the response format by replacing .json with .html, .xml, or .vcf. Reference our new V2 API Docs for example API responses and more detailed instructions. You can also use our Live API Console to test the new Twitter name lookup from within your browser.

You may notice that for some queries, the response data for an email address search will return a different amount of information than a query for an associated Twitter name. We are working as hard as we can to make sure that the response data is consistant regardless of which parameter you’re using to perform the lookup. Because of this, we recommend defaulting to an email query when an email address is available, to ensure that the most information possible is returned.

More To Come…

Lookup by Twitter name is the first in a series of new lookup parameters we’ll be releasing. Stay tuned to this blog, and follow us on Twitter at @FullContactAPI for the latest announcements. And if you’re not yet a FullContact user, sign up for a free API key, test it out, and let us know what you think!

Without well designed docs, even RESTful APIs like ours can be difficult to use. In tandem with the release of the Version 2 FullContact API, we’ve spent that past few weeks improving our API docs with a brand new design, new navigation, more detailed information, and a live API console.

Version 2 API Docs

Our new docs have been redesigned from the ground up. The the first thing you’ll notice is the floating navigation module. Doc pages tend to be long, so we created a JavaScript navigation bar that follows you down the page, as you scroll. We’ve also added tags to each section of the documentation, indicating whether an endpoint is free or paid. Currently all of our endpoints are free to use except for the Person endpoint, which provides enhanced contact information based on an email address or Twitter name. (We’ll be releasing more information about our Name Stats, Name Normalization, Name Parser, and other new endpoints in the coming weeks. Follow @FullContactAPI on Twitter for updates on the latest releases.)

The documentation for each endpoint begins with a high-level overview, describing the basic functionality, input parameters, and responses. Example API requests are provided for each response format, including JSON, XML, HTML, and vCard.

The parameters section contains descriptions of each available input parameter for a given endpoint. For example, the Person method requires that either an email address, twitter name, or phone number is submitted as input. Other parameters, such as webhookUrl, timeoutSeconds, queue, and callback are optional, and should only be used in certain contexts.

Example API responses are provided for each response format as well. Click the pill-shaped tabs across the top of the Responses table to toggle between JSON, XML, HTML, and vCard formats.

Live API Console

Our new Live API Console makes it easy to test the FullContact API methods right from within your browser. Once you’ve signed up for a free API key, navigate to the Live API Console page, follow the directions below the console, and start using the FullContact API endpoints immediately. We suggest you open the API docs in one browser window and the API console in another, so you can reference the docs while you make live test calls to the API. Once a request is successfully made, you’ll be able to inspect the raw HTTP request and response data from tabs within the console.

Over the coming weeks we will continue to update and enhance our API docs. We’ll also be rolling out blog posts describing how to use our new endpoints. If you have any feedback or suggestions email me at robbie@fullcontact.com, and whatever you do, don’t be a grin fucker.

]]> http://www.fullcontact.com/2012/02/09/new-fullcontact-api-docs-and-api-console-released/feed/ 0 http://www.fullcontact.com/2012/02/04/dont-get-grinfucked-by-your-users/ http://www.fullcontact.com/2012/02/04/dont-get-grinfucked-by-your-users/#comments Sat, 04 Feb 2012 18:08:49 +0000 Bart Lorang http://fullcontact.com/?p=714 Continue reading...]]> I woke up this morning and I couldn’t stop thinking about how evil “sugar coated” feedback is when trying to build great software – especially from end users. It drives me crazy when I know someone is holding something back.

Coincidentally, a few minutes later, I read Brad Feld’s post on grinfucking and Mark Suster’s Don’t be a Grin Fucker.

Both posts are spot on. Our team met one-on-one with Suster for 15 minutes during TechStars Boulder 2011 and we really appreciated his candor. He gave us some honest, direct feedback that rattled around in my brain for the next few weeks. Now, that piece of feedback is an important part of our current strategy.

Part of the magic of TechStars is its “no bullshit” culture based on brutal feedback and intellectual honesty. David Cohen has done a great job instilling these principles into every TechStars founder, employee and mentor.

Unfortunately TechStars ended, and we had to rejoin the human race. Now, I find myself encountering way too much “sugar coating” – but now I think I prefer the term grinfucking.

I tend to meet with lots of people every day, in person, on the phone or via email. I encourage entrepreneurs to Tungle Me if they want a quick 15 minute mentorship session. I find that helping others with their problems serves as a sort of ‘mental gymnastics’ and keeps me ready to solve the most difficult challenges at my own company.

No matter who I meet with, at the end of the meeting I usually show the other person what I’m doing. It used to be our website. Then our API. Now it’s our new iOS app that we are currently iterating on.

I’m finding that a most people naturally try to grinfuck me by being polite about our software. I literally have to draw their feedback out by saying:

I’m going to watch you use our iOS App and take notes. Tell me exactly what you’re thinking as you install it and use it for the first time. I’m not going to say a word.

Usually, this is followed by some hesitation and I have to reassure them by saying:

You can’t hurt my feelings. I went through TechStars – we CRAVE brutal honesty. I’ll get upset if you sugarcoat anything. Hit me!

If they’re still hesitant, I usually remind them that I just gave them brutally honest feedback in some way, shape or form, and they should repay the favor. This usually does the trick.

What transpires next is magical.

Watching a stranger use your app for the first time is always incredibly humbling. But if you can get them to provide a stream-of-consciousness commentary while doing it? It can blow your mind and open your eyes. Usability issues scream out and are inherently obvious. Features that the entire company (including myself) thought were smart end up being dumb features and vice versa.

If you do this over and over, you’ll collect enough feedback to have some real, actionable data.

If you’re not ready for it, the process can hurt your feelings. But there’s no crying in baseball. And I guarantee the process will make your product better. After enough iterations, the feedback focuses on smaller details. That means your product is getting better. You’re making progress.

In short, don’t let users grinfuck you. As Steve Blank espouses, get out of your own building and make sure you get honest feedback about your product.

Have you got feedback for us about our iOS App? Download it, and email me your honest thoughts, good or bad. It’s just data to me and won’t hurt my feelings.

Just don’t be a grinfucker.

So we’re giving it another shot! You should too! If you submitted last time, we encourage you to resubmit – if you have questions, feel free to email robbie@fullcontact.com.

The winning app will receive a cash prize of $750, second place will receive $250.

In order to participate, head on over to CloudSpokes and sign up for a free account. Once you have your account, visit the FullContact challenge page to enter the competition. The winner will be chosen on February 12th.

Resources

• Visit the FullContest challenge page and sign-up for a free CloudSpokes account.
• Checkout our brand new FullContact jQuery plugin on github. This will come in handy on this project.

Screenshots

FullContact API Version 2 provides new data as well as much needed enhancements to the original Version 1 FullContact API. We’ve added a new section to API responses called digitalFootprint, which contains information such as influence topics and social influence scores from Klout. In an effort to make the API response data easier to work with, we’ve standardized the socialProfile fields across all social networks, to use consistent naming conventions. We’ve also removed and renamed various fields throughout the schema. For a detailed description of these changes, reference our blog post on Upcoming Changes To Our V1 Schema. Also, make sure you check out our new API documentation for detailed descriptions, example queries, and API responses.

If you’re a current FullContact API user it’s likely that you’re still using our original Version 1 Person API endpoint. We’ll be phasing out the Version 1 API on February 29th, 2012. We urge you to update your code to use the Version 2 Person API as quickly as possible, in most cases the code changes needed will be straightforward and minimal. Reference our Version 2 API documentation, our blog post on Upcoming Changes To Our V1 Schema, or email me directly at robbie@fullcontact.com if you need further help upgrading to Version 2.

We’ll be rolling out new API endpoints over the coming weeks. Stay tuned to the FullContact blog and follow us on Twitter @FullContactAPI for our latest releases. Many of our new APIs will be free to use, all you need to do is sign-up for a free FullContact Developer API Key to get started.

‘Why Bart, why?’, you ask?

In case you’ve been living under a rock the past few months, Denver Broncos Quarterback Tim Tebow has made headlines with his miraculous fourth-quarter comebacks and his sometimes-awful, sometimes-great play. As a Broncos fan, it’s been a special kind of torture.

Last week, Tim Tebow led the Denver Broncos past the Pittsburgh Steelers in one of the biggest upsets in Playoff history. Judging from my twitter stream during the game, I think I nearly suffered a heart attack.

Tomorrow night, Tebow and the Broncos take on 3-time Superbowl champ Tom Brady and the New England Patriots in what will surely be an epic playoff matchup. I have yet to decide if I’m going to watch the game from home or head to the Lazy Dog in Boulder. It’ll be a game time decision.

But I digress.

Tim Tebow’s prowess as a role model has been well documented. He’s a good kid that doesn’t drink or do drugs, is “saving himself” for marriage, has unbelievable work ethic and isn’t afraid to stand up for what he believes in. He’s also a 2-time BCS champion and the only true college sophomore to ever win the Heisman.

Recently, I’ve been thinking about Tebow through the the lens of my role as “startup founder.”

Tim Tebow is facing the same challenges most startups face. Let me elaborate.

Unorthodox Technique

Tebow has been widely panned by critics for his awkward, unconventional throwing motion. His motion is elongated and does not have the traditional quick-release of Aaron Rodgers or Drew Brees. In addition, Tebow runs the ball like a fullback. Brian Urlacher, the future Hall-of-Fame Chicago Bears middle linebacker, called him a “good running back.”

But Tebow gets the job done. He wins football games and he makes fans happy.

Like Tebow, startups don’t have picture perfect form. They are not well-oiled machines. Startups are scrappy. They are unorthodox. They don’t do things the “normal” way. And that’s fine.

Fred Wilson recently wrote that he knows a startup is onto something when it is Mocked and Misunderstood.

Well, Tim Tebow has been mocked mercilessly – there’s even an SNL parody out there.

So don’t worry about your startup’s unorthodox technique. All that matters is that you get the job done and keep customers happy. Like Tebow, worry about perfecting your form later.

Non-believers

Former NFL Players relentlessly criticize Tim Tebow. Merril Hoge called him an “Awful Quarterback.” Trent Dilfer said “Tebow couldn’t play in the NFL.” The list goes on.

What does Tebow do in response? He simply uses it as fuel for motivation.

Startups face this every day. When I tell people that we’re trying to solve the world’s contact information problem – I can’t count how many times I’ve seen doubt in their eyes. But it doesn’t deter me – it fuels me and it fuels our entire team.

As a startup, don’t let the non-believers, detractors and the naysayers get you down. Use it as motivational fuel instead.

Vanity metrics? Or metrics that matter?

The NFL establishment continue to judge Tebow based on traditional metrics like passing completion percentage, yards, touchdowns and QB rating. But the only real stat that matters in football is “games won.”

Tebow is at the bottom of the league in traditional passing metrics, but for an 8 game stretch he was 7-1. The only other QB who had more wins during that time was Aaron Rodgers.

Startups often report vanity metrics – “X number of PageViews” or “Y number of Users.” But that doesn’t mean startups are actually solving real problems and providing real value.

Like Tebow, startups should focus on metrics that matter.

The Team

Tim Tebow understands that it’s all about the team. Most investors in startups would agree. It’s about 1) The Team 2) The Team and 3) The Team.

Building am effective team during the early stages of a startup is difficult. One bad apple can spoil the bunch. That’s why Brandon Lloyd was traded to the St. Louis Rams when Tebow got the starting nod. Lloyd was a bad apple that didn’t want to play with Tebow. He finished the season with the Rams. Needless to say, the Rams didn’t make the playoffs. Tebow and the Broncos did.

Tebow recently said: “If you believe, unbelievable things can sometimes be possible. I think that’s pretty special that we have a team that constantly believes and believes in each other.”

At a startup, you need to believe in one another. Unwavering faith in your teammates, your mission and the belief that together, you will achieve your common goals is unbelievably important.

I’ll close by letting you watch this video, created after Tim Tebow’s days as a Florida Gator. It gives me chills.

Go Broncos.

If you’re currently using our V1 API endpoint, make sure you update your code to reflect these changes. The new V2 API endpoint is currently live at http://api.fullcontact.com/v2/person.json?email=[email]&apiKey=[your key]. We’ve also created a schema update doc, a color coded JSON doc, and an example JSON response for you to test your code against.

Standard Social Profile

Social profile data has been standardized to conform to the following format and naming conventions.

Example:

socialProfile: {
    "url": [public URL to social profile],
    "id": [user Id of profile],
    "type": [old type - to be deprecated],
    "typeId": [typeId = standardized type],
    "typeName": [friendly typeName],
    "username": "[user’s username]",
    "bio": [short tagline/bio/headline on network],
    "rss": [RSS feed, if available]
    "following": [how many people person is following]
    "followers": [how many people are following person]
}

Field Name Changes and Removals

The following fields have been removed or renamed:

• We’re removing the birthday and facebookUsername fields from the Facebook social profile.
• We’re removing profile_url, facebookUsername, twitterUsername, facebookId, created_at, known, slug, and time_zone from the Plancast social profile.
• We’re removing profileId from the Google Plus social profile. The title field is going to be renamed to bio.
• We’re removing twitterUsername, twitterScreenname, twitterId, and extrenalUrl from the Twitter social profile.
• We’re removing connections on LinkedIn. We’re adding followers and following. The headline field is going to be renamed to bio.
• We’re removing message from Tungle.me.
• We’re removing the icon, about, name, and user_id fields from Digg. The about field will be renamed to bio.
• We’re removing short_bio, name, ext_api_urls, sessions_attending, sessions_speaking, sessions_tracking, attending, speaking, and tracking from Lanyrd. The about field will be renamed to bio.
• We’re removing the myspaceUsername field from the Myspace social profile. The id field will now contain the actual Myspace id instead of the entire string.

digitalFootprint

We’ve added a digitalFootprint node to the response, which contains influence scores and topics from Klout. All topic and score related information is being moved to this node.

Klout Score Types

• general
• amplification
• reach
• network

Example:

digitalFootprint: {
    "scores": {
        {
            "value":45,
            "provider": "klout",
            "type": "general"
        }
    },
    "topics": {
        {
            "value": "techstars",
            "provider": "klout"
        },
        {
            "value": "angel investing",
            "provider": "klout"
        }
    }
}

Relocating Website URLs to contactInfo.websites

The following fields will now be found under contactInfo.websites, which contains a collection of non social profile urls associated with this person.

• angellist.blogUrl
• gravatar.blogUrl
• twitter.externalUrl
• github.blogUrl

Example:

"contactInfo": {
    "familyName": "Lorang",
    "givenName": "Bart",
    "fullName": "Bart Lorang",
    "websites":
    [
        "http://www.bartlorang.com"
    ]
}

Support

We understand that by making these schema changes we will inevitably be affecting code that’s already been written. We strive to get things right the first time, however in this case we made some mistakes early on that have to be fixed now. If you have any questions about this update make sure to reference the schema update doc, the color coded JSON doc, the example JSON response, or send me an email and I’ll be glad to help.

I liked David’s point about downtime – it doesn’t matter to customers whether the downtime was “scheduled” or “unscheduled” — just that it’s down. Thus, cloud software providers should be measured by total downtime and not a metric engineered to get providers off the hook for SLA compliance.

I’ve always believed in transparency about uptime. Recently, we experienced some significant downtime, which resulted in this post by our CTO about his desire for a chaos monkey.

In an effort to be transparent about our operations, we launched status.fullcontact.com a several months ago and wrote about it here.

Unfortunately, I’m disappointed in our results. Our API was only up 99.84% of the time (about 6 hours of downtime) since August 16th, 2011. During that time, we also deployed over 400 automated builds to production (or about 4 per day). We will strive to do better in 2012.