You can use this API to sell Remodeling.com LLC your quality leads for any home services vertical. For you to partner with Remodeling.com, you need to email us on gate io app and explain how are you going to generate the leads. Once you are setup with Remodeling.com partner program, your account manager will assign for your account an API key, and a secret key. You can use these keys to test our API using the forms below.
The API allows to Ping & Post leads into Remodeling.com system via a RESTful API. You can use any technology you want, we just need you to send our API JSON requests, and parse our JSON responses back. Your leads must be generated through an online form, and posted in realtime to our API.
The Remodeling.com Lead Seller API allows a partner to:
What you need to get started:
If you have a high quality website related to the home services industry, we will help you to increase the monetization of your website.
The ping offers our partners a method to check if we are able to purchase a lead, and how much we are willing to pay for it. The ping will require few parameters including the zipcode, service and few service specific questions' answers. The ping expected payout is not guaranteed and may change in the post. Your lead's final payout is included in the post response, not in the ping. This does not happen often, but it occurs when we compute the ping expected commission assuming that this lead is going to be sold to two buyers. However, if one of those buyers had this lead before or rejected this lead due to certain validation rules they have then our post commission will be lower. If you are going to sell us a shared lead, you must include the SHA1 encoded phone numbers for each contractor you are selling this lead, and the available number of legs.
The Post API call receives your entire lead. We will reject duplicate and invalid leads, and we will indicate the reason in the post response.
Every single request must include in the header the following parameters:
The Request-Signature is a combination of the Base64 encoded unix timestamp, and the SHA1 of the encoded unix timestamp and your secret key. Just to clarify the authentication process, let us assume the following:
Current time = 20 Jul 2016 05:19:04 PDT -07:00
secret key = wtZ58cHvhwkCjZ5L-VKkl_A_oHZus05-b3V3ZGvh3X4 (will be provided by your account manager)
Then the Unix timestamp is 1469017144, and the encoded unix timestamp is MTQ2OTAxNzE0NA==
Request-Signature = encoded_unix_timestamp--SHA1(secret_key, encoded_unix_timestamp), then:
Request-Signature = MTQ2OTAxNzE0NA==--b97f48255b4f2bca4d78e5ace45dae091866c1b1.
* Notice that we concatenated the encoded unix timestamp with the SHA1 encoded string using two hyphens.
Considering our usage of timestamps, you need to update the signature with every request as we are going to invalidate requests after very few minutes.