# Overview

<div style='text-align:center'><img src='/images/logo_viamericas.png' width='60%'/></div><br><br> 

 ViaBlocks API Inbound is a server-to-sever API that enables regulated partners create and track money transfers. The API supports sender and beneficiary onboarding, transaction creation, funding, FX handling, payout execution, and status tracking. The two API calls are POST /transaction/create to submit sender, beneficiary, and transaction details, and POST /transaction/status to retrieve the latest processing status. 

 Inbound transaction is a money transfer created by a partner through this API. It represents funds sent from a sender in the origination country to a beneficiary in the delivery country, and it is tracked from creation through payout using /transaction/status 

Version: 1.0.0

## Servers

Sandbox environment
```
https://sandbox-viablocks.viamericas.io
```

Production environment
```
https://viablocks.viamericas.net
```

## Download OpenAPI description

[Overview](https://docs2-viablocks.viamericas.io/_bundle/apis/inbound.yaml)

## Transaction

This section provides the Transaction endpoints required to manage and operate the full lifecycle of resources within the ViaBlocks platform. 

These endpoints are designed for secure, auditable, and scalable server-to-server integrations, and support all core business operations and compliance workflows.

### /transaction/create

 - [POST /transaction/create](https://docs2-viablocks.viamericas.io/apis/inbound/transaction/paths/~1transaction~1create/post.md): Creates a new money transfer transaction. 

This endpoint validates sender and beneficiary data, applies compliance checks, and registers the transaction for processing.

### /transaction/status

 - [POST /transaction/status](https://docs2-viablocks.viamericas.io/apis/inbound/transaction/paths/~1transaction~1status/post.md): Retrieves the current status and processing details of a previously created transaction.

This endpoint provides real-time visibility into the transaction lifecycle, including compliance checks, funding confirmation, routing, payout execution, and final settlement.

The transaction is uniquely identified by its uuid, which is returned by the transaction creation endpoint.