1<html><body> 2<style> 3 4body, h1, h2, h3, div, span, p, pre, a { 5 margin: 0; 6 padding: 0; 7 border: 0; 8 font-weight: inherit; 9 font-style: inherit; 10 font-size: 100%; 11 font-family: inherit; 12 vertical-align: baseline; 13} 14 15body { 16 font-size: 13px; 17 padding: 1em; 18} 19 20h1 { 21 font-size: 26px; 22 margin-bottom: 1em; 23} 24 25h2 { 26 font-size: 24px; 27 margin-bottom: 1em; 28} 29 30h3 { 31 font-size: 20px; 32 margin-bottom: 1em; 33 margin-top: 1em; 34} 35 36pre, code { 37 line-height: 1.5; 38 font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace; 39} 40 41pre { 42 margin-top: 0.5em; 43} 44 45h1, h2, h3, p { 46 font-family: Arial, sans serif; 47} 48 49h1, h2, h3 { 50 border-bottom: solid #CCC 1px; 51} 52 53.toc_element { 54 margin-top: 0.5em; 55} 56 57.firstline { 58 margin-left: 2 em; 59} 60 61.method { 62 margin-top: 1em; 63 border: solid 1px #CCC; 64 padding: 1em; 65 background: #EEE; 66} 67 68.details { 69 font-weight: bold; 70 font-size: 14px; 71} 72 73</style> 74 75<h1><a href="domainsrdap_v1.html">Domains RDAP API</a> . <a href="domainsrdap_v1.v1.html">v1</a></h1> 76<h2>Instance Methods</h2> 77<p class="toc_element"> 78 <code><a href="#close">close()</a></code></p> 79<p class="firstline">Close httplib2 connections.</p> 80<p class="toc_element"> 81 <code><a href="#getDomains">getDomains(x__xgafv=None)</a></code></p> 82<p class="firstline">The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error.</p> 83<p class="toc_element"> 84 <code><a href="#getEntities">getEntities(x__xgafv=None)</a></code></p> 85<p class="firstline">The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error.</p> 86<p class="toc_element"> 87 <code><a href="#getHelp">getHelp(x__xgafv=None)</a></code></p> 88<p class="firstline">Get help information for the RDAP API, including links to documentation.</p> 89<p class="toc_element"> 90 <code><a href="#getIp">getIp(x__xgafv=None)</a></code></p> 91<p class="firstline">The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error.</p> 92<p class="toc_element"> 93 <code><a href="#getNameservers">getNameservers(x__xgafv=None)</a></code></p> 94<p class="firstline">The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error.</p> 95<h3>Method Details</h3> 96<div class="method"> 97 <code class="details" id="close">close()</code> 98 <pre>Close httplib2 connections.</pre> 99</div> 100 101<div class="method"> 102 <code class="details" id="getDomains">getDomains(x__xgafv=None)</code> 103 <pre>The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error. 104 105Args: 106 x__xgafv: string, V1 error format. 107 Allowed values 108 1 - v1 error format 109 2 - v2 error format 110 111Returns: 112 An object of the form: 113 114 { # Response to a general RDAP query. 115 "description": [ # Error description. 116 "A String", 117 ], 118 "errorCode": 42, # Error HTTP code. Example: "501". 119 "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap". 120 "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body. 121 "data": "A String", # The HTTP request/response body as raw binary. 122 "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs. 123 { 124 "a_key": "", # Properties of the object. Contains field @type with type URL. 125 }, 126 ], 127 }, 128 "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6). 129 "notices": [ # Notices applying to this response. 130 { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3). 131 "description": [ # Description of the notice. 132 "A String", 133 ], 134 "links": [ # Link to a document containing more information. 135 { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2). 136 "href": "A String", # Target URL of a link. Example: "http://example.com/previous". 137 "hreflang": "A String", # Language code of a link. Example: "en". 138 "media": "A String", # Media type of the link destination. Example: "screen". 139 "rel": "A String", # Relation type of a link. Example: "previous". 140 "title": "A String", # Title of this link. Example: "title". 141 "type": "A String", # Content type of the link. Example: "application/json". 142 "value": "A String", # URL giving context for the link. Example: "http://example.com/current". 143 }, 144 ], 145 "title": "A String", # Title of a notice. Example: "Terms of Service". 146 "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons". 147 }, 148 ], 149 "rdapConformance": [ # RDAP conformance level. 150 "A String", 151 ], 152 "title": "A String", # Error title. 153}</pre> 154</div> 155 156<div class="method"> 157 <code class="details" id="getEntities">getEntities(x__xgafv=None)</code> 158 <pre>The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error. 159 160Args: 161 x__xgafv: string, V1 error format. 162 Allowed values 163 1 - v1 error format 164 2 - v2 error format 165 166Returns: 167 An object of the form: 168 169 { # Response to a general RDAP query. 170 "description": [ # Error description. 171 "A String", 172 ], 173 "errorCode": 42, # Error HTTP code. Example: "501". 174 "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap". 175 "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body. 176 "data": "A String", # The HTTP request/response body as raw binary. 177 "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs. 178 { 179 "a_key": "", # Properties of the object. Contains field @type with type URL. 180 }, 181 ], 182 }, 183 "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6). 184 "notices": [ # Notices applying to this response. 185 { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3). 186 "description": [ # Description of the notice. 187 "A String", 188 ], 189 "links": [ # Link to a document containing more information. 190 { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2). 191 "href": "A String", # Target URL of a link. Example: "http://example.com/previous". 192 "hreflang": "A String", # Language code of a link. Example: "en". 193 "media": "A String", # Media type of the link destination. Example: "screen". 194 "rel": "A String", # Relation type of a link. Example: "previous". 195 "title": "A String", # Title of this link. Example: "title". 196 "type": "A String", # Content type of the link. Example: "application/json". 197 "value": "A String", # URL giving context for the link. Example: "http://example.com/current". 198 }, 199 ], 200 "title": "A String", # Title of a notice. Example: "Terms of Service". 201 "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons". 202 }, 203 ], 204 "rdapConformance": [ # RDAP conformance level. 205 "A String", 206 ], 207 "title": "A String", # Error title. 208}</pre> 209</div> 210 211<div class="method"> 212 <code class="details" id="getHelp">getHelp(x__xgafv=None)</code> 213 <pre>Get help information for the RDAP API, including links to documentation. 214 215Args: 216 x__xgafv: string, V1 error format. 217 Allowed values 218 1 - v1 error format 219 2 - v2 error format 220 221Returns: 222 An object of the form: 223 224 { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. 225 "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body. 226 "data": "A String", # The HTTP request/response body as raw binary. 227 "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs. 228 { 229 "a_key": "", # Properties of the object. Contains field @type with type URL. 230 }, 231 ], 232}</pre> 233</div> 234 235<div class="method"> 236 <code class="details" id="getIp">getIp(x__xgafv=None)</code> 237 <pre>The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error. 238 239Args: 240 x__xgafv: string, V1 error format. 241 Allowed values 242 1 - v1 error format 243 2 - v2 error format 244 245Returns: 246 An object of the form: 247 248 { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. 249 "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body. 250 "data": "A String", # The HTTP request/response body as raw binary. 251 "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs. 252 { 253 "a_key": "", # Properties of the object. Contains field @type with type URL. 254 }, 255 ], 256}</pre> 257</div> 258 259<div class="method"> 260 <code class="details" id="getNameservers">getNameservers(x__xgafv=None)</code> 261 <pre>The RDAP API recognizes this command from the RDAP specification but does not support it. The response is a formatted 501 error. 262 263Args: 264 x__xgafv: string, V1 error format. 265 Allowed values 266 1 - v1 error format 267 2 - v2 error format 268 269Returns: 270 An object of the form: 271 272 { # Response to a general RDAP query. 273 "description": [ # Error description. 274 "A String", 275 ], 276 "errorCode": 42, # Error HTTP code. Example: "501". 277 "jsonResponse": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # HTTP response with content type set to "application/json+rdap". 278 "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body. 279 "data": "A String", # The HTTP request/response body as raw binary. 280 "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs. 281 { 282 "a_key": "", # Properties of the object. Contains field @type with type URL. 283 }, 284 ], 285 }, 286 "lang": "A String", # Error language code. Error response info fields are defined in [section 6 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-6). 287 "notices": [ # Notices applying to this response. 288 { # Notices object defined in [section 4.3 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.3). 289 "description": [ # Description of the notice. 290 "A String", 291 ], 292 "links": [ # Link to a document containing more information. 293 { # Links object defined in [section 4.2 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-4.2). 294 "href": "A String", # Target URL of a link. Example: "http://example.com/previous". 295 "hreflang": "A String", # Language code of a link. Example: "en". 296 "media": "A String", # Media type of the link destination. Example: "screen". 297 "rel": "A String", # Relation type of a link. Example: "previous". 298 "title": "A String", # Title of this link. Example: "title". 299 "type": "A String", # Content type of the link. Example: "application/json". 300 "value": "A String", # URL giving context for the link. Example: "http://example.com/current". 301 }, 302 ], 303 "title": "A String", # Title of a notice. Example: "Terms of Service". 304 "type": "A String", # Type values defined in [section 10.2.1 of RFC 7483](https://tools.ietf.org/html/rfc7483#section-10.2.1) specific to a whole response: "result set truncated due to authorization", "result set truncated due to excessive load", "result set truncated due to unexplainable reasons". 305 }, 306 ], 307 "rdapConformance": [ # RDAP conformance level. 308 "A String", 309 ], 310 "title": "A String", # Error title. 311}</pre> 312</div> 313 314</body></html>