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

Omise Transfers API

Payouts from your balance to a recipient bank account.

Omise Transfers API is one of 13 APIs that Omise publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 2019-05-29.

Requests are made against 2 base URLs: https://api.omise.co, https://vault.omise.co.

5 operations 2 paths 4 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2019-05-29
Base URL
https://api.omise.co
Authentication
HTTP Basic, HTTP Basic
Resource Areas
1

Authentication & Security 2

Omise Transfers API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (secretKeyAuth). It accepts HTTP basic authentication (publicKeyAuth). By default, every request must be authenticated.

  • secretKeyAuth — HTTP Basic auth against https://api.omise.co. The secret key (skeytest... or skey... ) is the username; the password is left empty.
  • publicKeyAuth — HTTP Basic auth against https://vault.omise.co for tokenization and for creating sources. The public key (pkeytest... or pkey... ) is the username; the passwor…

Paths & Operations 5

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

Transfers 5

Payouts from your balance to a recipient bank account.

POST
/transfers
Create a transfer
createTransfer body → 200401
GET
/transfers
List transfers
listTransfers → 200401
GET
/transfers/{id}
Retrieve a transfer
getTransfer 1 param → 200404
PATCH
/transfers/{id}
Update a transfer
updateTransfer 1 param body → 200404
DELETE
/transfers/{id}
Delete a transfer
deleteTransfer 1 param → 200404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Transfer (14 properties), List (7 properties), Error (4 properties), Deleted (3 properties). Each schema is shown below with its type and property counts.

List
object
Omise paginated list envelope.
7 properties
Error
object
4 properties
Transfer
object
14 properties
Deleted
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

omise-transfers-api-openapi.yml Raw ↑

Other APIs Omise publishes across the network.

Omise Account API
Omise Cards API
Omise Charges API
Omise Customers API
Omise Disputes API
Omise Events API
Omise Links API
Omise Recipients API
Omise Refunds API
Omise Schedules API
Omise Sources API
Omise Tokens API
Where this information came from

This is an independent, third-party profile of Omise Transfers 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.