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

Cariqa Billing Details API

The Billing Details API from Cariqa — 1 operation(s) for billing details.

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

Tagged areas include Billing Details. 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 2 operations across 1 path, and defines 6 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.

2 operations 1 paths 6 schemas 1 GET1 PUT

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 Billing Details 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 2

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

Billing Details 2
GET
/api/v1/users/{user_id}/billing-details/
Get Billing Details
users_billing_details_retrieve 1 param → 200403404
PUT
/api/v1/users/{user_id}/billing-details/
Update Billing Details
users_billing_details_update 1 param body → 200400403404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ConnectAPIBillingDetails (10 properties), Error (3 properties), ErrorDetail (2 properties), Detail (1 property). Each schema is shown below with its type and property counts.

ErrorTypeEnum
string
validationerror - validationerror paymentmethoderror - paymentmethoderror paymenterror - paymenterror temporarylocked - temporarylocked alreadycharging - alrea…
ConnectAPIBillingDetails
object
Serializer which is used to serialize data with the possible business details if exist
10 properties 2 required
Detail
object
400 status error message response serializer.
1 property 1 required
ErrorDetail
object
2 properties 2 required
AccountTypeEnum
string
personal - personal business - business
Error
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cariqa-billing-details-api-openapi.yml Raw ↑

Other APIs Cariqa publishes across the network.

Cariqa Charging Sessions API
Cariqa Debts API
Cariqa Invoices API
Cariqa Payments API
Cariqa Stations API
Cariqa Users API
Where this information came from

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