SumUp REST API

Name: SumUp REST API
Brand: SumUp REST API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingBearer, oauth245 EndpointsREST

For Agents

Programmatically get available payment methods, create a checkout. Covers 45 operations with Bearer, oauth2 authentication.

Install Jentic One Beta

Connect the SumUp REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SumUp REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SumUp REST API.

Get available payment methods

Create a checkout

List checkouts

Retrieve a checkout

GET STARTED

Start building with SumUp REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SumUp REST API for, with concrete tasks.

★ Payments Operations

Use the SumUp REST API to perform payments operations programmatically. The API provides 45 endpoints covering core functionality including get available payment methods, create a checkout, list checkouts.

Call GET /v0.1/merchants/{merchant_code}/payment-methods to get available payment methods

Automated Checkouts Management

Automate checkouts operations by combining multiple SumUp REST API endpoints. Agents can create a checkout and then list checkouts in a single workflow.

Call POST /v0.1/checkouts to create a checkout, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SumUp REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle Bearer, oauth2 tokens manually.

Search Jentic for 'get available payment methods', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

45 endpoints — sumup’s rest api operates with [json](https://www.

METHOD

PATH

DESCRIPTION

GET

/v0.1/merchants/{merchant_code}/payment-methods

Get available payment methods

POST

/v0.1/checkouts

Create a checkout

GET

/v0.1/checkouts

List checkouts

GET

/v0.1/checkouts/{id}

Retrieve a checkout

PUT

/v0.1/checkouts/{id}

Process a checkout

DELETE

/v0.1/checkouts/{id}

Deactivate a checkout

POST

/v0.1/customers

Create a customer

GET

/v0.1/customers/{customer_id}

Retrieve a customer

GET

/v0.1/merchants/{merchant_code}/payment-methods

Get available payment methods

POST

/v0.1/checkouts

Create a checkout

GET

/v0.1/checkouts

List checkouts

GET

/v0.1/checkouts/{id}

Retrieve a checkout

PUT

/v0.1/checkouts/{id}

Process a checkout

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SumUp REST API Bearer, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get available payment methods') and Jentic returns the matching SumUp REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SumUp REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SumUp REST API through Jentic.

What authentication does the SumUp REST API use?

The SumUp REST API uses Bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get available payment methods with the SumUp REST API?

Yes. Use the GET /v0.1/merchants/{merchant_code}/payment-methods endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SumUp REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get available payment methods through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get available payment methods'. Jentic returns the matching SumUp REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the SumUp REST API have?

The SumUp REST API exposes 45 endpoints covering checkouts, customers, transactions operations.

SumUp REST API

Connect the SumUp REST API to your agent

Capabilities

Start building with SumUp REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs