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 Roles Verification API

The RolesVerification API from Conga — 2 operation(s) for rolesverification.

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

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

This API exposes 5 operations across 2 paths, and defines 33 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/sign.

5 operations 2 paths 33 schemas 1 DELETE2 GET1 POST1 PUT

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 Roles Verification API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (JWT). By default, every request must be authenticated.

  • JWT — Provide oauth authentication

Paths & Operations 5

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

RolesVerification 5
GET
/v1/cs-account/{accountId}/verificationTypes
Retrieve advanced verification types
RolesVerification_GetAccountVerificationTypes 1 param → 200401500
POST
/v1/cs-packages/{packageId}/roles/{roleId}/verification
Create advanced verification
RolesVerification_CreateRoleVerification 2 params body → 200400401403404500
DELETE
/v1/cs-packages/{packageId}/roles/{roleId}/verification
Delete an advanced verification method
RolesVerification_DeleteRoleVerification 2 params → 204400401403404500
GET
/v1/cs-packages/{packageId}/roles/{roleId}/verification
Retrieve information on verification types being used
RolesVerification_GetRoleVerification 2 params → 200204400401500
PUT
/v1/cs-packages/{packageId}/roles/{roleId}/verification
Update an advanced verification method
RolesVerification_UpdateRoleVerification 2 params body → 200400401403404500

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Sender (26 properties), Plan (12 properties), Account (11 properties), ProfessionalIdentityField (7 properties). Each schema is shown below with its type and property counts.

Address
object
6 properties
Translation
object
Field localization.
5 properties
Quota
object
4 properties
UserCustomField
object
Object to manage a user custom field
5 properties
Company
object
Company information.
4 properties
GroupMembership
object
Object to manage group membership
3 properties
Error2
object
Object representing an error condition
6 properties
SenderType
string
TextualSignatureStyle
object
Object to manage a text signature
2 properties
License
object
License information.
5 properties
Transaction
object
3 properties
SenderStatus
string
External
object
External integration provider settings.
4 properties
CcExpiration
object
2 properties
CreditCard
object
5 properties
Price
object
Object to manage price
2 properties
Account
object
Account information.
11 properties
Verification
object
Object to manage verification on roles
2 properties
Plan
object
12 properties
Entity
object
Object used to manage entities from Microsoft Dynamics
3 properties
MemberType
string
Type of member in a group
ProfessionalIdentityField
object
Object to manage professional identity field
7 properties
CycleCount
object
2 properties
LicenseStatus
string
SignatureStyle
object
2 properties
Cycle
string
AccountProviders
object
2 properties
Provider
object
Object to manage account providers for documents and users
4 properties
Target
string
CustomField
object
A custom field is one that, at the time of signing, is automatically populated with data that is specific to the signer. For instance, a signer might have an A…
6 properties
Currency
object
The currency used for the Price object
3 properties
ResultOfSender
object
Object used to manage OneSpan list types
2 properties
Sender
object
Sender
26 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conga-rolesverification-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 Roles Verification 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.