GET
/
v1
/
projects
curl --request GET \
  --url https://api.chainstack.com/v1/projects/ \
  --header 'Authorization: Bearer <token>'
{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "id": "PR-123-456",
      "name": "My public chain project",
      "type": "public",
      "networks": 0,
      "created_at": "2020-06-15T07:38:00.747Z",
      "creator": {
        "id": "UR-111-111-111",
        "email": "john.smith@example.com",
        "first_name": "John",
        "last_name": "Smith",
        "organization": {
          "id": "RG-123-456",
          "name": "My organization"
        }
      }
    }
  ]
}

Authorizations

​
Authorization
string
header
required

Chainstack API uses API keys to authenticate requests. You can view and manage your API keys in the platform UI. Your API keys carry many privileges, so be sure to keep them secure! Provide your API key as the Authorization header. The value of the header consists of Bearer prefix and secret key generated through the platform UI.

curl -X GET 'https://api.chainstack.com/v1/organization/' \
--header 'Authorization: Bearer FX7CWlLg.FMpAO8cgCX2N7s41EncRru2nb5CmTZUt'

All API requests must be made over HTTPS.

Query Parameters

​
order_by
enum<string>

Which field to use when ordering the results. <br> Use the - prefix to perform descending ordering (-name).

Available options:
name,
created_at
​
page
integer

A page number within the paginated result set.

​
organization
string

Filter by organization ID.

​
name
string

Filter by name.

​
type
enum<string>

Filter by project type.

Available options:
public

Response

200 - application/json
​
count
integer

Number of the objects in the paginated results.

Example:

123

​
next
string | null

Link to the next page.

​
previous
string | null

Link to the previous page.

​
results
object[]