API archive entry · source-reported

Rebilly REST API

# Introduction The Rebilly API is built on HTTP. Our API is RESTful. It has predictable resource URLs. It returns HTTP response codes to indicate errors. It also accepts and returns JSON in the HTTP body. You can use your favorite HTTP/REST library for your programming language to use Rebilly's API, or you can use one of our SDKs (currently available in PHP and Javascript). We have other APIs that are also available. Every action from our app is supported by an API which is documented and available for use so that you may automate any workflows necessary. This document contains the most commonly integrated resources. # Authentication When you sign up for an account, you are given your first secret API key. You can generate additional API keys, and delete API keys (as you may need to rotate your keys in the future). You authenticate to the Rebilly API by providing your secret key in the request header. Rebilly offers three forms of authentication: secret key, publishable key, JSON Web Tokens, and public signature key. - Secret API key: used for requests made from the server side. Never share these keys. Keep them guarded and secure. - Publishable API key: used for requests from the

Provider / source website

Documentation & source

Use the provider’s reference for current endpoints, setup, limits and terms.

No separate documentation URL has been confirmed for this record.

Open provider / source ↗

Provider content retains its own terms. This listing does not grant reuse or training rights.

Access at a glance

These are reported access facts. Check the current documentation before integrating.

  • Authentication: Unknown.
  • HTTPS: not confirmed.
  • Browser access (CORS): Unknown.

Pricing and limits

Current plans, quotas, and rate limits have not been reviewed for this listing. Check the provider’s current terms; no authentication does not necessarily mean free usage.

Documentation and sources

Imported from APIs.guru OpenAPI Directory. A detailed editorial review has not been published yet.

Provider / source reference

OpenAPI specification

APIs.guru OpenAPI Directory · CC0 contributed definitions; upstream provider terms may differ

More Finance APIs

1Forge Finance APIs

Stock and Forex Data and Realtime Quotes

Unknown · HTTPS unconfirmed · CORS Unknown

Account and Transaction API Specification - UK

## Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the UK Open Banking Specification v3.1.5 This Account and Transaction API Specification describes the flows and payloads for retrieving a list of accounts and their transactions. The API endpoints described here allow a AISP to: * Create the Consent with the appropriate permissions in order to be able to access the API Endpoints * Retrieve the list of accounts * Retrieve an account's details * Retrieve an account's balances * Retrieve an account's transactions * Retrieve an account's beneficiaries * Retrieve an account's standing orders * Retrieve an account's party * Retrieve an account's scheduled payments * Retrieve an account's statements ## Quick Getting Started 1. **Login/Register** to the NBG Technology HUB 2. Go to **"APPS"** 3. Select your Organization and go to step 4. If you want to create a new Organization click **\"CREATE AN ORGANIZATION\"** and follow the steps below: 1. Enter the title of your Organization 2. Enter a short description of your Organization (optional) 3. Click **"SUBMIT"** 4. Select the Organization of choice and click **"ADD AN APPLICATION"** 1. Fill in the for

Unknown · HTTPS unconfirmed · CORS Unknown

Account API

This API is used for the classic integration. If you are just starting your implementation, refer to our new integration guide instead. The Account API provides endpoints for managing account-related entities on your platform. These related entities include account holders, accounts, bank accounts, shareholders, and verification-related documents. The management operations include actions such as creation, retrieval, updating, and deletion of them. For more information, refer to our documentation. ## Authentication Your Adyen contact will provide your API credential and an API key. To connect to the API, add an `X-API-Key` header with the API key as the value, for example: ``` curl -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ ... ``` Alternatively, you can use the username and password to connect to the API using basic authentication. For example: ``` curl -U "ws@MarketPlace.YOUR_PLATFORM_ACCOUNT":"YOUR_WS_PASSWORD" \ -H "Content-Type: application/json" \ ... ``` When going live, you need to generate new web service user credentials to access the live endpoints. ## Versioning The Account API supports versioning using a version suffix in the endpoint URL. Thi

Unknown · HTTPS unconfirmed · CORS Unknown

Accounting API

A flexible API for pulling accounting data, normalized and aggregated from 20 accounting integrations. Standardize how you connect to your customers’ accounting software. View, create, update, and delete data in the same way for all the leading accounting platforms. Read more... See our OpenAPI spec

Unknown · HTTPS unconfirmed · CORS Unknown

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.