It's completely FREE to Sign Up and won't take long.






By clicking the button, you agree to the Terms & Conditions, Commercial Agreement , and Privacy Policy.
Get Started!
Already have an account? Login

1LINX HAS YOU COVERED


OUR SOLUTIONS


Create a seamless relationship for your customers by pre-populating their registration information and allowing them to authenticate forms with a single click.

What Matters To You? Conversion Matters.
Don’t lose customers because of a lengthy registration process. There’s no need to keep your customers tied to traditional and long form sign-up processes. With 1Linx’s Click-To-Fill, you can:

Mobile level authentication.
Your customers can bypass passwords, security questions and device-level validation by using information supplied to their mobile carrier to verify their identity.

Increase conversion of new sign-ups with a unique experience.
Click-To-Fill makes conversion at the point of registration exponentially easier and simpler for you and your customers, by obtaining your customer’s information and pre-populating the form - with just 1-click.

Take social engagement to the next level.
Turn a "follower", "fan", or "friend" into valuable customer in your CRM stream.

These are just a few examples of how 1Linx can help solve your business problems.
For more examples or to talk to a sales rep, contact us here.
  • PRICING - SIGN UP TODAY FOR A FREE TEST ACCOUNT

    Pay As You Go -- No Commitments! No Long-Term Contract!

    Starts at $.01 for mobile authentication and up to .10 for the full set of data.

    Sign Up Now »

  • VIEW OUR API HERE »

    The interface is a RESTful JSON API and can be accessed in the following fashion. Note that this API supports submitting the parameters using a GET (shown below) or a POST (required when URI exceeds :

    SAMPLE URL:

    https://api.1linx.com/rest/clicktofill/v2/clickToFill.php? clientId=abcdefgh123456789&serviceDesc=Cleaning&advertiserName= MrClean&returnUrl=http%3A%2F%2Fgoogle.com

    View Our Descriptive Table Here »

    Parameter Req'd Description
    clientId Y An identifier issued by the provider to identify the user of the API
    serviceDesc Y A short description for the service or product you’re offering
    advertiserName Y Advertiser name for the current flow
    returnUrl Y Client’s end point URL to which to redirect the user after the flow is complete. The statusCode/statusDescription posted to this URL will indicate success or a reason for the failure, allowing the client to appropriately inform the user.
    method N Either GET or POST. Indicates whether the response parameters submitted to your returnURL will be via a GET or POST method. If not specified, the method is defaulted to GET.
    config N A JSON encoded array of values in the following format:
    container_ classes CSS classes to apply to the general body of the page, beneath the header
    header_ classes CSS classes to apply to the top portion of the hosted forms, typically a banner
    header_ image_ source A URL. When supplied, the header will load with the referenced image
    mobile_ content_ classes CSS classes to apply to the portion of the page below the top/banner portion on the manual mobile entry page
    contact_ content_ classes CSS classes to apply to the portion of the page below the top/banner portion on the contact page
    field_ container_ classes CSS classes to apply to the DIV within which contains the form input fields
    input_ classes CSS classes to apply to each input field
    submit_ button_ classes CSS classes to apply to the submit button
    mobile_ accept_ button_ classes CSS classes to apply to the accept button in the consent form on the mobile page
    contact_ accept_ button_ classes CSS classes to apply to the accept button on the contact page
    mobile_ cancel_ button_ classes CSS classes to apply to the cancel button in the consent form on the mobile page
    contact_ cancel_ button_ classes CSS classes to apply to the cancel button on the contact page
    mobile_ desc_ text Text string to use on the mobile page for better integration with the path. i.e. "Step 1 : Enter your mobile"
    contact_ desc_ text Text string to use on the contact page for integration with the path. i.e. ‘Step 2 : Enter your contact info’
    requestId N Identifier passed by the client. Recommended to be unique for every request for reconciliation purposes
    scope N This defines the depth of information you would like returned to you. Possible values are,

    • "mobile" - only the customer’s mobile number will be returned, whether provided from the network or from the user’s manual entry.

    • "mobileonly" – only the customer’s mobile number will be returned, only when available from the network.

    • "all" – mobile and contact information will be collected and returned to you

    This defaults to "all" when the value is not provided or when the value is not one of those listed above

    The code snippet below depicts the relationship the above “config” parameters have in affecting how the hosted consent pages are rendered. Below is the template used for the first landing page, which handles the consent modal when network detection is available (see the msg_modal div) as well as the form for manual mobile number entry (see the mobile-form form).

    <body>
    <div id="consent_page" class="<? CONTAINER_CLASS ?>">
    <div class="<? HEADER_CLASS ?>">
    <img src="<? HEADER_IMAGE_SOURCE ?>" width="100%" style="max-width: 640px"/>
    </div>
    <div class="<? MOBILE_CONTENT_CLASSES ?>">
    <form id="mobile-form">
    <div class="<? MOBILE_DESC_CLASSES ?>">
    <? MOBILE_DESC_TEXT ?>
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input id="msisdn" name="msisdn" class="<? INPUT_CLASSES?>" placeholder="Phone Number" value="1"/>
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    We would like to validate your contact info, click the button below to authorize
    s to confirm your contact information, or <a id="reject" href="#">click here</a>
    to cancel
    </div>
    <a id="submitContinue" href="#" class="<? SUBMIT_BUTTON_CLASSES ?>">Submit & Continue</a>
    </form>
    </div>
    </div>

    <!--HIDDEN MESSAGE MODAL-->
    <div id="msg_modal" style="display:none" class="<? MODAL_CLASSES ?>">
    <? MODAL_DESC_TEXT ?>
    <div id="msg_modal_inner" class="<? MODAL_INNER_CLASSES ?>">
    Click the button below to authorize us to confirm your contact information and autofill
    your form. By clicking YES below, you give <span id="operator">your wireless operator</span>
    consent to provide us information about your wireless service including your Wireless
    telephone number. Click <a id="reject" href="#">here</a> to cancel<br/>
    </div>
    <a id="acceptTerms" href="#" class="<? MOBILE_ACCEPT_BUTTON_CLASSES ?>">Yes</a>
    <a id="cancel" href="#" class="<? MOBILE_CANCEL_BUTTON_CLASSES ?>">Cancel</a>
    </div>
    </body>

    Subsequently if the scope is set to “all”, the user is subsequently presented the contact form screen to collect consent to share their name and address information. Below is the template used for this landing page:


    <body>
    <div id="contact_page" class="<? CONTAINER_CLASSES ?>">
    <div class="<? HEADER_CLASSES ?>">
    <img src="<? HEADER_IMAGE_SOURCE ?>" width="100%" style="max-width: 640px"/>
    </div>
    <div class="<? CONTACT_CONTENT_CLASSES ?>">
    <form action="ctf_update.php" id="contactform" method="post">
    <div class="<? CONTACT_DESC_CLASSES ?>">
    <? CONTACT_DESC_TEXT ?>
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="fname" class="<? INPUT_CLASSES ?>" placeholder="First Name" value="John A" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="lname" class="<? INPUT_CLASSES ?>" placeholder="Last Name" value="Smith" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="msisdn" class="<? INPUT_CLASSES ?>" placeholder="Mobile" value="19497262653" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="address1" class="<? INPUT_CLASSES ?>" placeholder="Address" value="123 James St" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="city" class="<? INPUT_CLASSES ?>" placeholder="City" value="San Francisco" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="state_province" class="<? INPUT_CLASSES ?>" placeholder="State/Province" value="CA" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    <input name="zip" class="<? INPUT_CLASSES ?>" placeholder="ZIP" value="941326809" />
    </div>
    <div class="<? FIELD_CONTAINER_CLASSES ?>">
    Click the OK button below to authorize us to update your contact information and
    submit your contact information to fulfill your request. Or <a href="#">click here</a>
    to cancel. By clicking the OK button, I verify this is my phone number and consent
    to receive phone calls regarding SERVICE_DESC from a(n) ADVERTISER_NAME operator using
    an automatic telephone dialing system.
    </div>
    <div class="<? SUBMIT_BUTTON_CONTAINER_CLASSES ?>">
    <a id="acceptTerms" href="#" class="<? CONTACT_ACCEPT_BUTTON_CLASSES ?>">OK</a>
    <a id="cancel" href="#" class="<? CONTACT_CANCEL_BUTTON_CLASSES ?>">Cancel</a>
    </div>
    </form>
    </div>
    </div>
    </body>

    Below shows the screenflows for demonstrating the user experience (Click To Expand):

    Responses

    The response from this API is a JSON encoded body of the following format:

    {
    "statusCode" :0,
    "statusDescription" :"Success",
    "RedirectUrl" :"http:\/\/api.1linx.com\/rest\/clicktofill\/v1\/ctf_mobile.php?session=214081"
    }

    Where:

    statusCode – is a numeric result code (see table on page 7 for full list of status codes)

    statusDescription – is a textual description of the error case

    RedirectUrl – is the URL to which to redirect the user

    After being redirected to the above RedirectUrl, the user will proceed through our hosted consent flow and upon completion, the user will be redirected to the returnUrl provided in the clickToFill API call. This response parameter is passed thru a GET URI parameter or as a POST variable depending on the “method” specified in the original clickToFill API call.

    Note that the result, user’s mobile number and/or contact information are not passed directly to thru the returnUrl. Instead, a unique location is sent to the returnUrl where those properties can be securely retrieved. The response parameter sent to the returnUrl is of the following format:

    Parameter

    Description

    contactUrl

    A URL location from which the user’s contact information can be retrieved


    e.g., if the requested transmission method were GET, the user would be redirected to the following URL:

    http://www.returnUrl.com?statusCode =0&statusDescription=Success&contactUrl=https%3A%2F%2Fapi.1linx.com%2Frest%2Fclicktofill %2Fv1%2Fctf_retrieve.php%3Fsession%3D214104

    Where:

    contactUrl - ‘https://api.1linx.com/rest/clicktofill/v1/ctf_retrieve.php?session=214104’ has been URL-encoded

    In order to retrieve the contact information, the contactUrl must be prepended with the ‘clientId’ URI parameter so that your API call can be authenticated. Note that this call must be a server-to-server call in order to protect your clientId from being exposed in your site’s source code. Below is a example:

    https://api.1linx.com/rest/clicktofill/v1/ctf_retrieve.php?session=214104&clientId=abcdefgh123456789

    The response from requesting the contactUrl is a JSON encoded body of the following format, dependent on the ‘scope’ specified in the initial clickToFill API call:

    Scope = “all”

    {
    "fname":"LUIS O",
    "lname" :"HERNANDEZ",
    "msisdn" :"12292881196",
    "address1" :"758 DRAKE AVE APT 108",
    "city" :"LONG BEACH",
    "state_province" :"CA",
    "zip" :"902456809",
    "statusCode" :"0",
    "statusDescription" :"Success",
    "consent_details" :{
    "consented" :"true",
    "consent_time" :"2013-12-15 20:12:17",
    "consent_screenshot_url" :"http:\/\/api.1linx.com\/rest\/clicktofill\/v1\/consentScreens\/2141045_e45c5f68a4287719a23f5cfbcf41835d.png"
    }
    }

    Scope = “mobile”

    {
    "msisdn" :"12123007304",
    "statusCode" :"0",
    "statusDescription" :"Success",
    "consent_details" :{
    "consented" :"true",
    "consent_time" :"2013-12-13 02:57:34",
    "consent_screenshot_url" :"http:\/\/api.1linx.com\/rest\/clicktofill\/v1\/consentScreens\/2095940_9ddcfcfb0d6f804602130beae33eb8d1.png"
    }
    }

    Where:

    statusCode - is a numeric result code (see table below)

    statusDescription - is a textual description of the error case

    msisdn – the mobile number of the subscriber in E164 format (11 digits in North America)

    fname – first initial/name and optionally middle initial/name (eg. ALEX P)

    lname – last name

    address1 – line 1 of the address

    address2 – (Optional) line 2 of the address

    address3 – (Optional) line 3 of the address

    city – city

    state_province – two character state/province abbreviation

    country – US or CANADA

    zip – ZIP (5-9 digits) or Postal Code (6-7 alphanumeric) of the subscriber

    Below is an enumerated list of status codes that can be encountered:

    Status Code

    Status Description

    0

    Success

    103

    Internal Error

    112

    Bad Parameter Missing ClientId

    113

    Bad Parameter Missing serviceDesc

    114

    Bad Parameter Missing advertiserName

    122

    Bad Parameter Invalid ClientId

    203

    Subscriber is unreachable

    301

    Contact information not found

    302

    Operator not supported; no contact information available

    401

    Auto-detection was not available for this customer

    402

    Customer did not consent to mobile detect

    403


    Integration Demo

    To help you with the integration, we’ve created the following demo flow:

    http://www.1linx.com/onlineshopper/hc_index.php

    This flow was constructed from our API with the following parameters (the parameters are encoded in an array and you’ll need to fill in your own clientId),

    array(

    "clientId" => "YOUR_CLIENT_ID",

    "method" => "POST",

    "successUrl" => "http://www.1linx.com/onlineshopper/credit_card.php",

    "cancelUrl" => "http://www.1linx.com/onlineshopper/index.php",

    "config" => json_encode(

    array(

    "title" => "Online Shopper",

    "css" => array(

    "http://www.1linx.com/onlineshopper/style.css"

    ),

    "container_classes" => "container",

    "header_classes" => "header",

    "header_image_source" => "http://www.1linx.com/onlineshopper/images/logo.png",

    "content_classes" => "content",

    "field_container_classes" => "field",

    "input_classes" => "input",

    "submit_button_classes" => "submit",

    "submit_image_source" => "",

    "mobile_desc_text" => "Step 1: Enter you Mobile Number for Validation",

    "contact_desc_text" => "Step 2: Confirm your contact information"

    ))

    );

    Please feel free to visit the above demo site and contact us at support@1linx.com with your questions or concerns.

  • DOWNLOAD OUR API HERE »

Meet them where they are. With our mobile IP Information API you can pinpoint your customer’s location and reach them with advertising that is relevant and meaningful to them.

What Matters To You? Location Matters.
Don’t get lost in unknown territory. You already know that location is a main pillar in the marketing mix and can help inform why, when and how you reach your customers. With 1Linx’s IP Information, you can:

Create a personalized web experience for your customers.
List local deals, promotions and information on local or market specific retailers depending on your customer’s location.

Comply with geographic restrictions.
Allow yourself the freedom of knowing that your promotions are all within market and local affiliate guidelines.

Reduce customer fraud.
Compare IP information to other data associated with the account- like credit card information - and decrease online fraud behavior.

These are just a few examples of how 1Linx can help solve your business problems.
For more examples or to talk to a sales rep, contact us here.
  • PRICING - SIGN UP TODAY FOR A FREE TEST ACCOUNT

    Pay As You Go -- No Commitments! No Long-Term Contract!

    $.0001 per look-up.

    Sign Up Now »

  • VIEW OUR API HERE »

    The interface is a RESTful JSON API and can be accessed in the following fashion:

    SAMPLE URL:

    https://api.1linx.com/rest/ip/v1/ipInfo.php?clientId=abcdefgh123456789&ip=8.8.8.8&hostname=false

    Parameter

    Req’d

    Description

    clientId

    Y

    An identifier issued by the provider to identify the user of the API

    ip

    Y

    IPv4 in dotted decimal format (eg. 192.168.1.1). Note IPv6 is not supported.

    requestId

    N

    Identifier passed by the client. Recommended to be unique for every request for reconciliation purposes

    hostname

    N

    Boolean passed as "true" or "false" indicating whether to resolve the IP’s hostname and return the ‘Hostname’ parameter in the response. Note that this significantly increases the response time since a DNS lookup is required so enable with caution. If the parameter is not provided, the feature is disabled by default.


    Responses

    The response from this API is a JSON encoded body of the following format:

    {
    "Response" :{
    "StatusCode" :0,
    "StatusDescription" :"Success",
    "IP" :"8.8.8.8",
    "Hostname" :"google-public-dns-a.google.com",
    "Latitude" :"38",
    "Longitude" :"-97",
    "Organization" :"AS15169 Google Inc.",
    "Country" :"US"
    }
    }

    Where:

    StatusCode - is a numeric result code

    StatusDescription - is a textual description of the error case

    IP - is the IP information was requested for

    Hostname - (Conditional) the reverse DNS hostname associated with the IP

    Latitude - (Optional) the latitude for the estimated location for the IP. Formatted with double precision.

    Longitude - (Optional) the longitude for the estimated location for the IP. Formatted with double precision.

    Organization - (Optional) Organization/ISP associated with the IP.

    City - (Optional) location city for the IP

    Region - (Optional) location region/state for the IP

    Country - (Optional) location country for the IP

    PhoneAreacode - (Optional) Dialing area code associated with the IP location

    Internal - Either true or false indicating whether the IP is a internal IP.

    Below are the currently supported StatusCode values:

    StatusCode

    StatusDescription

    0

    Success

    103

    Internal Error

    113

    Bad Parameter Missing IP

    123

    Bad Parameter Invalid IP

    120

    Bad Parameter Missing Client Id

    122

    Bad Parameter Invalid Client Id

  • DOWNLOAD OUR API HERE »

Find the right connection. Our Operator Look-Up API allows you to find out the carrier tied to the specific number. This way, you can authenticate the validity of a number and determine if it is a landline, VOIP or mobile number.

For Coverage in US and Canada.

What Matters To You? Quality Matters.
Don’t waste your messages on a customer that can’t receive them! As a marketer you already know the value of quality data. With 1Linx’s Operator Look-Up, you can:

Stop hackers in their tracks.
You’ll receive intelligent data on patterns and the history of the phone type, so you can flag high-risk transactions or outright block them.

Increase the rate of successful calls.
Reduce false leads, improperly formatted numbers, or other inaccurate information - and make you next customer call successful.

Ensure the phone number can receive SMS messages
Operator look-up enables you to know the origin of the number, and - if it’s a mobile number - confirm that the carrier allows for SMS messages

These are just a few examples of how 1Linx can help solve your business problems.
For more examples or to talk to a sales rep, contact us here.
  • PRICING - SIGN UP TODAY FOR A FREE TEST ACCOUNT

    Pay As You Go -- No Commitments! No Long-Term Contract!

    $0.002 per look up. Get 5,000 look-ups for free.

    Sign Up Now »

  • VIEW OUR API HERE »

    The interface is a RESTful JSON API and can be accessed in the following fashion:

    SAMPLE URL:

    http://api.1linx.com/rest/operator/v1/checkOperator.php?clientId=abcdefgh123456789&msisdn=12292881196

    Parameter

    Description

    clientId

    A identifier issued by the provider to identify the user of the API

    msisdn

    The mobile number of the subscriber being verified. The numbers should be in E164 format (11 digits in North America without any "+" characters)

    requestId

    (Optional) Identifier passed by the client. Recommend to be unique for every request for reconciliation purposes

    The response of this API is a JSON encoded body of the following format:

    {"Response":{"StatusCode"0,"StatusDescription":"Success","Operator":"NEXTELUS"}}

    Where:

    StatusCode - is a numeric result code (see table below)

    StatusDescription - is a textual description of the error case

    Operator - is the wireless operator of the mobile number (see table below). If the number is not a mobile number "NONMOBILE" will be returned, where as if the number is not a valid phone number "NOT_VALID" will be returned.

    Below are the currently supported StatusCode values:

    StatusCode

    StatusDescription

    0

    Success

    103

    Internal Error

    110

    Bad Parameter Missing MSISDN

    112

    Bad Parameter Invalid MSISDN

    120

    Bad Parameter Missing ClientId

    122

    Bad Parameter Invalid ClientId

    Below are the currently supported Operator values:

    Operator

    Operator Name

    ACSUS

    ACS Wireless

    ALLWESTUS

    All West Wireless

    ALLIEDUS

    Allied

    ALLTELUS

    Alltel

    CINGULARUS

    AT&T Mobility (formerly Cingular Wireless)

    ATTUS

    AT&T Wireless

    BLUEGRASSUS

    Bluegrass

    BOOSTUS

    Boost

    CTCUS

    Cambridge Telecom

    CELLCOMUS

    Cellcom

    SOUTH CANAAN CELLULARUS

    Cellular One of NE PA

    CELLULARSOUTHUS

    Cellular South

    CENTENNIALUS

    Centennial

    CHARITONUS

    Chariton Valley Cellular

    CHATMOBILITYUS

    Chat Mobility Cellular

    CINBELLUS

    Cincinnati Bell

    COXUS

    Cox Wireless

    CRICKETUS

    Cricket Communications

    CROSSUS

    Cross Wireless

    DENALIUS

    Denali

    DOBSONUS

    Dobson

    DUETIPUS

    Duet IP

    ECITUS

    ECIT - Cellular One of East Central Illinois

    APPALACHIANUS

    EKN - Appalachian Wireless

    ELEMENTUS

    Element Mobile

    EPICTOUCHUS

    Epic Touch

    FARMERSMUTUALUS

    FMTC - Farmer's Mutual Telephone Company

    GCIUS

    GCI - General Communications, Inc

    GOLDENSTATEUS

    Golden State Cellular

    IMMIXUS

    Immix - PC Management

    INLANDUS

    Inland Cellular

    IVCUS

    IVC - Illinois Valley Cellular

    IOWAWIRELESSUS

    iWireless (Iowa Wireless Services)

    METROPCSUS

    Metro PCS

    MOBIPCSUS

    Mobi PCS

    MOBILENATIONUS

    MobileNation

    MOSAICUS

    Mosaic Telecom

    MTPCSUS

    MTPCS

    NEXTECHUS

    Nex-Tech Wireless

    NEXTELUS

    Nextel Communications

    NUCLANATURITAUS

    NNTC - Nucla-Naturita Telephone Company

    NTELOSUS

    nTelos

    NWMISSOURIUS

    NW Missouri Cellular

    PANHANDLEUS

    Panhandle Wireless

    PEOPLESUS

    Peoples Wireless

    PIONEERUS

    Pioneer Wireless

    PLATEAUUS

    Plateau Wireless

    REVOLUS

    Revol Wireless

    RINAUS

    Rural Independent Network Alliance

    GOLDSTARUS

    Silver Star PCS (aka Gold Star)

    SIMMETRYUS

    Simmetry Wireless

    EAGLEUS

    Snake River PCS (aka Eagle Telephone System, Inc)

    SOUTH CENTRAL UTAHUS

    South Central

    SPRINTUS

    Sprint PCS

    SYRINGAUS

    Syringa

    TMOBILEUS

    T-Mobile

    THUMBUS

    Thumb Cellular

    UNITAHBASINUS

    UBET Wireless

    RURALCELUS

    Unicel (formerly Rural Cellular Corp/RCC)

    UNIONUS

    Union Telephone

    UNITEDWIRELESSUS

    United Wireless

    USCELLULARUS

    US Cellular

    VERIZONUS

    Verizon Wireless

    NECOCELLUS

    Viaero Wireless

    VIRGINUS

    Virgin Mobile

    WCENTRALUS

    West Central Wireless

    ALLIANTCA

    Alliant

    BELLCA

    Bell Mobility Canada

    MICROCELLCA

    Microcell

    MTSCA

    MTS

    NORTHTELEPHONECA

    North Telephone

    ROGERSCA

    Rogers

    SASKTELCA

    SaskTel

    TELEBECCA

    Telebec

    TELUSCA

    Telus

    VIRGINCA

    Virgin Canada

  • DOWNLOAD OUR API HERE »

Enrich the quality of your mobile leads with the name and address of the people who click your mobile ads or visits your mobile site.

What Matters to You? Time Matters.
Don’t waste your time verifying prospect and customer information when it can be done automatically. We know how valuable your time is so we want to help you better manage it. With 1Linx’s Subscriber Look-Up you can:

Verify the identity of users -- instantly.
Find out in real-time if you are talking to a real person so your time can be spent on other tasks.

Reduce inaccuracies on outbound fulfillment.
Having a database updated with vetted customer information will ensure that your fulfillment tactics are sent to the right people and addresses.

Create a welcoming customer experience.
Greet your customers personally, during inbound calls

These are just a few examples of how 1Linx can help solve your business problems.
For more examples or to talk to a sales rep, contact us here.
  • PRICING - SIGN UP TODAY FOR A FREE TEST ACCOUNT

    Pay As You Go -- No Commitments! No Long-Term Contract!

    $0.10 per look-up. Get over 100 look-ups for free.

    Sign Up Now »

  • VIEW OUR API HERE »

    The interface is a RESTful JSON API and can be accessed in the following fashion:

    SAMPLE URL:

    https://api.1linx.com/rest/identity/v1/mobileIdentity.php?clientId=abcdefgh123456789&msisdn=12292881196

    Parameter

    Description

    clientId

    A identifier issued by the provider to identify the user of the API

    msisdn

    The mobile number of the subscriber being queried. The numbers should be in E164 format (11 digits in North America without any "+" characters)

    requestId

    (Optional) Identifier passed by the client. Recommend to be unique for every request for reconciliation purposes


    The response of this API is a JSON encoded body of the following format:

    {
    "Response" :{
    "StatusCode" :0,
    "StatusDescription" :"Success",
    "Contact" :{
    "firstname" :"LUIS O",
    "lastname" :"HERNANDEZ",
    "address1" :"758 DRAKE AVE APT 108",
    "address2" :"",
    "address3" :"",
    "city" :"LONG BEACH",
    "state_province" :"CA",
    "country" :"US",
    "zip" :"90245"
    },
    "PhoneType" :"MOBILE"
    }
    }

    Where:

    StatusCode - is a numeric result code (see table below)

    StatusDescription - is a textual description of the error case

    Contact - (Conditional) Is the JSON object containing the contact details of the individual. Details of the fields are provided below:

    firstname - first initial/name and optionally middle initial/name (eg. ALEX P)

    lastname - last name

    address1 - line 1 of the address

    address2 - line 2 of the address where applicable

    address3 - line 3 of the address where applicable

    city - city

    state_province - two character state/province abbreviation

    country - US or CANADA

    zip - ZIP or Postal Code of the subscriber

    PhoneType - (Conditional) enumeration of the type of phone number, possible values are FIXED_LINE, VOIP or MOBILE

    Below are the currently supported StatusCode values:

    StatusCode

    StatusDescription

    0

    Success

    103

    Internal Error

    110

    Bad Parameter Missing MSISDN

    112

    Bad Parameter Invalid MSISDN

    120

    Bad Parameter Missing ClientId

    122

    Bad Parameter Invalid ClientId

    301

    Contact Information not found

    302

    Operator not supported; no contact information available


    Below are the currently supported Operator values:

    Operator

    Operator Name

    ACSUS

    ACS Wireless

    ALLWESTUS

    All West Wireless

    ALLIEDUS

    Allied

    ALLTELUS

    Alltel

    CINGULARUS

    AT&T Mobility (formerly Cingular Wireless)

    ATTUS

    AT&T Wireless

    BLUEGRASSUS

    Bluegrass

    BOOSTUS

    Boost

    CTCUS

    Cambridge Telecom

    CELLCOMUS

    Cellcom

    SOUTH CANAAN CELLULARUS

    Cellular One of NE PA

    CELLULARSOUTHUS

    Cellular South

    CENTENNIALUS

    Centennial

    CHARITONUS

    Chariton Valley Cellular

    CHATMOBILITYUS

    Chat Mobility Cellular

    CINBELLUS

    Cincinnati Bell

    COXUS

    Cox Wireless

    CRICKETUS

    Cricket Communications

    CROSSUS

    Cross Wireless

    DENALIUS

    Denali

    DOBSONUS

    Dobson

    DUETIPUS

    Duet IP

    ECITUS

    ECIT - Cellular One of East Central Illinois

    APPALACHIANUS

    EKN - Appalachian Wireless

    ELEMENTUS

    Element Mobile

    EPICTOUCHUS

    Epic Touch

    FARMERSMUTUALUS

    FMTC - Farmer's Mutual Telephone Company

    GCIUS

    GCI - General Communications, Inc

    GOLDENSTATEUS

    Golden State Cellular

    IMMIXUS

    Immix - PC Management

    INLANDUS

    Inland Cellular

    IVCUS

    IVC - Illinois Valley Cellular

    IOWAWIRELESSUS

    iWireless (Iowa Wireless Services)

    METROPCSUS

    Metro PCS

    MOBIPCSUS

    Mobi PCS

    MOBILENATIONUS

    MobileNation

    MOSAICUS

    Mosaic Telecom

    MTPCSUS

    MTPCS

    NEXTECHUS

    Nex-Tech Wireless

    NEXTELUS

    Nextel Communications

    NUCLANATURITAUS

    NNTC - Nucla-Naturita Telephone Company

    NTELOSUS

    nTelos

    NWMISSOURIUS

    NW Missouri Cellular

    PANHANDLEUS

    Panhandle Wireless

    PEOPLESUS

    Peoples Wireless

    PIONEERUS

    Pioneer Wireless

    PLATEAUUS

    Plateau Wireless

    REVOLUS

    Revol Wireless

    RINAUS

    Rural Independent Network Alliance

    GOLDSTARUS

    Silver Star PCS (aka Gold Star)

    SIMMETRYUS

    Simmetry Wireless

    EAGLEUS

    Snake River PCS (aka Eagle Telephone System, Inc)

    SOUTH CENTRAL UTAHUS

    South Central

    SPRINTUS

    Sprint PCS

    SYRINGAUS

    Syringa

    TMOBILEUS

    T-Mobile

    THUMBUS

    Thumb Cellular

    UNITAHBASINUS

    UBET Wireless

    RURALCELUS

    Unicel (formerly Rural Cellular Corp/RCC)

    UNIONUS

    Union Telephone

    UNITEDWIRELESSUS

    United Wireless

    USCELLULARUS

    US Cellular

    VERIZONUS

    Verizon Wireless

    NECOCELLUS

    Viaero Wireless

    VIRGINUS

    Virgin Mobile

    WCENTRALUS

    West Central Wireless

  • DOWNLOAD OUR API HERE »


ABOUT 1LINX

1Linx provides simple and smart APIs for data. Our solutions are intuitive for implementation and practical for every day use; but what sets us a part is our commitment to quality, focus on enriched data and our continuous innovation on current and future solutions. Headquartered in NY, we are always looking for new ways to provide you with enriched data so you can make creative and logical decisions for your business.

Alykhan Govani

CEO

Favorite Quote:
"Artists give people something they didn’t know they were missing."
- Daniel Pink

Sean Johnson

Content Director

Favorite Quote:
"Anything you can imagine you can create."
- Oprah Winfrey


STAY CONNECTED


    Need a Sales Rep?
    Connect with our Sales Team: sales@1linx.com

    Need Technical Support?
    Connect with our Support Team: support@1linx.com

    Do you have a general inquiry?
    Feel free to fill out the form to the right and we’ll get back to you right away.

  • New York Office
    122 EAST 42ND STREET. SUITE 720 NEW YORK, NY 10168
  • San Francisco Office
    170 COLUMBUS AVE. SUITE 280 SAN FRANCISCO, CA 94133