How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Roadsync

Roadsync transactions API

The transactions API from Roadsync — 2 operation(s) for transactions.

Documentation Provider Profile APIs.io OpenAPI GitHub

Roadsync transactions API is one of 18 APIs that Roadsync publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 2 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.8.45.

Requests are made against a single base URL, https://client-api.staging.roadsync.com/{basePath}.

3 operations 2 paths 24 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.8.45
Base URL
https://api.roadsync.app/rspay/v1
Authentication
API Key, HTTP Bearer
Contact
christo.delange@roadsync.com
License
Copyright (c) 2020, RoadSync Inc.
Resource Areas
1

Authentication & Security 2

Roadsync transactions API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (api_key). It accepts HTTP bearer tokens (JWT) (session_token). By default, every request must be authenticated.

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

transactions 3
GET
/transactions
Get a List of Transactions
get-transactions 2 params → 200
POST
/transactions
Create a Single Transaction
post-transactions 1 param body → 201
GET
/transactions/{id}
Get a Single Transaction
get-transactions-id 2 params → 200401403404

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are transaction (11 properties), payeeShort (3 properties), brokerShort (2 properties). Each schema is shown below with its type and property counts.

isVerified
boolean
A verified Payee is visible to all brokers in the RoadSync Pay environment. Some partners are allowed to verify a Payee by setting the isverified flag to true…
invoiceNumber
string
The invoice number being paid by the payable/receivable. This is visible by the Payee in remittance emails as referenceid.
brokerName
string
The name of the broker.
scheduledForDate
string
A valid date in the future when the payment should be initiated or "now" indicating immediate payment.
payeeShort
object
Details of the Payee receiving the funds. It could be a Carrier or Factoring Company.
3 properties
amountAsString
string
Money in USD to transfer or has been transferred.
amount
number
Money in USD to transfer or has been transferred.
poNumber
string
A unique identifier that links the purchase order the payable.
isFactoringCompany
boolean
Send "true" if this Payee is a Factoring Company, "false" otherwise.
status
The current status of the payable. UNKNOWN is returned when the status value is not recognized.
eta
string
The estimated time of arrival of the payment, based on the payment method selected and scheduled date in ISO 8601 format.
idempotencyKey
integer
Provide a unique value to prevent duplicates during retries.
brokerShort
object
The short description of the broker.
2 properties
createdDatetime
string
Indicates the datetime when the object was created in ISO 8601 format.
brokerId
integer
The identifier of a Broker to which the Payee will be assigned or has already been assigned.
payeeId
integer
The unique identifier of the Payee who will receive the funds. It could be a Carrier or a Factoring Company.
referenceId
string
An identifier used by the Broker to correlate the Transaction with another system or document.
payeeName
string
The name of the Carrier or Factoring Company.
payableId
integer
The Payable's ID
updatedDatetime
string
Indicates the last time the entity was updated in ISO 8601 format.
id
integer
The id number of the object being returned.
carrierPayeeId
string
If the Transaction is created for a Factoring Company, then a Carrier can be associated to the Transaction.
transaction
object
11 properties
paymentMethod
The method used to settle a payable.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

roadsync-transactions-api-openapi.yml Raw ↑

Other APIs Roadsync publishes across the network.

Roadsync authenticated API
AE Profile APIs.io
Roadsync brokers API
AE Profile APIs.io
Roadsync department API
AE Profile APIs.io
Roadsync directory API
AE Profile APIs.io
Roadsync eta API
AE Profile APIs.io
Roadsync funding sources API
AE Profile APIs.io
Roadsync invoice API
AE Profile APIs.io
Roadsync loads API
AE Profile APIs.io
Roadsync location API
AE Profile APIs.io
Roadsync payables API
AE Profile APIs.io
Roadsync payees API
AE Profile APIs.io
Roadsync payment API
AE Profile APIs.io
#Transaction
← Back to R APIs
API Details
ID
roadsync:roadsync-transactions-api
Base URL
https://api.roadsync.app/rspay/v1
Docs
https://developer.roadsync.com/openapi/rspay/overview/
Provider
Roadsync
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=roadsync-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/roadsync-transactions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Roadsync transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.