Kobble Relays API

Introduction

Create and manage rules defining spending limits, merchant category code (MCC) restrictions, and other card usage parameters. Process transactions based on client-defined rules.

Overview

Provides a endpoint to create relays.

Key Features

RESTful API with predictable resource-based URLs.

Authentication with secure bearer tokens.

Flexible options for creating and managing endusers.

Base URLs

Use the appropriate base URL depending on the environment:

Production: https://apikobble.net/

Staging: https://staging.apikobble.net/

Ensure you prepend the base URL to each endpoint while making requests.

Each environment has its own Cognito user pool, so your staging client ID and secret will not authenticate against production. Production credentials are issued separately as part of go-live.

API Endpoints

Create subscription.

Authentication

All requests to the Relays API require an access token. Include the access token in the headers of each request:

To generate an access token, please refer to Authorization.

Error Handling

The API returns standard HTTP status codes for responses. Use the status code to determine the result of your request.

Notes

All responses are returned in JSON format.

Ensure the proper base URL and headers are used in each request.

Relays API

Kobble Relays API#

Introduction#

Overview#

Key Features#

Base URLs#

API Endpoints#

Authentication#

Error Handling#

Notes#