The FullContact Developer API is used to manage and enhance contact information. Use our API to provide social profiles in your app, improve contacts in address books, enrich CRM information, or create highly personalized marketing campaigns.
Our API is RESTful and must be queried with HTTP GET or HTTP POST requests. Responses are delivered in JSON or XML format. Some endpoints support HTML or vCard formatted responses. You will need to sign up for a free account to get an API Key and get started.
All successful responses are returned in JSON, XML, HTML or sometimes vCard, depending on the response format you request. On our paid endpoints, such as Person, you will only be billed for queries that respond with a 200 response code, which indicates that the transaction was completed successfully.
| Status Code | Description |
|---|---|
| 200 OK | Your request processed successfully. |
| 202 Accepted | Your request is currently being processed. You can check again later to see the request has been processed. |
| 400 Bad Request | Your request was malformed. |
| 403 Forbidden | Your API key is invalid, missing, or has exceeded its quota. |
| 404 Not Found | This person was searched in the past 24 hours and nothing was found. |
| 410 Gone | This resource cannot be found. You will receive this status code if you attempt to query our deprecated V1 endpoints. |
| 422 Invalid | Invalid or missing API query paraemeter. |
| 500 Internal Server Error | There was an unexpected error on our server. If you see this please contact support@fullcontact.com. |
Social Network Types
Below is a list of type ids for photos, socialProfiles, and icons returned by the person method.