# HTTP API methods

Krypc supports a subset of these which are detailed in this section.

### Arguments <a href="#arguments" id="arguments"></a>

Arguments are added through the special query string key `arg`:

```bash
curl -X POST -u "<API_KEY>:<API_KEY_SECRET>" "https://https://Krypc/api/v0/cat?arg=QmeGAVddnBSnKc1DLE7DLV9uuTqo5F7QbaveTjr45JUdQn"
```

Note:`arg` can be used multiple times to signify multiple arguments.

### Flags <a href="#flags" id="flags"></a>

Flags commonly used with the IPFS CLI are added through the query string. For example, the `--encoding=json` flag is the `&encoding=json` query parameter below:

```bash
> curl -X POST -u "<API_KEY>:<API_KEY_SECRET>" "https://ipfs.krypc.io:5001/api/v0/object/get?arg=QmaaqrHyAQm7gALkRW8DcfGX3u8q9rWKnxEMmf7m9z515w&encoding=json"
{
  "Links": [
    {
      "Name": "index.html",
      "Hash": "QmYftndCvcEiuSZRX7njywX2AGSeHY2ASa7VryCq1mKwEw",
      "Size": 1700
    },
    {
      "Name": "static",
      "Hash": "QmdtWFiasJeh2ymW3TD2cLHYxn1ryTuWoNpwieFyJriGTS",
      "Size": 2428803
    }
  ],
  "Data": "CAE="
}
```

### HTTP status codes <a href="#http-status-codes" id="http-status-codes"></a>

Status codes used at the RPC layer are simple:

* `200` - The request was processed or is being processed (streaming)
* `500` - RPC endpoint returned an error
* `400` - Malformed RPC, argument type error, etc
* `403` - RPC call forbidden
* `404` - RPC endpoint doesn't exist
* `405` - HTTP Method Not Allowed

Status code `500` means that the requested RPC function *does* exist, but IPFS was not able to fulfill the request because of an error. To know the reason, you have to look at the error message that is usually returned with the body of the response (if no error, check application logs).

Streaming endpoints fail as above, unless they have started streaming. That means they will have sent a `200` status code already. If an error happens during the stream, it will be included in a `Trailer` response header (some endpoints may additionally include an error in the last streamed object).

A `405`error may mean that you are using the wrong HTTP method (i.e. GET instead of POST), or that you are not allowed to call that method (i.e. due to CORS restrictions when making a request from a browser).

### NDJSON responses[​](https://docs.infura.io/networks/ipfs/http-api-methods#ndjson-responses) <a href="#ndjson-responses" id="ndjson-responses"></a>

When a bunch of objects are requested, IPFS returns them in the Newline Delimited JSON, [NDJSON](http://ndjson.org/), format.

This is because the calls are asynchronous and the responses are processed one object at a time.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.krypcore.com/dev-docs/api-reference/infrastructure-apis/ipfs-http-client-apis/http-api-methods.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.