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
Rainforest

Rainforest Devices API

Resources for device functions.

Documentation Provider Profile APIs.io OpenAPI GitHub

Rainforest Devices API is one of 23 APIs that Rainforest publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 8 operations across 6 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.sandbox.rainforestpay.com, https://api.rainforestpay.com.

8 operations 6 paths 0 schemas 1 DELETE2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.rainforestpay.com
Authentication
HTTP Bearer
Contact
Rainforest
Resource Areas
1

Authentication & Security 1

Rainforest Devices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (APIKey) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 8

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

Devices 8

Resources for device functions.

POST
/v1/device_registrations
Create device registration
create_device_registration 1 param body → 2004004014035XX
GET
/v1/device_registrations
List device registrations
list_device_registrations 8 params → 2004004014035XX
GET
/v1/device_registrations/{device_registration_id}
Get device registration
get_device_registration 2 params → 2004004014034045XX
DELETE
/v1/device_registrations/{device_registration_id}
Delete device registration
delete_device_registration 2 params → 2044004014034045XX
POST
/v1/device_registrations/{device_registration_id}/payin
Present payin on a registered device
create_device_payin 2 params body → 2004004014034044095XX
POST
/v1/device_registrations/{device_registration_id}/payment_method
Present payment method on a registered device
create_device_payment_method 2 params body → 2004004014034044095XX
POST
/v1/device_registrations/{device_registration_id}/cancel
Cancel presented entity on device
cancel_device_presented 2 params → 2022044004014034045XX
POST
/v1/device_registrations/{device_registration_id}/simulate
Simulate device interaction
simulate_on_device 2 params body → 2044004014034044095XX

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rainforest-devices-api-openapi.yml Raw ↑

Other APIs Rainforest publishes across the network.

Rainforest ACH Returns API
AE Profile APIs.io
Rainforest API Keys API
AE Profile APIs.io
Rainforest Billing Profiles API
AE Profile APIs.io
Rainforest BIN Lookups API
AE Profile APIs.io
Rainforest Chargebacks API
AE Profile APIs.io
Rainforest Deposit Method Configs API
AE Profile APIs.io
Rainforest Deposit Methods API
AE Profile APIs.io
Rainforest Deposits API
AE Profile APIs.io
Rainforest File Upload Configs API
AE Profile APIs.io
Rainforest File Uploads API
AE Profile APIs.io
Rainforest Forward Requests API
AE Profile APIs.io
Rainforest Health API
AE Profile APIs.io
#Devices
← Back to R APIs
API Details
ID
rainforest:rainforest-devices-api
Base URL
https://api.rainforestpay.com
Docs
https://docs.rainforestpay.com/
Provider
Rainforest
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=rainforest-devices-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/rainforest-devices-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 Rainforest Devices 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.