Design https post script to email and enter database

HTTPS notifications When notifications are delivered via HTTPS, for every lead our systems will issue an HTTPS POST request to a given, pre-configured URL. All the fields that are part of the notification (so all the mandatory fields and the optional fields that were filled-in by the user) are sent in the request body, encoded using the application/x-www-form-urlencoded format. The receiving server should handle the request accordingly and respond with plain text “OK”, using HTTP code 200 If Google fails to reach the server, or the server doesn’t respond in the way described above, we will try again after some time. The exact time or number of retry attempts are subject to change. The lead is not considered delivered until we have received a response described above at least once. Please note that client systems should be ready to handle a scenario where a particular lead gets delivered more than once, that is more than one HTTPS request with the same lead_id field value is issued. Names used as keys in the request body can be found in the table on the following page. In the same table we provide details on format of the fields. All integers sent in a request will be non-negative, with no sign at the beginning (e.g. “123”).