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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cariqa

Cariqa Payments API

The Payments API from Cariqa — 4 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cariqa Payments API is one of 7 APIs that Cariqa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and a quickstart.

This API exposes 4 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0 (v1).

Requests are made against 2 base URLs: https://connect.cariqa.com, https://dev.connect.cariqa.com.

4 operations 4 paths 9 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0 (v1)
Base URL
https://connect.cariqa.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cariqa Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

  • BearerAuth — JWT Authorization header using the Bearer scheme.

Paths & Operations 4

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

Payments 4
GET
/api/v1/users/{user_id}/payment-methods/
List Payment Methods
users_payment_methods_list 3 params → 200403404
DELETE
/api/v1/users/{user_id}/payment-methods/{pm}/
Delete Payment Method
users_payment_methods_destroy 2 params → 204400402403404
POST
/api/v1/users/{user_id}/payment-methods/{pm}/default/
Set Payment Method as Default
users_payment_methods_default_create 2 params → 204403404
GET
/api/v1/users/{user_id}/setup-intents/
Get Setup Intent
users_setup_intents_retrieve 2 params → 200400403404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ConnectAPIPM (5 properties), PaginatedConnectAPIPMList (4 properties), ConnectAPICardPM (4 properties), Error (3 properties). Each schema is shown below with its type and property counts.

ErrorTypeEnum
string
validationerror - validationerror paymentmethoderror - paymentmethoderror paymenterror - paymenterror temporarylocked - temporarylocked alreadycharging - alrea…
ConnectAPIPM
object
5 properties 5 required
Detail
object
400 status error message response serializer.
1 property 1 required
ConnectAPISetupIntent
object
1 property 1 required
PaginatedConnectAPIPMList
object
4 properties 2 required
ErrorDetail
object
2 properties 2 required
ConnectAPICardPM
object
4 properties 4 required
ConnectAPIPMTypeEnum
string
card - card applepay - applepay googlepay - googlepay
Error
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cariqa-payments-api-openapi.yml Raw ↑

Other APIs Cariqa publishes across the network.

Cariqa Billing Details API
AE Profile APIs.io
Cariqa Charging Sessions API
AE Profile APIs.io
Cariqa Debts API
AE Profile APIs.io
Cariqa Invoices API
AE Profile APIs.io
Cariqa Stations API
AE Profile APIs.io
Cariqa Users API
AE Profile APIs.io
#Payments
← Back to C APIs
API Details
ID
cariqa:cariqa-payments-api
Base URL
https://connect.cariqa.com
Docs
https://docs.cariqa.com
Provider
Cariqa
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cariqa-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cariqa-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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