Create REST discovery connection
Use this endpoint to create a REST connection to a payment provider: PagBank, Stripe, or Pix BCB. The credential fields each connector type requires are listed as requiredFields on GET /v1/discovery/connector-types. An optional baseURL replaces the default provider address for this connection. After you create it, the connection appears in GET /v1/discovery/connections; an update to a REST connection accepts only configName.
Autorizaciones
Bearer token authentication (format: "Bearer {token}")
Cuerpo
Unique connection config name (tenant-scoped)
1 - 255"pagbank-prod"
REST connector type this connection serves
PAGBANK, STRIPE, PIX_BCB 1"PAGBANK"
Stripe restricted API key
512Optional per-connection API base URL (http/https); when omitted the deployment default for the connector type is used
2048"https://sandbox.provider.example"
PEM-encoded Pix client certificate
8192Pix OAuth2 client id
512PEM-encoded Pix client private key
8192Pix OAuth2 client secret
512PagBank EDI token
512PagBank establishment id
512Respuesta
Created
Connection configuration name
"prod-ledger-db"
Database name
"ledger"
Database engine type (canonical engine token as stored)
"POSTGRESQL"
Database host; empty for REST connector connections, whose service address is reported as baseURL
"db.internal.example.com"
Internal Matcher connection identifier
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
Timestamp the connection was last observed healthy (RFC 3339)
"2026-06-17T14:32:05Z"
Database port
5432
Whether table schemas have been discovered for this connection
Current lifecycle status of the connection as reported by the extraction engine
"available"
Database user name the connection authenticates as
"matcher_ro"
Per-connection API base URL of a REST connector connection; absent when the deployment default applies and for database connectors
"https://sandbox.provider.example"
Schema/namespace within the database, when set
"public"

