"content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
                                        "schema": {

				"application/ccxml+xml",
				"application/cea-2018+xml",
				"application/cellml+xml",
				"application/cnrp+xml",
				"application/commonground",
				"application/conference-info+xml",
				"application/cpl+xml",
				"application/csta+xml",
				"application/cstadata+xml",
				"application/cu-seeme",
				"application/cybercash",
				"application/davmount+xml",
				"application/dca-rft",
				"application/dec-dx",

                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            }
                        },
                    }
                },
                "/no_response_model-no_annotation-return_dict": {

application/vnd.ms-powerpoint=powerpoint\n\
application/vnd.openxmlformats-officedocument.presentationml.presentation=powerpoint\n\
application/vnd.oasis.opendocument.text=odt\n\
application/vnd.oasis.opendocument.spreadsheet=ods\n\
application/vnd.oasis.opendocument.presentation=odp\n\
application/pdf=pdf\n\
application/x-fictionbook+xml=fb2\n\
application/e-pub+zip=epub\n\
application/x-ibooks+zip=ibooks\n\

    responses returned by OkHttp itself, and it was an old mistake to permit
    application code to omit a message.

 *  The challenge's scheme and realm are now non-null. If you are calling
    `new Challenge(scheme, realm)` you must provide non-null values. These were
    never null in challenges created by OkHttp, but could have been null in
    application code that creates challenges.

                        .header("Authorization", "Bearer " + user.getAuthenticationResult().accessToken())
                        .header("Accept", "application/json")
                        .header("Content-type", "application/json")
                        .body("{\"securityEnabledOnly\":false}")
                        .execute()) {

g:{},ajaxSettings:{url:Et.href,type:"GET",isLocal:/^(?:about|app|app-storage|.+-extension|file|res|widget):$/.test(Et.protocol),global:!0,processData:!0,async:!0,contentType:"application/x-www-form-urlencoded; charset=UTF-8",accepts:{"*":zt,text:"text/plain",html:"text/html",xml:"application/xml, text/xml",json:"application/json, text/javascript"},contents:{xml:/\bxml\b/,html:/\bhtml/,json:/\bjson\b/},responseFields:{xml:"responseXML",text:"responseText",json:"responseJSON"},converters:{"* text":String,"text...

g:{},ajaxSettings:{url:Et.href,type:"GET",isLocal:/^(?:about|app|app-storage|.+-extension|file|res|widget):$/.test(Et.protocol),global:!0,processData:!0,async:!0,contentType:"application/x-www-form-urlencoded; charset=UTF-8",accepts:{"*":zt,text:"text/plain",html:"text/html",xml:"application/xml, text/xml",json:"application/json, text/javascript"},contents:{xml:/\bxml\b/,html:/\bhtml/,json:/\bjson\b/},responseFields:{xml:"responseXML",text:"responseText",json:"responseJSON"},converters:{"* text":String,"text...

    /**
     * The POST method.
     */
    protected static final String POST = "POST";

    /**
     * The MIME type.
     */
    protected String mimeType = "application/json";

    /**
     * Constructor.
     */
    public SearchApiManager() {
        setPathPrefix("/api/v1");
    }

    /**
     * Registers this API manager.
     */

 *
 *  * http://host
 *
 * Both the unnecessary port specification (`:80`) and the absent trailing slash (`/`) cause URI to
 * bucket the two URLs separately. This harms URI's usefulness in collections. Any application that
 * stores information-per-URL will need to either canonicalize manually, or suffer unnecessary
 * redundancy for such URLs.
 *