Skip to content
Vocapable Developers

Complete a calendar OAuth consent

GET
/v1/integration-connections/callback
curl --request GET \
  --url 'https://api.vocapable.com/v1/integration-connections/callback?state=example' \
  --header 'Authorization: Bearer <token>'

Unauthenticated by design: the customer’s admin lands here from the provider’s consent screen carrying no API key, so the signed, tenant-bound, 10-minute state is the admission control (docs/04-api.md §7).

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Query Parameters

Section titled “Query Parameters”
state
required
State
string
code
Any of:
string
error
Any of:
string

Responses

Section titled “Responses”

200

Section titled “200”

Successful Response

Media typeapplication/json
IntegrationConnectionSummary

A connection as its tenant sees it - token material is structurally absent.

object
id
required
Id
string
provider
required
Provider
string
external_account_id
Any of:
string
scopes
Scopes
Array<string>
status
required
Status
string
Allowed values: active expired revoked error
last_refreshed_at
Any of:
string format: date-time
created_at
required
Created At
string format: date-time
updated_at
required
Updated At
string format: date-time
Example
{
  "status": "active"
}

303

Section titled “303”

Consent completed and the browser was redirected to the deployment’s fixed portal Settings URL.

Headers

Section titled “Headers”
Location
string format: uri

The fixed portal Settings URL.

422

Section titled “422”

Validation Error

Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
input
Input
ctx
Context
object
Examplegenerated
{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example",
      "input": "example",
      "ctx": {}
    }
  ]
}