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

Conga Preferences API

The Billing Preference Controller

Conga Preferences API is one of 347 APIs that Conga publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Preferences. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 7 operations across 5 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://rls.congacloud.com/api/billing/v1.

7 operations 5 paths 8 schemas 2 GET4 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://rls.congacloud.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Conga Preferences API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — Please insert JWT with Bearer into field

Paths & Operations 7

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

Preferences 7

The Billing Preference Controller

GET
/preferences
List preference records
7 params → 200204500
PATCH
/preferences
Update preference records
body → 200207400500
POST
/preferences
Create preferences
body → 201207400500
PATCH
/preferences/activate
Activate or deactivate a list of preference records
body → 200207400500
PATCH
/preferences/{id}/default
Mark the Preference record as default
1 param → 200400500
GET
/preferences/{preferenceId}
Get a preference record
2 params → 200404
PATCH
/preferences/{preferenceId}/activate
Activate or deactivate a preference record
2 params → 200400500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are BillingPreference (21 properties), PreferenceHistory (21 properties), BaseResponse (5 properties), ApiError (4 properties). Each schema is shown below with its type and property counts.

ErrorApiResponse
object
1 property
ApiError
object
4 properties
BillingPreferenceToggleActiveRequest
object
Represents a request to toggle the active flag for a billing preference. Contains the preference identifier and the active status.
2 properties
PreferenceHistory
object
21 properties
BaseResponse
object
5 properties
BaseResponseBatchResponse
object
2 properties
LookupObject
object
2 properties
BillingPreference
object
21 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conga-preferences-api-openapi.yml Raw ↑

Other APIs Conga publishes across the network.

Conga Advantage Platform MCP Server
Conga GraphQL API
Conga 2. Order Actions API
Conga 3. Order Line Items API
Conga Account API
Conga Account Attachments Blacklist API
Conga Account Attachments Whitelist API
Conga Account Designer Settings API
Conga Account Email Reminder Settings API
Conga Account Feature Settings API
Conga Account Package Settings API
Conga Account Roles API
Where this information came from

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