apify 0.4.1 → 0.4.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/VERSION +1 -1
- data/apify.gemspec +1 -1
- data/app/views/apify/api/_protocol.html.erb +1 -1
- metadata +2 -2
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
0.4.
|
|
1
|
+
0.4.2
|
data/apify.gemspec
CHANGED
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
<ul>
|
|
20
20
|
<li>Successful requests are returned with a status of 200 (OK).</li>
|
|
21
21
|
<li>The body of a successful response is always a hash, serialized as JSON.</li>
|
|
22
|
-
<li>Requests that have errors are returned with a status of 500 (internal server error). The body of a error response is an error message in
|
|
22
|
+
<li>Requests that have errors are returned with a status of 500 (internal server error). The body of a error response is an error message in the response's content type (won't be JSON in most cases).</li>
|
|
23
23
|
<li>You can download an example for a successful response value by appending <code>?example=value</code> to the action URL.</li>
|
|
24
24
|
<li>You can download a <a href="http://json-schema.org/">JSON schema</a> for a successful response by appending <code>?schema=value</code> to the URL. The API guarantees that all responses conform to this schema.</li>
|
|
25
25
|
</ul>
|