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
Rotessa

Rotessa Customers API

Create, retrieve, and update the bank-account holders Rotessa withdraws from.

Documentation Provider Profile APIs.io OpenAPI GitHub

Rotessa Customers API is one of 6 APIs that Rotessa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://api.rotessa.com/v1, https://sandbox-api.rotessa.com/v1.

6 operations 4 paths 8 schemas 2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.rotessa.com/v1
Authentication
API Key
Contact
Rotessa Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Rotessa Customers API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — API key placed in the Authorization header in the form Authorization: Token token=" ". Keys are created and revoked in the Rotessa admin portal.

Paths & Operations 6

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

Customers 6

Create, retrieve, and update the bank-account holders Rotessa withdraws from.

GET
/customers
Get all customers
listCustomers → 200401500
POST
/customers
Create a customer
createCustomer body → 200400401422
PATCH
/customers
Update a customer via PATCH
updateCustomer body → 200400401404422
GET
/customers/{id}
Get a specific customer based on Rotessa ID
getCustomer 1 param → 200401404
POST
/customers/show_with_custom_identifier
Get a specific customer based on custom identifier
showCustomerByCustomIdentifier body → 200401404
POST
/customers/update_via_post
Update a customer via POST
updateCustomerViaPost body → 200400401404422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Customer (18 properties), CustomerCreate (14 properties), FinancialTransaction (11 properties), TransactionSchedule (9 properties). Each schema is shown below with its type and property counts.

FinancialTransaction
object
11 properties
TransactionSchedule
object
9 properties
Address
object
Customer address.
6 properties
CustomerUpdate
ErrorEnvelope
object
Rotessa error envelope. Errors are returned as a list of objects each carrying a machine-readable errorcode and a human-readable errormessage.
1 property
Frequency
string
Frequency of the transaction schedule.
Customer
object
18 properties
CustomerCreate
object
14 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rotessa-customers-api-openapi.yml Raw ↑

Other APIs Rotessa publishes across the network.

Rotessa Transaction Schedules API
AE Profile APIs.io
Rotessa Transaction Report API
AE Profile APIs.io
Rotessa Transaction Report API
AE Profile APIs.io
Rotessa Transaction Schedules API
AE Profile APIs.io
#Customers
← Back to R APIs
API Details
ID
rotessa:rotessa-customers-api
Base URL
https://api.rotessa.com/v1
Docs
https://rotessa.com/docs/#customers
Provider
Rotessa
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=rotessa-customers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/rotessa-customers-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 Rotessa Customers 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.