Áskell API

Name: Áskell API API
Brand: Áskell API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling SubscriptionsapiKey35 EndpointsREST

For Agents

Run subscription billing — manage plans, customers, subscriptions, transactions, and webhooks — through the Áskell recurring-payments API.

Quickstart

Get started with Áskell API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"subscribe a customer to an Áskell plan"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Áskell API API.

Create and update customer records with payment methods attached

Subscribe a customer to a plan and create multiple subscriptions in one call

List transactions and generate receipts for individual transaction UUIDs

Add a temporary payment method during a checkout flow

Manage webhook endpoints and inspect webhook delivery history

GET STARTED

Start building with Áskell API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Áskell API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Áskell API, keeping it validated and agent-ready. Áskell is an Icelandic subscription billing platform that handles plans, customers, subscriptions, transactions, and webhooks for recurring revenue businesses. The API exposes 35 endpoints across customers, subscriptions, plans, transactions, webhooks, and checkout flows. Authentication uses an API key passed in the Authorization header — secret keys for backend calls and publishable keys for client-side checkout flows.

Use Cases

Patterns agents use Áskell API API for, with concrete tasks.

★ Subscription Onboarding Flow

Convert a new sign-up into a paying subscriber by creating the Áskell customer, attaching a payment method, and subscribing them to the chosen plan. POST /customers/ creates the customer, POST /customers/paymentmethod/ attaches the card, and POST /customers/{customerReference}/subscriptions/add/ activates the subscription. Suitable for SaaS and membership businesses on the Icelandic market.

Create an Áskell customer for 'jane@example.is', attach a payment method, and subscribe to plan 'premium-monthly'

Receipt and Transaction Reporting

Pull the customer's transaction history via GET /transactions/ and generate per-transaction receipts via GET /transactions/{uuid}/receipt/. Useful for finance reconciliation, customer self-service, and compliance reporting where each charge needs an itemised receipt URL.

List Áskell transactions for the last 7 days and generate receipt URLs for any transaction over 10000 ISK

Webhook-Driven Subscription Lifecycle

Register an Áskell webhook for subscription events (payment success, payment failure, cancellation) and use the Webhook calls endpoint to inspect delivery history. Agents can react to failed payments by initiating dunning workflows or notifying customer support. Reduces silent churn from expired cards.

Create an Áskell webhook for the 'subscription.payment_failed' event and verify the most recent delivery succeeded via the Webhook calls endpoint

AI Agent for Subscription Operations

An agent integrated through Jentic can monitor failed payments, retry charges, manage plan upgrades, and answer customer questions about billing — all without holding the Áskell secret API key. Jentic stores the key in its vault and the agent uses Jentic's intent search to navigate the 35 endpoints by purpose rather than reading docs.

Through Jentic, find Áskell subscriptions that failed payment in the last 24 hours and draft a customer message with a payment-update link

Key Endpoints

35 endpoints — jentic publishes the only available openapi specification for áskell api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/customers/

Create a customer

GET

/customers/{customerReference}/subscriptions/

Get all subscriptions for a customer

POST

/customers/{customerReference}/subscriptions/add/

Add a subscription to a customer

POST

/subscriptions/multi/

Create multiple subscriptions

POST

/customers/paymentmethod/

Add a payment method to a customer

GET

/transactions/

Get a list of transactions

GET

/transactions/{uuid}/receipt/

Create a receipt for a transaction

GET

/plans/

Get a list of plans

POST

/customers/

Create a customer

GET

/customers/{customerReference}/subscriptions/

Get all subscriptions for a customer

POST

/customers/{customerReference}/subscriptions/add/

Add a subscription to a customer

POST

/subscriptions/multi/

Create multiple subscriptions

POST

/customers/paymentmethod/

Add a payment method to a customer

Why though Jentic?

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

Credential isolation

Áskell secret API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw key never enters prompts, logs, or agent memory.

Intent-based discovery

Agents search Jentic by intent (e.g. 'subscribe a customer to an Áskell plan') and Jentic returns the matching operation with its input schema, so the agent can call the right endpoint without reading docs.

Time to first call

Direct Áskell integration: 1-2 days to wire the Authorization 'Api-Key' header, customer-payment-method flow, and webhooks. Through Jentic: under 1 hour — search by intent, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Stripe is the global subscription billing platform; Áskell focuses on the Icelandic market with local payment-method support.

Choose Stripe for international billing; choose Áskell when ISK billing and Icelandic payment methods are the priority.

Alternative

Recurly

Recurly is an enterprise subscription billing platform with deep dunning and revenue-recognition features.

Use Recurly for complex global subscription businesses; pick Áskell for simpler Iceland-focused recurring revenue.

Alternative

Paddle

Paddle is a merchant-of-record subscription platform that handles tax compliance globally.

Choose Paddle when you need a merchant-of-record handling sales tax and VAT; choose Áskell for direct Icelandic billing.

Complementary

Xero Accounting

Xero records subscription revenue from Áskell into the general ledger.

Pair with Áskell when subscription transactions need to flow into accounting for reconciliation and reporting.

FAQs

Specific to using Áskell API API through Jentic.

Why is there no official OpenAPI spec for Áskell API?

Áskell does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Áskell API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Áskell API use?

The API uses an API key passed in the Authorization header. Áskell issues two key types: a Secret-Api-Key for backend calls (Authorization: 'Api-Key {secret}') and a Public-Api-Key for client-side checkout. Jentic stores the secret key in its vault and never exposes it to the agent.

Can I subscribe a customer to a plan through the Áskell API?

Yes. POST /customers/{customerReference}/subscriptions/add/ adds a subscription to an existing customer. For multiple subscriptions in one call, use POST /subscriptions/multi/. The customer must have a payment method attached via POST /customers/paymentmethod/ first.

How do I generate a receipt for a transaction?

GET /transactions/{uuid}/receipt/ returns a receipt for the specified transaction UUID. List transactions first via GET /transactions/ to find the UUID, then call the receipt endpoint to retrieve the formatted receipt.

What are the rate limits for the Áskell API?

The OpenAPI specification does not document explicit rate limits. Áskell is a regional billing provider — implement exponential backoff on HTTP 429 and avoid polling /transactions/ in tight loops. Use webhooks for event-driven workflows where possible.

How do I create a customer through Jentic?

Search Jentic for 'create an Áskell customer' — POST /customers/ will be returned. Load the operation schema, supply the customer details, and execute. Jentic handles authentication and returns the customerReference for downstream subscription operations.