![]() That message that comes back interactively doesn ot mention "rec_edit" at all. ![]() The minimum amount of information that you would need to provide an update for with the current IPv4 address manually update the IP for you should be able to run the following -Ĭurl must include an `a' parameter, with a value of wl|chl|nul|ban|comm_news|devmode|sec_lvl|ipv46|ob|cache_lvl|fpurge_ts|async|mirage2|img.q|minify|stats|zone_check|zone_ips|zone_ss|vote_ss|app|ip_lkup|set|app_req|app_req_list|app_version|custom_cert_set|custom_cert_purge|custom_cert_load_multi|custom_cert_load|ersubmit|zoneupload|user_notification_remove|pref_set|zone_file_purge|zone_file_refresh|zone_settings "service_mode" - Status of CloudFlare Proxy, 1 = orange cloud, 0 = grey cloud. 1 = Automatic, otherwise, value must in between 10 seconds. "content" - The content of the DNS record, will depend on the the type of record being added ![]() Available by using the rec_load_all call. In addition you must pass the following parameters: Requires the basic parameters described in Section 2.1 of this document. The record will be updated to the data passed through arguments here. Specific actions are described in Section 3 below.Įdit a DNS record for a zone. The "a" specifies which action you'd like to perform. "a" - To define which request is being made, the client should POST an "a" parameter. "email" - The e-mail address associated with the API key. "tkn" - This is the API key made available on your Account page. So just to help get this ball moving in the right direction here are the relevant parts of the api.Īll GET/POST requests should be directed at the client gateway interface, located at:Įvery GET/POST request must include at the following basic parameter(s): There seems to be some confusion on what the valid parameters are for the cloudflare client api. Then change your username(email) and tkn(password) to protect them and whatever other data (put a bogus domain name and IP if you like), and post what URL string format actually works. Get a URL string that actually works for you by trying just in the browser bar. So "a=DIUP" is not valid, and it seems that the suggested "u=username" should still be the old "email=". You must include an `a' parameter, with a value of wl|chl|nul|ban|comm_news|devmode|sec_lvl|ipv46|ob|cache_lvl|fpurge_ts|async|mirage2|img.q|minify|stats|zone_check|zone_ips|zone_ss|vote_ss|app|ip_lkup|set|app_req|app_req_list|app_version|custom_cert_set|custom_cert_purge|custom_cert_load_multi|custom_cert_load|ersubmit|zoneupload|user_notification_remove|pref_set|zone_file_purge|zone_file_refresh|zone_settingsĪdditionally, email and tkn parameters are required. I sent this in a URL to test what comes back: it responded with: E_INVLDINPUT
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |