Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Roadsync funding sources API

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

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

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

This API exposes 4 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.0.1, at version 1.8.45.

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

4 operations 2 paths 15 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Roadsync funding sources 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 4

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

funding sources 4
GET
/payees/{payee_id}/funding-sources
Get a Payee's Funding Sources
get-funding-sources-id 2 params → 200
POST
/payees/{payee_id}/funding-sources
Create a Funding Source for a Payee
post-payee-funding-sources 2 params body → 201
PATCH
/payees/{payee_id}/funding-sources
Update a Funding Source for a Payee
update-payee-funding-sources 2 params body → 201
GET
/brokers/{broker_id}/funding-sources
Get a Broker's Funding Sources
get-broker-funding-sources-id 1 param → 200

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

id
integer
The id number of the object being returned.
brokerId
integer
The identifier of a Broker to which the Payee will be assigned or has already been assigned.
city
string
A valid city in the United States.
postalCode
string
A valid postal code in the United States.
walletBalance
number
The current balance of the wallet funding source.
bankFundingSource
addressLineOne
string
The valid address of a person or business in the United States.
addressLineTwo
string
If necessary, add a second line of the address in the United States.
state
string
A valid 2 character state code in the United States.
bankName
string
A nickname for the bank account.
hasRtp
boolean
Whether or not the payee's funding source is RTP eligible.
routingNumber
string
A valid routing number for a bank in the United States. Must be exactly 9 digits.
bankAccountType
accountNumber
string
A valid bank account number for a bank in the United States. Typically 10-12 digits in length. When being read, this will be the last 4 digits of the account n…
fundingSourceId
Id representing the funding source (papercheck, ach or wallet).

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

roadsync-funding-sources-api-openapi.yml Raw ↑

Other APIs Roadsync publishes across the network.

Roadsync authenticated API
Roadsync brokers API
Roadsync department API
Roadsync directory API
Roadsync eta API
Roadsync invoice API
Roadsync loads API
Roadsync location API
Roadsync payables API
Roadsync payees API
Roadsync payment API
Roadsync ping API