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

Coalesce Git Accounts API

Manage Git account integrations

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

Tagged areas include Git Accounts. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against 5 base URLs: https://app.coalescesoftware.io/api/v1, https://app.us-east-1.aws.coalescesoftware.io/api/v1, https://app.eu.coalescesoftware.io/api/v1, https://app.northamerica-northeast1.gcp.coalescesoftware.io/api/v1, https://app.australia-southeast1.gcp.coalescesoftware.io/api/v1.

5 operations 2 paths 5 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
Base URL
https://app.coalescesoftware.io/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Coalesce Git Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token obtained from the Deploy tab in the Coalesce application. Tokens never expire and remain valid across all environments and projects.

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.

Git Accounts 5

Manage Git account integrations

GET
/gitAccounts
List Git Accounts
listGitAccounts 4 params → 200400401
POST
/gitAccounts
Create Git Account
createGitAccount body → 200400401
GET
/gitAccounts/{gitAccountID}
Get Git Account
getGitAccount 1 param → 200400401
PUT
/gitAccounts/{gitAccountID}
Update Git Account
updateGitAccount 1 param body → 200400401
DELETE
/gitAccounts/{gitAccountID}
Delete Git Account
deleteGitAccount 1 param → 204400401

Schemas 5

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

GitAccountList
GitAccountInput
object
3 properties 2 required
GitAccount
object
4 properties
PaginatedResponse
object
2 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coalesce-git-accounts-api-openapi.yml Raw ↑

Other APIs Coalesce publishes across the network.

Coalesce Environments API
Coalesce Nodes API
Coalesce Projects API
Coalesce Runs API
Coalesce Scheduler API
Coalesce Users API
Where this information came from

This is an independent, third-party profile of Coalesce Git Accounts 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.