### Get Account API Call Example

Source: https://blue-media.stoplight.io/docs/index

This snippet demonstrates how to make a 'Get Account' API call. It requires an 'X-Api-Key' in the header for authentication and an 'AccountID' as a parameter. The expected response is a 200-range status code.

```HTTP
GET /accounts/{AccountID} HTTP/1.1
Host: api.bluems.com
X-Api-Key: YOUR_ACCESS_CODE_SECRET
```

--------------------------------

### Pagination Example with pageToken

Source: https://blue-media.stoplight.io/docs/index

Demonstrates how to use `pageSize` and `pageToken` for paginating API results. When `pageSize` is set and results exceed it, a `pageToken` is returned to fetch subsequent data.

```JSON
{
  "pageSize": 10,
  "pageToken": "nextPageTokenValue"
}
```

--------------------------------

### HTTP GET Request for Information Retrieval

Source: https://blue-media.stoplight.io/docs/index

The GET method is used for retrieving information about your account or environment. The requested information is returned as a JSON object. GET requests are read-only and do not modify any data.

```HTTP
GET /api/resource
```

--------------------------------

### API Key Authentication (Header)

Source: https://blue-media.stoplight.io/docs/index

This method involves including your API key in the header of your API calls. The key should be passed in a parameter named 'X-Api-Key'.

```HTTP
X-Api-Key: 123
```

--------------------------------

### HTTP POST Request for Object Creation

Source: https://blue-media.stoplight.io/docs/index

The POST method is used to create a new object. The request must include all necessary attributes for object creation. Send a POST request to the target endpoint to create a new object.

```HTTP
POST /api/resource
```

--------------------------------

### API Key Authentication (Query)

Source: https://blue-media.stoplight.io/docs/index

This method involves including your API key as a query parameter in your API calls. The parameter should be named 'apiKey'.

```HTTP
?apiKey=123
```

--------------------------------

### HTTP PATCH Request for Partial Resource Modification

Source: https://blue-media.stoplight.io/docs/index

The PATCH method allows for partial modification of resources. Unlike PUT, which typically requires a full resource representation, PATCH requests contain instructions to update only specific attributes.

```HTTP
PATCH /api/resource/{id}
```

--------------------------------

### HTTP DELETE Request for Resource Removal

Source: https://blue-media.stoplight.io/docs/index

The DELETE method is used to remove a resource from your account and environment. It is idempotent, meaning it can be safely retried without changing the outcome if the resource is already deleted. If the resource is not found, a response indicating this will be returned.

```HTTP
DELETE /api/resource/{id}
```

--------------------------------

### Bearer Token Authentication

Source: https://blue-media.stoplight.io/docs/index

This method requires you to provide your bearer token in the Authorization header when making requests to protected resources.

```HTTP
Authorization: Bearer 123
```

--------------------------------

### HTTP PUT Request for Resource Update

Source: https://blue-media.stoplight.io/docs/index

The PUT method is used to update information about a resource. It is idempotent, meaning it sets the resource to a specified state regardless of its current state. No pre-check of the resource's attributes is necessary.

```HTTP
PUT /api/resource/{id}
```

--------------------------------

### Filtering with JSON Object

Source: https://blue-media.stoplight.io/docs/index

Illustrates how to filter API results by providing a JSON object in the filter field. The specific JSON structure is determined by the API's Schema identifier.

```JSON
{
  "filter": {
    "attribute": "value"
  }
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.