# Using TxServer API

**Coreledger TxServer** is a component of the TEOS platform, responsible for wallet and device management and for signing and submitting transactions to the blockchains.

**Coreledger TxServer** is required to be used along with TEOS API in case TEOS API Consumer has devices which operate as private keys holder and must be able to sign the transactions with these devices.

## TXServer Concepts

### Device

TXServer device entity represents a physical user device, like a smartphone or a virtual device, like some software worker. In the transaction flow the device API is used to notify a device, responsible for signing, about incoming transaction and about its status updates, after it was signed and submitted for writing into a blockchain.

#### Device Token

The device token is a special type of OAuth access token, containing information about user and device. It is not related to the OAuth device grant flow. Acquisition of the device token is described in the [device authorization flow](/resources/using-additional-apis-of-teos-platform/device-authorization-flow-with-txserver-and-teos-authentication-service.md) article.

#### Device API

This is an API of TXServer with device-specific functionality. Developer reference can be found in [Swagger](https://txapi.coreledger.net/swagger). Most of the functions require the [device token](#device-token) as Bearer.

### Provider

TXServer provider entity represents a consumer of provider API, responsible for transaction initiation and business logic of an application. Examples of providers are: TeosAPI tenants, WLM tenants.

#### Provider API

This API of TXServer is used by various TEOS platform components, e.g. TeosAPI.


---

# 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://teos-docs.coreledger.net/resources/using-additional-apis-of-teos-platform/using-txserver-api.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.