Post Transaction  [Go SDK]

Posts a new transaction to the DigitalBits Network. Note that creating a valid transaction and signing it properly is the responsibility of your client library.

Transaction submission and the subsequent validation and inclusion into the DigitalBits Network’s ledger is a complicated and asynchronous process. To reduce the complexity, frontier manages these asynchronous processes for the client and will wait to hear results from the DigitalBits Network before returning an HTTP response to a client.

Transaction submission to frontier aims to be idempotent: a client can submit a given transaction to frontier more than once and frontier will behave the same each time. If the transaction has already been successfully applied to the ledger, frontier will simply return the saved result and not attempt to submit the transaction again. Only in cases where a transaction’s status is unknown (and thus will have a chance of being included into a ledger) will a resubmission to the network occur.

Information about building transactions in JavaScript.


If you are encountering this error it means that either:

  • Frontier has not received a confirmation from the Core server that the transaction you are trying to submit to the network was included in a ledger in a timely manner or:
  • Frontier has not sent a response to a reverse-proxy before in a specified time.

The former case may happen because there was no room for your transaction in the 3 consecutive ledgers. In such case, Core server removes a transaction from a queue. To solve this you can either:

  • Keep resubmitting the same transaction (with the same sequence number) and wait until it finally is added to a new ledger or:
  • Increase the fee.


POST /transactions


name loc notes example description
tx body required AAAAAOf4yDBA== Base64 representation of transaction envelope XDR

curl Example Request

curl -X POST \


A successful response (i.e. any response with a successful HTTP response code) indicates that the transaction was successful and has been included into the ledger.

If the transaction failed or errored, then an error response will be returned. Please see the errors section below.


The response will include all fields from the transaction resource.

Example Response

  "_links": {
    "self": {
      "href": ""
    "account": {
      "href": ""
    "ledger": {
      "href": ""
    "operations": {
      "href": "{?cursor,limit,order}",
      "templated": true
    "effects": {
      "href": "{?cursor,limit,order}",
      "templated": true
    "precedes": {
      "href": "\u0026cursor=4122468524494848"
    "succeeds": {
      "href": "\u0026cursor=4122468524494848"
    "transaction": {
      "href": ""
  "id": "f5d126b3b2e870d3ec5f2ed7d11135cf4cefc95459d5ffb8c67dcd3731c08cc6",
  "paging_token": "4122468524494848",
  "successful": true,
  "hash": "f5d126b3b2e870d3ec5f2ed7d11135cf4cefc95459d5ffb8c67dcd3731c08cc6",
  "ledger": 959837,
  "created_at": "2021-06-16T12:26:02Z",
  "source_account_sequence": "4109304449728516",
  "fee_charged": "100",
  "max_fee": "100",
  "operation_count": 1,
  "memo_type": "none",
  "signatures": [
  "valid_after": "1970-01-01T00:00:00Z",
  "valid_before": "2021-06-16T12:29:53Z"

Possible Errors

  • The standard errors.
  • transaction_failed: The transaction failed and could not be applied to the ledger.
  • transaction_malformed: The transaction could not be decoded and was not submitted to the network.
  • timeout: No response from the Core server in a timely manner. Please check “Timeout” section above.

Edit this doc in GitHub


Stay up to date on the latest happenings at DigitalBits. Get the latest news.