### Notifications & Subscriptions API (v1.0)

Source: https://developers.cobre.co/docs/Platformv3/jquqj4hu719ef-notifications-and-subscriptions-api

This API allows you to subscribe to various events and receive notifications via webhooks. It supports a wide range of events related to accounts, money movements, reports, and bulk money movements.

```APIDOC
## Subscribable Events

This section lists the available events that can be subscribed to. Each event has a unique subscription key and an associated layout for notifications.

### Accounts Events

- **accounts.balance.credit**: Event triggered every time the balance of the account gets credited.
- **accounts.balance.debit**: Event triggered every time the balance of the account gets debited.

### Money Movements Events

- **money_movements.status.initiated**: Event triggered every time a money movement resource status changes to initiated.
- **money_movements.status.processing**: Event triggered every time a money movement resource status changes to processing.
- **money_movements.status.pending_approval**: Event triggered every time a money movement resource status changes to pending approval.
- **money_movements.status.completed**: Event triggered every time a money movement resource status changes to completed.
- **money_movements.status.canceled**: Event triggered every time a money movement resource status changes to canceled.
- **money_movements.status.returned**: Event triggered every time a money movement resource status changes to returned.
- **money_movements.status.rejected**: Event triggered every time a money movement resource status changes to rejected.
- **money_movements.status.failed**: Event triggered every time a money movement resource status changes to failed.

### Cross Border Money Movements Events

- **cross_border_money_movements.status.initiated**: Event triggered every time a cross border money movement resource status changes to initiated.
- **cross_border_money_movements.status.processing**: Event triggered every time a cross border money movement resource status changes to processing.
- **cross_border_money_movements.status.completed**: Event triggered every time a cross border money movement resource status changes to completed.
- **cross_border_money_movements.status.rejected**: Event triggered every time a cross border money movement resource status changes to rejected.

### Reports Events

- **reports.created**: Event triggered every time a report has been created.

### Bulk Money Movements Events

- **bulk_money_movements.status.validating**: Event triggered every time a bulk money movement resource status changes to validating.
- **bulk_money_movements.status.processing**: Event triggered every time a bulk money movement resource status changes to processing.
- **bulk_money_movements.status.pending_approval**: Event triggered every time a bulk money movement resource status changes to pending_approval.
- **bulk_money_movements.status.completed**: Event triggered every time a bulk money movement resource status changes to completed.
- **bulk_money_movements.status.canceled**: Event triggered every time a bulk money movement resource status changes to canceled.
- **bulk_money_movements.status.failed**: Event triggered every time a bulk money movement resource status changes to failed.

### API Base URL

- **Production**: `https://api.cobre.co/v1/`

### Security

- **Bearer Auth**: Provide your bearer token in the `Authorization` header when making requests to protected resources.
  Example: `Authorization: Bearer 123`
```

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

### Move Money API Error Codes

Source: https://developers.cobre.co/docs/Platformv3/uwbgq7emqmma5-error-dictionary

This section details error codes specific to the Move Money module. These errors indicate issues with the money movement request, such as invalid descriptions, destination IDs, references, URLs, expiration dates, FX quotes, bank codes, R2P links, source IDs, account authorizations, categories, or secondary counterparties.

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

### Authenticate with Bearer Token

Source: https://developers.cobre.co/docs/Platformv3/jquqj4hu719ef-notifications-and-subscriptions-api

This snippet demonstrates how to authenticate API requests using a Bearer token. The token should be included in the 'Authorization' header. This is crucial for accessing protected resources within the Cobre Notifications Service.

```HTTP
GET /some/protected/resource HTTP/1.1
Host: api.cobre.co
Authorization: Bearer 123
```

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