Portal Configuration

Submit Portal Config

Submit or update portal credentials for a brand+portal combination.

Payload from PortalConfigDialog.js: { "brand_id": 1, "pv_id": 10, (optional) "platform_slug": "standvirtual", "credentials": { "client_id": "...", "client_secret": "...", ... } }

A support ticket is opened for every submission so the work is tracked rather than living only in an email — see app/services/portal_config_tickets.

GOVERNING PRINCIPLE: the credentials are the product, the ticket is the alert. Nothing in the alerting path may prevent the credentials from being stored, so every lookup that can fail (PV ownership, company name, ticket creation) lives AFTER the upsert and is individually guarded. The response is a 200 with ticket_id: null when the alert degrades — never a 4xx/5xx on a submission that succeeded.

post/api/integrazu/portal-config

Headers

x-api-tokenstring nullable

Request body

object required

Response

Successful Response

{"stackTrail":"paths:/api/integrazu/portal-config:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes

No recorded changes to this endpoint across all 1 revision of this API.